MCP Server

SuperPrompts is a hosted Model Context Protocol server. Add it to Claude Code, Cursor, Claude Desktop, VS Code or any MCP client and your agent can read and edit the prompts in a project without leaving the conversation.

Endpoint

https://superprompts.app/api/v2/mcp

Transport is Streamable HTTP. Every request is self-contained, so there is no session to establish, keep alive or reconnect. Authenticate with a project API key (Project → Settings → API) in the x-api-key header or as Authorization: Bearer. The key scopes the server to that project. The endpoint is versioned with the REST API; see API versions.

Claude Code

claude mcp add --transport http superprompts https://superprompts.app/api/v2/mcp \
  --header "x-api-key: sp_YOUR_PROJECT_KEY"

Then ask for what you want in plain language: “Show me the production version of the support prompt”, “Tighten the refund rule and publish it”, “Create a new prompt for onboarding emails from this markdown”.

Cursor, Claude Desktop, VS Code

Add this to the client's MCP configuration (for Cursor: .cursor/mcp.json; for Claude Desktop: claude_desktop_config.json; for VS Code: .vscode/mcp.json with "servers" instead of "mcpServers").

{
  "mcpServers": {
    "superprompts": {
      "url": "https://superprompts.app/api/v2/mcp",
      "headers": { "x-api-key": "sp_YOUR_PROJECT_KEY" }
    }
  }
}

Tools

list_prompts

Every prompt in the project, with production and latest version hashes.

get_prompt

Read a prompt: assembled text, sections, tools, detected {{variables}}. Accepts version ("production", "latest" or a hash) and variables to compile.

create_prompt

Create a prompt from sections or markdown. Optionally publish the first version.

update_prompt

Save a new version from sections or markdown with a commit message. Identical content returns the existing version. Optionally publish.

publish_prompt

Point production at a version: a hash, a unique prefix, or "latest".

What a session looks like

> Which prompts do we have in this project?
  list_prompts → Support agent (production 8481c55), Onboarding email (unpublished)

> Read the production support prompt.
  get_prompt { prompt_id, version: "production" }

> Refunds should be escalated, not refused. Update the Rules section and publish.
  update_prompt { prompt_id, sections: [...], message: "escalate refunds", publish: true }
  → version 9f2a1c0 is now production

Every change made through MCP shows up in History with its message, and can be rolled back from the dashboard or with publish_prompt.

Notes

Reads through MCP do not append Prompt Guard by default, so the agent sees exactly what you wrote. Pass guard: true to see the served text.
The same per-organization rate limit applies as for the REST API (60 requests per minute on Free, none on Pro).
Treat the key like a password. Anyone with it can publish to production for that project. Failed authentication is throttled per client, and Host and Origin headers are validated against this deployment. See Security.