MCP

MCP is at https://api.scaledpapers.com/mcp. An owner or admin creates one key on API Keys and exports it as SP_API_KEY. The agent then uses that workspace’s checks, status pages, components, incidents, maintenance windows, Slack connection, and existing alert destinations. Creating and revoking the key still happens in the console. The same key works with Call the API and the Status API.

Do not paste the raw key into a project config file. The snippets below read SP_API_KEY from the environment. An agent should follow the setup prompt and run these steps itself.

Install the skill

npx skills add ScaledPapers/skills --skill scaledpapers -a claude-code -a codex -g -y

That installs the same instructions into Claude Code and Codex. The source is https://github.com/ScaledPapers/skills. The catalog page is https://www.skills.sh/scaledpapers/skills/scaledpapers. Cursor loads that repo as a plugin. The key is still created in the console.

Codex only

npx skills add ScaledPapers/skills --skill scaledpapers -a codex -g -y
bash ~/.agents/skills/scaledpapers/scripts/wire-mcp.sh codex
export SP_API_KEY=sp_…

Reload Codex if MCP tools do not appear. Then ask it to call usage.

Connect

1. Create a key. Copy the secret once.
2. Export it in the shell you use for the editor: export SP_API_KEY=sp_…
3. Wire MCP. After the skill is installed, run bash ~/.agents/skills/scaledpapers/scripts/wire-mcp.sh with cursor, claude, or codex. The script merges config idempotently. Or add the server manually for one of these clients.

Cursor (~/.cursor/mcp.json or .cursor/mcp.json):

{
  "mcpServers": {
    "scaledpapers": {
      "url": "https://api.scaledpapers.com/mcp",
      "headers": { "Authorization": "Bearer ${env:SP_API_KEY}" }
    }
  }
}

Claude Code:

claude mcp add --transport http scaledpapers https://api.scaledpapers.com/mcp \
  --header "Authorization: Bearer ${SP_API_KEY}"

Codex (~/.codex/config.toml):

[mcp_servers.scaledpapers]
url = "https://api.scaledpapers.com/mcp"
bearer_token_env_var = "SP_API_KEY"

claude.ai and Claude Desktop custom connectors are not supported. They expect OAuth, and this server takes the bearer key.

What the agent can do

Ask it to watch the health URLs in the repo. It can list and create checks (HTTP, API, DNS, and TCP), pause or delete a check, run a probe, and create or update a public status page. It can open incidents, post updates, schedule maintenance, start or disconnect Slack (you open the returned URL), and attach alert destinations that already exist.

Cursor enables at most 40 MCP tools across all servers. This server uses 31.

Maintenance tools default notify_subscribers to false. The REST API defaults it to true when a public component is included. Tell the agent when a window should email subscribers.

A private-page password you type into the chat is stored in the agent transcript. Set that password on Page settings if you do not want it in the chat.

What stays in the console

Team invites and roles, creating and revoking API keys, billing, creating or deleting alert destinations, deleting an incident, and visitor subscribers stay in the console. The agent can use a destination after you create it, and it can test one.