Skip to main content
Create a Blueprints API key in the app, store it as a local secret, then add the MCP server to your client.

​
Requirements

  • A Blueprints account with API key access
  • A bp_ API key created in the app with the scopes your workflow needs
  • An MCP client that supports remote HTTP servers and custom headers
Keep the API key in an environment variable, client secret store, or uncommitted local config. Do not paste it into prompts, shell history, synced editor settings, or checked-in dotfiles. For read-only MCP use, grant blueprints:read. For blueprint authoring, add blueprints:write. For deploy and stop tools, add blueprints:deploy. MCP clients do not need key-management scopes.

​
Claude Code

read -s BLUEPRINTS_API_KEY
claude mcp add --transport http blueprints https://mcp.useblueprints.ai/mcp --header "Authorization: Bearer $BLUEPRINTS_API_KEY"

​
Cursor

Use your client’s secret-management support where available. If your client requires a plain JSON config, keep the file local and uncommitted. 
{
  "mcpServers": {
    "blueprints": {
      "url": "https://mcp.useblueprints.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${BLUEPRINTS_API_KEY}"
      }
    }
  }
}

​
OpenCode

{
  "mcp": {
    "blueprints": {
      "type": "remote",
      "url": "https://mcp.useblueprints.ai/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer ${BLUEPRINTS_API_KEY}"
      }
    }
  }
}

​
Verify the connection

After connecting, ask your client to list your Blueprints MCP tools or call list_blueprints. If the client reports authentication errors, confirm that:
  • The header starts with Authorization: Bearer.
  • The key starts with bp_.
  • The key has not been revoked.
  • The key has the required scope for the tool you asked the client to call.
  • The account that created the key still has access to Blueprints.

​
First prompt

After the connection works, start with a narrow read-only request: 
List my Blueprints blueprints and summarize their current status. Do not edit or deploy anything.
Then move into edits only after the client has identified the target blueprint and described the intended tool calls.