Build in Origamy from
the AI app you already use
Connect Claude, ChatGPT, Cursor or another MCP app and ask it to read your setup, then plan segments, templates, forms and journeys. You see the plan first, and everything lands off.
Your workspace,
in the conversation
It works as you, in the workspace you pick, with your permissions. The AI runs on your own app’s plan.
“Which journeys are on, and how often have they run?”
It reads your segments, templates, forms, journeys, reports and teams, and can search across all of them by name.
“Plan a visitor follow-up: a form, two messages and a call task for my team.”
It checks the whole plan against the same rules the builders use, shows you a preview and saves it only after you say yes.
“Draft this month’s email with the fields we actually have.”
It gets your field names and made-up sample people, so templates use real variables without it seeing anyone real.
Two minutes,
one URL
You need an Origamy account and this address. There is no API key to copy. You sign in with your Origamy account.
https://mcp.origamy.io/mcpClaude
Claude web and desktop. Free plans can add one custom connector.
- Go to Customize → Connectors.
- Choose + Add, then Add custom connector.
- Name it Origamy, paste the URL and choose Continue.
- Keep the detected sign-in settings and choose Add.
- Sign in when Claude asks. If it doesn't, choose Connect on the Origamy connector.
On a Team or Enterprise plan
An owner adds it first under Organization settings → Connectors: Add, then Custom, then Web. Each person then chooses Connect under Customize → Connectors.
In a chat
Use +, then Connectors, to turn Origamy on or off for that conversation.
ChatGPT
OpenAI offers custom MCP servers on ChatGPT Business, Enterprise and Edu, on the web. An admin or owner usually adds it.
- Go to Plugins, choose the + button, then Add custom MCP server.
- Name it Origamy and paste the URL under Connection.
- Choose OAuth for authentication.
- Read the risk warning and tick I understand and want to continue.
- Choose Create as a plugin, sign in, then install it.
- In a new chat, type @ and pick Origamy.
For the whole workspace
Only admins and owners can publish it for everyone. Until then it stays private to the people testing it.
If the menu looks different
OpenAI is moving this from Apps to Plugins, so older workspaces may show Settings → Apps → Create instead.
Cursor
Add this to ~/.cursor/mcp.json for all your projects, or .cursor/mcp.json for one.
{
"mcpServers": {
"origamy": {
"url": "https://mcp.origamy.io/mcp"
}
}
}
Cursor then asks you to sign in. No client ID is needed, because it registers itself.
Claude Code
Run this in your terminal. Add --scope user to use it in every project.
$ claude mcp add --transport http origamy https://mcp.origamy.io/mcp
Then run /mcp inside Claude Code and follow the browser sign-in.
VS Code
For GitHub Copilot's agent mode.
- Open the Command Palette and run MCP: Add Server.
- Choose HTTP (HTTP or Server-Sent Events) and paste the URL.
- Enter origamy as the server ID.
- Choose Global for your own use.
- Confirm the trust prompt and sign in when the browser opens.
Any other MCP app
Look for "remote MCP server" or "custom connector" in its settings and give it these details.
Apps that only run local servers need a bridge to reach a remote one, and we haven't tried any.
We have tested this end to end with Claude. The others follow the same standard but haven’t been tried against Origamy yet, and their steps come from each vendor’s help pages, which change. If one doesn’t connect, tell us.
You pick the workspace,
and what it may do
Your app opens Origamy in your browser. Choose one workspace and the permissions, then choose Allow. It can’t do more than your own role allows, and each connection covers a single workspace.
Disconnect any time under Settings → Connected apps. The app’s next call fails, and it has to be connected again. Owners and admins can see and disconnect every app connected to the workspace.
What it
can’t do
No personal data
There is no setting that opens it up. When your app needs to see what a person looks like, it gets made-up people shaped like your audience, with test contact details that can’t receive anything.
It can’t message your contacts
No tool sends anything. A journey only starts when someone on your team turns it on in Origamy.
Everything lands off
Journeys and reports stay off, templates stay drafts and forms stay unpublished. Publishing a form takes its own permission, which is off unless you tick it.
Plan first, then apply
Your app has to plan before it saves. Plans that don’t pass the checks are refused with the reason, and it can’t change anything a live journey is using.
Text is treated as data
Words people typed, such as a template body, come back marked as untrusted, and your app is told never to follow instructions inside them.
Every call is recorded
We log the app, the person, the tool and the result for each call, and limit how fast a connection can call.
The tools
it gets
Nineteen tools, shaped around the job rather than one for every screen. The guide explains each one.
Read your setup
- get_workspace_overview
- search
- fetch
- list_segments
- get_segment
- list_templates
- get_template
- list_forms
- get_form
- list_workflows
- get_workflow
- list_reports
- list_teams
People’s shape
- get_people_schema
- sample_people
Field names and made-up people. Never real values.
Build
- plan_changes
- get_changeset
- apply_changeset
- publish_form
Segments, templates, forms, journeys, teams and reports.
Connect it, then ask it
what’s in your workspace
On every plan for now · uses your AI app’s own plan for the thinking