MCP Integration

Connect any MCP-compatible AI client — Claude Desktop, ChatGPT, Cursor, VS Code, Windsurf, and others — to your SuperClaws agent. Once connected, your favourite AI tool can read files, send instructions, search your toolkit, and work with your financial data, all through a single authenticated endpoint.

What is MCP? MCP (Model Context Protocol) is an open standard that lets AI clients talk to external services in a structured way. Instead of copy-pasting information back and forth, your AI client can directly call SuperClaws tools — reading ClawBox files, checking balances, running searches — right inside the same conversation.

Why Use MCP?

Connecting via MCP means your AI client gets superpowers it wouldn't have on its own:

  • File access — read and list files in your ClawBox storage directly from a chat
  • Tool search — find the right automation tool from your connected toolkit without leaving the conversation
  • Financial insights — query account balances, transactions, and spending summaries (if you've connected financial accounts)
  • One key, any client — your Bridge API key works in every MCP client, so you don't need to manage separate integrations
  • Audit trail — every MCP session is logged in your dashboard so you can see exactly what connected and when

How to Get There

The MCP settings are inside your SuperClaws dashboard. Here's how to find them:

1
Log in to your dashboard

Go to app.superclaws.io and sign in with your email and password.

2
Open the MCP settings page

Click your profile icon in the top-right corner of any page, then select MCP from the dropdown menu. You can also navigate directly to app.superclaws.io/app/mcp.

3
Copy your Bridge API Key

Your Bridge API Key is shown at the top of the page. This is the credential you'll paste into your MCP client. Keep it private — anyone with this key can access your agent.

Regenerate if needed If you think your key has been exposed, click Regenerate Key on the MCP settings page. Your old key stops working immediately and a new one is issued. Any MCP clients using the old key will need to be updated.

Setting Up Claude Desktop

Claude Desktop uses a local config file to know which MCP servers to connect to.

1
Open your Claude Desktop config file

The file lives at different locations depending on your OS:

  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

If the file doesn't exist yet, create it. If it already has an mcpServers section, add to it rather than replacing the whole thing.

2
Paste the SuperClaws server entry

Copy the config snippet from your MCP settings page — it already has your API key filled in — and add it to the config file:

{
  "mcpServers": {
    "superclaws": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.superclaws.io/mcp",
        "--header",
        "Authorization: Bearer YOUR_BRIDGE_API_KEY"
      ]
    }
  }
}
3
Restart Claude Desktop

Quit and reopen Claude Desktop. After restarting, look for the hammer icon (🔨) at the bottom of the chat window — this confirms MCP tools are available. Click it to see the list of SuperClaws tools.

Example — once connected in Claude "List the files in my ClawBox and summarise the one called quarterly-report.pdf"

Setting Up ChatGPT

ChatGPT supports MCP servers through its Connectors settings. This is currently available on the ChatGPT desktop app and some web plans.

1
Open MCP settings in ChatGPT

In ChatGPT, go to Settings → Alpha → Alpha Features → MCP Servers. If you don't see this option, the feature may not yet be available on your account.

2
Add the server

Click Add MCP server and enter:

  • Server URL: https://api.superclaws.io/mcp
  • Authorization: Bearer token — paste your Bridge API Key
Can't find MCP settings? ChatGPT MCP support is rolling out gradually. If you don't see it in Settings, check back in a few weeks or use one of the other supported clients listed on this page.

Setting Up Cursor

Cursor has built-in MCP support accessible from its settings panel.

1
Open MCP settings in Cursor

Go to Cursor Settings → MCP → Add new MCP server.

2
Paste the config

Cursor uses the same mcpServers JSON format as Claude Desktop. Copy the snippet from your MCP settings page:

{
  "mcpServers": {
    "superclaws": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.superclaws.io/mcp",
        "--header",
        "Authorization: Bearer YOUR_BRIDGE_API_KEY"
      ]
    }
  }
}
3
Reload and verify

Cursor will pick up the change automatically. Start a new chat and ask it to list your available tools — it should include the SuperClaws set.

Example — once connected in Cursor "Search my toolkits for anything related to email and show me what's available."

Setting Up Other Clients

Any MCP client that supports HTTP/SSE transport will work. The SuperClaws MCP endpoint supports both the standard Authorization: Bearer header and the x-api-key header for clients that don't support custom auth headers natively.

VS Code (GitHub Copilot)

VS Code uses a different config format from Claude/Cursor. Add this to your settings.json (open it via Ctrl+Shift+P → Preferences: Open User Settings (JSON)) inside the "mcp" section:

{
  "mcp": {
    "servers": {
      "superclaws": {
        "url": "https://api.superclaws.io/mcp",
        "type": "http",
        "headers": {
          "Authorization": "Bearer YOUR_BRIDGE_API_KEY"
        }
      }
    }
  }
}

Windsurf

In Windsurf go to Settings → MCP → Add MCP Server and paste the same mcpServers config used for Claude/Cursor (shown in the Cursor section above). The config file lives at ~/.codeium/windsurf/mcp_config.json.

Perplexity

In Perplexity go to Settings → AI → Connectors → Add MCP server. Enter https://api.superclaws.io/mcp as the server URL, and add an Authorization header with the value Bearer YOUR_BRIDGE_API_KEY.

Any other client

For any other MCP client that supports HTTP or SSE transport:

  • Server URL: https://api.superclaws.io/mcp
  • Authentication: pass your Bridge API Key as Authorization: Bearer YOUR_BRIDGE_API_KEY
  • Protocol version: 2024-11-05

Available Tools

Once connected, your MCP client can call any of the following SuperClaws tools in conversation:

ToolWhat it does
clawbox_files_listList files in your ClawBox storage — supports search and pagination
clawbox_file_readRead the contents of a specific file by name or ID
clawbox_file_writeWrite or overwrite a file in ClawBox (text or base64-encoded content)
clawbox_file_deleteDelete a file from ClawBox by ID
tools_listList all tools available in your connected toolkit
tools_searchSearch your toolkit by keyword or use-case
fi_balanceGet account balances for connected financial accounts
fi_transactionsQuery recent transactions with optional date and amount filters
Your AI client decides which tools to use You don't need to name tools explicitly. Just describe what you want in plain English — "show me files uploaded this week" or "what's my current account balance?" — and the AI will figure out which tools to call.

Sessions & Security

Every time an MCP client connects to SuperClaws, a session record is created. You can view and manage active sessions from your MCP settings page.

  • Session ID — returned in the x-superclaws-mcp-session-id response header; clients that cache it avoid creating duplicate sessions
  • Last active — updated every time that session makes a request
  • Revoke — click Revoke next to any session to cut off that client immediately, without touching your API key
Keep your Bridge API Key private Your key grants access to your agent's files and tools. Don't share it, don't commit it to a public repository, and regenerate it if you think it's been compromised.

Troubleshooting

Tools not showing up in my client

Make sure your API key is pasted correctly with no extra spaces. Try opening a brand-new chat — some clients only load MCP tools at the start of a conversation. Also confirm you have Node.js installed if your client is using npx mcp-remote.

Getting an authentication error

Double-check the key on your MCP settings page — use the copy button to avoid typos. If you recently regenerated your key, update the config in every client you use.

File tool returns no results

Check your ClawBox — go to the ClawBox page in your dashboard to see what's there. If it's empty, upload a file and then try again from your MCP client.