Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.superblocks.com/llms.txt

Use this file to discover all available pages before exploring further.

The Superblocks MCP server lets AI coding agents (Cursor, Claude Code, Windsurf, and others) interact with your Superblocks organization directly. Agents can list applications, manage integrations, deploy apps, manage access control, and more — all through the Model Context Protocol.

​
Quickstart

Connect to the hosted Superblocks MCP server — no install required. You’ll need your Superblocks API token, which you can find in Personal Settings > API Key.
Install MCP ServerClick the button to install, then replace YOUR_TOKEN with your API token in Cursor Settings > MCP.Or add it manually:
{
  "mcpServers": {
    "superblocks": {
      "url": "https://app.superblocks.com/mcp",
      "headers": {
        "Authorization": "Bearer <superblocks-access-token>"
      }
    }
  }
}

​
What can the MCP server do?

Once connected, AI agents can use the following capabilities through natural language:
CategoryExamples
ApplicationsList apps, view structure, check commit history, deploy, undeploy
IntegrationsList, create, update, and delete integrations
Access controlView and manage application, workflow, and job permissions
Role managementAssign and update org-level roles for users and groups
OrganizationView org summary, list members, manage builder seats
FoldersCreate, update, and delete folders
AuditQuery audit events and compute aggregated metrics
Chat historyRetrieve Clark AI conversation history for any application
BillingView plan summary and usage
KnowledgeList and view Knowledge entries

​
Alternative: Local MCP server

If you prefer to run the MCP server locally, you can use the CLI-based setup instead. This requires Node.js 22+ and an API token.
1

Authenticate

Run the following command, replacing <token> with your Superblocks API key. You can find your API key in Personal Settings.
npx -y @superblocksteam/mcp-server login --token <token>
2

Install the MCP server

Run the setup command for your IDE:
npx -y @superblocksteam/mcp-server setup --client cursor
This writes the MCP server configuration to ~/.cursor/mcp.json.
3

Restart your IDE

Restart your IDE to pick up the new MCP server configuration. You should see superblocks listed as a connected MCP server.
If you already have the Superblocks CLI installed, you can set up the local MCP server through it instead: 
superblocks login
superblocks mcp setup --client cursor
Use --dry-run to preview the configuration without modifying any files: 
npx -y @superblocksteam/mcp-server setup --client cursor --dry-run

​
Troubleshooting

Verify your API token is correct. You can find or regenerate it in Personal Settings > API Key.Make sure the Authorization header uses the Bearer prefix:
Authorization: Bearer sb_xxxxxxxxxx
If the token was recently regenerated, update it in your MCP client configuration and restart your IDE.
Verify the server starts correctly by running it directly:
npx -y @superblocksteam/mcp-server --help
If you see the usage text, the server is installed correctly. Restart your IDE and check that the MCP server appears in your IDE’s MCP server list.
Re-run the login command to refresh your token:
npx -y @superblocksteam/mcp-server login --token <token>
Your token is stored at ~/.superblocks/auth.json. You can verify it exists:
cat ~/.superblocks/auth.json
The local MCP server requires Node.js 22 or later. Check your version:
node --version
The hosted server at app.superblocks.com/mcp has no local requirements.