Scripe in Claude, ChatGPT and Cursor.
Connect once and ask from the chat: which outliers fit our positioning, draft this for the founder, what did last week do. More than a hundred actions, the same permissions as in the app.
Connected in a minute.
Three steps in Claude, ChatGPT or Cursor. Your assistant runs the sign-in for you.
- 01
Copy the server URL
https://mcp.scripe.io/mcp, the same address for every assistant and every workspace.
- 02
Add it to your assistant
In Claude or ChatGPT, add it as a custom connector. In Cursor, add it to your MCP servers.
- 03
Sign in and choose access
Approve Scripe's consent screen with read-only or full access. Your assistant starts in your default workspace and can switch to any other you can open.
Every part of Scripe, from where you work.
The MCP server, the public API and webhooks expose the same system the app runs on: ideas, posts, media, the knowledge base, the calendar and the numbers.
Your own workflows on the public API.
Create ideas, drafts and media, read the knowledge base and the numbers, schedule posts, from your own code. Versioned, scoped by API key, documented at scripe.io/developers.
When something happens in Scripe, tell anyone.
A post goes live, an idea is written, a review is approved: a webhook fires, and Zapier, n8n or your own endpoint takes it from there. A Slack message, a Notion row, a CRM note.
Create, read, update and delete every part of Scripe.
The same actions the Scripe Agent has in the app, available to your assistant and your code.
Search the outliers
Posts by topic that beat their author's own average, with the evidence behind them.
Ideas
List, create, update and schedule ideas; generate ideas from any text.
Posts
Draft, edit, schedule and publish, within the workspace's review rules.
Media
Generate carousels and images in the brand kit; attach them to posts.
Knowledge base
Add, read and delete documents; read and update the positioning.
Analytics
Impressions, engagement and clicks per post and profile, and across workspaces.
Read-only or full access. Your choice at connect time.
Connecting an assistant shows one consent screen with one choice. Read-only gives the requested read scopes; full access includes writing, publishing and settings. The connection acts with your account and sees what you see in Scripe.
DocumentationScopes
Every API key and connection carries explicit scopes; a write needs a write scope.
OAuth
Assistants connect through OAuth; keys are minted in the workspace's developer settings.
Your account
The connection reads and writes as you, in the workspaces and profiles you can open.