It plays well with what you already run.
We would rather connect to your stack than pretend you should abandon it. Here is what connects today — and what honestly does not yet.
Current integration surface
AI assistants
- Claude (MCP)
- ChatGPT (MCP)
- Any MCP-capable client
Scoped, revocable read/write keys.
DetailsCRM sync
- GoHighLevel contact sync
- CSV import and export
Bring an existing list in; take yours out whenever.
DetailsPayments and commerce
- Card payments
- Checkouts
- Upsell offers
- Transactions
Configured in workspace settings.
DetailsDomains and delivery
- Any registrar
- Automatic SSL
- CDN delivery
Point your domain; the rest is handled.
DetailsIntegrations are expanding. If something you depend on is missing, tell us — that is genuinely how the list gets prioritised.
Keys and connections live in your workspace.
API keys are scoped and revocable, so an assistant with read access can never publish, and you can cut access without touching your site.
How MCP access works
Three products, deliberately separate
Same company, same thinking, different jobs. We keep them separate so you can adopt one without swallowing all three.
StoryOS
Open-source, self-hostable, API-first: user-defined relational databases, eight view types, automations, and a native MCP server. StoryPages is your public face; StoryOS is where the work is actually tracked.
How it connects: Both products expose MCP servers, so one AI assistant can span your public site and your internal data. There is no prebuilt one-click sync between them today — the honest answer is MCP and APIs.
Visit StoryOSStoryFunnels
The James Cook Media practice for people who want the strategy and the build handled with them rather than by them. Same team, same thinking, more hands.
How it connects: If you would rather someone built and ran the funnel for you, this is that route.
Visit StoryFunnelsConnect it to the stack you already have.
Start free, point your assistant at it, and see how it fits before you move anything.