> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stage.systems/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Claude and other apps

> Let Claude, Cursor or a script work on your site through the Stage MCP — edit content, read analytics, run campaigns — with the same permissions you have.

Stage speaks [MCP](https://modelcontextprotocol.io), 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

<Steps>
  <Step title="Add the connector">
    In Claude (web or desktop): **Settings → Connectors → Add custom connector**, and enter
    `https://api.stage.systems/mcp`.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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 …"
  </Step>
</Steps>

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

| Ask about | The app can |
| - | - |
| Content | list pages, read any page, article or global, search for text, change fields, add and remove list items and sections, create pages and articles, publish or schedule an article |
| Media | browse the library, add an image or video from a public link, upload a file from your computer (Claude Code and Cursor run the upload for you; in claude.ai share the file with a link instead) |
| Publishing | publish the site (it will ask you first) |
| Analytics | the overview, per-section numbers, funnels, A/B tests, signups |
| Inbox | who wrote in and what they said |
| Campaigns | list, read, create and schedule posts, request approval, approve (publishers), the tracked link, metrics, replies |
| Bookings | services, schedules, who booked |

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.

```bash theme={null}
claude mcp add --transport http stage https://api.stage.systems/mcp \
  --header "Authorization: Bearer stg_live_…"
```

## 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".


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.