Skip to main content
Stage speaks MCP, the open protocol AI apps use to work with tools. Connect an app once and it can read and change your site on your behalf: edit copy, add items to a list, draft an article, read this month’s numbers, schedule a post. Everything an app does runs as you, only on the sites you chose, and can never do more than your role allows. What it saves is not live until someone publishes.

​
Connect Claude

1

Add the connector

In Claude (web or desktop): Settings → Connectors → Add custom connector, and enter https://api.stage.systems/mcp.
2

Sign in and choose the sites

Claude opens the Stage sign-in. Use your normal Stage login, pick the sites (or All sites), and turn off anything the app should not be able to do. Allow.
3

Ask

“What are the top pages this month?” · “Change the hero headline on the home page to …” · “Add a card to the services list called …” · “Draft an article about …” · “Schedule a post for Tuesday 9am saying …”
Claude Code and Cursor work the same way: add https://api.stage.systems/mcp as an HTTP MCP server and sign in when prompted.

​
What it can do

It only sees the tools your site and role allow — a viewer’s connection cannot edit, and an org without the Campaign tool shows no campaign tools.

​
Scripts and automations: API keys

For Claude Code, a script or CI, an admin creates an API key in Settings → Apps & API: a name, a role ceiling, and the scopes it may use. The key is shown once. It acts as the person who made it, on this site only, and dies with their membership.

​
See and cut connections

Settings → Apps & API lists the apps connected to the site and the keys that exist. You can disconnect any app you connected yourself; admins can disconnect anything and revoke keys. Every change an app makes shows in the activity log as “you, via MCP”.