Run Magister from Claude & ChatGPT

# Magister MCP — agent connection playbook

MCP server URL (remote, streamable HTTP): https://mcp.magistermarketing.com/mcp

## 1. Account (skip if the user already has one)
- POST https://magistermarketing.com/api/signup
  body: { "email", "team_name", "project_name", "website_url" }
  (GET the same URL to discover the field schema.)
- The response contains a signup_url. Have the user open it in a browser and
  finish with Google sign-in using the same email. The account, organization,
  brand, and verified website context are created only after sign-in succeeds.
  The link expires in 30 minutes.
- If self-serve signup is temporarily paused, a not_invited response means no
  signup link was created; tell the user signup is unavailable and stop.

## 2. Connect
- Claude Code: claude mcp add --transport http --scope user magister https://mcp.magistermarketing.com/mcp
- Codex: codex mcp add magister --url https://mcp.magistermarketing.com/mcp
- Cursor: merge this entry into ~/.cursor/mcp.json (global) or
  .cursor/mcp.json (project), then authenticate. Its public client id has no
  secret and uses PKCE. The config requests only read + audit:run; add any
  other scope explicitly before requesting it:
{
  "mcpServers": {
    "magister": {
      "url": "https://mcp.magistermarketing.com/mcp",
      "auth": {
        "CLIENT_ID": "magister-cursor-public-v1",
        "scopes": [
          "read",
          "audit:run"
        ]
      }
    }
  }
}
- If Cursor previously registered Magister with read only:
  After switching to this config or changing scopes, log out of the Magister server in Cursor's Tools & MCP settings, then reconnect. If Cursor still reuses an older OAuth session, run “Cursor: Clear All MCP Tokens” from the Command Palette and reconnect; that fallback also signs you out of other OAuth MCP servers.
- For another client, add a remote MCP server with the URL above in its
  connector or MCP settings. For Claude Desktop, merge this into
  claude_desktop_config.json and restart:
{
  "mcpServers": {
    "magister": {
      "url": "https://mcp.magistermarketing.com/mcp"
    }
  }
}

## 3. Authorize
- The client opens Magister's consent screen: the user picks an organization
  and scopes. Read tools are on by default; run/publish/send/spend scopes are
  opt-in, and money/live actions also require immediate confirmation in chat.
- OAuth consent cannot widen the scopes requested by the client. In Cursor,
  add a new run/write scope to auth.scopes and reconnect before requesting it.

## 4. Verify
- Call the list-projects tool. Most tools take a project_id from that list.
- Keep the first check read-only: get the brand profile, current plan, existing
  audit health, or existing AI-visibility results.
- Starting a fresh audit requires audit:run. Cursor's config above includes it;
  other clients must register that scope before requesting authorization.

## 5. Brands & organizations
- One connection covers the user's whole organization: list-projects returns
  every brand/client, and every tool takes a project_id — so switching brands
  is just referencing a different project in the same conversation.
- To work in a different ORGANIZATION, reauthorize the connector (client
  settings -> reconnect); the consent screen shows an organization picker when
  the user belongs to more than one. No reinstall — takes ~30 seconds.

MCP eligibility is confirmed for the selected organization at connection time.
Depending on the current Magister access policy, an active Connect or Agent
subscription may be required. If a tool needs an integration that isn't
connected, it returns a one-click connect link.