MCP Integration
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:
Go to app.superclaws.io and sign in with your email and password.
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.
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.
Setting Up Claude Desktop
Claude Desktop uses a local config file to know which MCP servers to connect to.
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.
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"
]
}
}
}
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.
Setting Up ChatGPT
ChatGPT supports MCP servers through its Connectors settings. This is currently available on the ChatGPT desktop app and some web plans.
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.
Click Add MCP server and enter:
- Server URL:
https://api.superclaws.io/mcp - Authorization: Bearer token — paste your Bridge API Key
Setting Up Cursor
Cursor has built-in MCP support accessible from its settings panel.
Go to Cursor Settings → MCP → Add new MCP server.
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"
]
}
}
}
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.
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:
| Tool | What it does |
|---|---|
clawbox_files_list | List files in your ClawBox storage — supports search and pagination |
clawbox_file_read | Read the contents of a specific file by name or ID |
clawbox_file_write | Write or overwrite a file in ClawBox (text or base64-encoded content) |
clawbox_file_delete | Delete a file from ClawBox by ID |
tools_list | List all tools available in your connected toolkit |
tools_search | Search your toolkit by keyword or use-case |
fi_balance | Get account balances for connected financial accounts |
fi_transactions | Query recent transactions with optional date and amount filters |
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-idresponse 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
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.