Admin MCP

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

Looking to build, edit, and publish apps conversationally from tools like Claude and Slack? See the Builder MCP. The Admin MCP on this page is for administering your org from AI coding agents.

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.

Cursor
Claude Code
Other MCP clients

Click 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>"
      }
    }
  }
}

Run this command in your terminal:

claude mcp add --transport http \
  --header "Authorization: Bearer <superblocks-access-token>" \
  superblocks https://app.superblocks.com/mcp

Point your MCP client at the following URL with an Authorization header:

URL: https://app.superblocks.com/mcp
Header: Authorization: Bearer <superblocks-access-token>

What can the MCP server do?

Once connected, AI agents can use the following capabilities through natural language:

Category	Examples
Applications	List apps, view structure, check commit history, deploy, undeploy
Integrations	List, create, update, and delete integrations
Access control	View and manage application, workflow, and job permissions
Role management	Assign and update org-level roles for users and groups
Organization	View org summary, list members, manage builder seats
Folders	Create, update, and delete folders
Audit	Query audit events and compute aggregated metrics
Chat history	Retrieve Clark AI conversation history for any application
Billing	View plan summary and usage
Knowledge	List 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.

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>

Install the MCP server

Run the setup command for your IDE:

Cursor
Claude Code
Other MCP clients

npx -y @superblocksteam/mcp-server setup --client cursor

This writes the MCP server configuration to ~/.cursor/mcp.json.

npx -y @superblocksteam/mcp-server setup --client claude

This writes the MCP server configuration to ~/.claude.json.

npx -y @superblocksteam/mcp-server setup

This prints the JSON configuration to stdout. Copy it into your MCP client’s configuration file.

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

Hosted server: authentication errors

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.

Local server: not connecting

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.

Local server: authentication errors

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

Local server: Node.js version requirements

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.

Org administration

Governance

Billing

Superblocks on AWS

Quickstart

What can the MCP server do?

Alternative: Local MCP server

Troubleshooting

​Quickstart

​What can the MCP server do?

​Alternative: Local MCP server

​Troubleshooting

Quickstart

What can the MCP server do?

Alternative: Local MCP server

Troubleshooting