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.

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. The hosted server runs at https://{tenant}.superblocks.com/mcp. Replace {tenant} with the value for your instance from Instance URLs.

Cursor
Claude Code
Other MCP clients

Click the button to install, then replace YOUR_TOKEN with your API token in Cursor Settings > MCP. The button installs the Cloud US server; on Cloud EU or a Cloud-Prem instance, also change the URL to https://{tenant}.superblocks.com/mcp.Or add it manually:

{
  "mcpServers": {
    "superblocks": {
      "url": "https://{tenant}.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://{tenant}.superblocks.com/mcp

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

URL: https://{tenant}.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
Supply chain	Fetch an app’s SBOM, find apps by package, list npm packages across the org
Code security	Read fleet CVE findings, check packages before install, list accepted advisories
Policy agents	List policies, read run history and findings, check publish gates
Knowledge	List and view Knowledge entries
Superblocks Database	Read-only view of your Superblocks Database estate: summarize databases, instances, and pools per data tag (`get_app_databases_overview`), list every app database with its application, state, and host (`list_app_databases`), list cluster pools and their provisioning runs (`list_app_database_pools`, `get_app_database_pool_provisioning_run`), and check whether an app’s database can run on every data tag (`get_application_database_compatibility`). Requires `app_databases:manage` except for the compatibility check. Application listings and summaries also report whether each app has a database, and integration listings flag the ones a database owns

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@beta 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@beta setup --client cursor

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

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

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

npx -y @superblocksteam/mcp-server@beta 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

On Cloud EU or a Cloud-Prem instance, run superblocks config set domain {tenant}.superblocks.com before superblocks login. See Instance URLs for your {tenant} value. Use --dry-run to preview the configuration without modifying any files:

npx -y @superblocksteam/mcp-server@beta 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@beta --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@beta 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 {tenant}.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