Integrations
Plug StoryOS into everything you already use.
Your CRM, your communication tools, your editing software — StoryOS reaches into the stack your team already runs, so stories flow out without rebuilding your workflow.
One protocol connects your whole stack.
Connect Cue to anything. StoryOS exposes an open Model Context Protocol (MCP) surface and a Cue API secured with OAuth 2.0, so your tools and AI agents can read and act on your story graph — with human-approval gates intact.
Open Model Context Protocol surface
Any MCP-compatible tool or AI agent can read and act on the StoryOS story graph. The protocol is open, well-documented, and designed for the agentic tooling your team uses today and the tools they will use next year.
Cue API secured with OAuth 2.0
External tools authenticate through OAuth 2.0 and operate within scoped permissions. Every write action that touches a narrative surface still passes through a human-approval gate — the connectivity layer cannot bypass the controls the platform enforces.
Human-approval gates intact
Cue reads context, surfaces suggestions, and can draft across connected systems. A human on your team approves before anything reaches a client, donor, or audience — regardless of where the trigger originated.
What connects today
Three categories of connectivity are available now — donor and CRM systems, communication platforms, and media tools.
Donor & CRM
Push stories and stewardship touches into the systems your development team already runs.
Work & communication
Reachable through StoryOS's open connectivity layer.
Media & post-production
Fits the tools your editors already use.
CRM and communication tools listed here are reachable through StoryOS's open connector framework and MCP surface. Native integration depth varies by tool; additional tools connect as the platform matures.
Bring your stack into the story.
We'll be in touch. If you have a specific integration in mind, mention it when you sign up — it helps us prioritize the connector roadmap.