Docs · Updated 2026-09-11

Client setup

ToolCargo servers use MCP's Streamable HTTP transport. Any client that supports remote servers with a header or OAuth can connect.

The examples use the Site Audit server URL https://toolcargo.com/mcp/site-audit. Replace YOUR_API_KEY with a key from your dashboard. Never commit a key to a repository; use environment variables where the client supports them.

Client	Auth	Status
Claude Code	API key	Tested by us
Claude (claude.ai)	OAuth	Tested by us
Cursor	API key	Documented, not yet tested by us
VS Code (Copilot agent mode)	API key	Documented, not yet tested by us
ChatGPT (developer mode)	OAuth	Documented, not yet tested by us
MCP Inspector	API key	Tested by us

Claude Code — tested ✓

Run this once in a terminal. It adds the server for your user across projects.
Start `claude` and run `/mcp` to confirm it shows as connected.

terminal

claude mcp add --transport http --scope user toolcargo-site-audit https://toolcargo.com/mcp/site-audit \
  --header "Authorization: Bearer YOUR_API_KEY"

.mcp.json (project, key read from the environment)

{
  "mcpServers": {
    "toolcargo-site-audit": {
      "type": "http",
      "url": "https://toolcargo.com/mcp/site-audit",
      "headers": {
        "Authorization": "Bearer ${TOOLCARGO_API_KEY}"
      }
    }
  }
}

Claude (claude.ai & Desktop) — tested ✓

Open Settings → Connectors → Add custom connector.
Name it toolcargo-site-audit and paste the server URL below. Leave the OAuth client fields empty.
Click Connect. You'll be sent to ToolCargo to sign in and approve access; no API key is needed.
Custom connectors are available on plans where Anthropic enables them; on Team/Enterprise an owner may need to add it.

server URL

https://toolcargo.com/mcp/site-audit

Cursor — not yet tested

Add this to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
Set TOOLCARGO_API_KEY in your environment, or paste the key in place of the variable.

mcp.json

{
  "mcpServers": {
    "toolcargo-site-audit": {
      "url": "https://toolcargo.com/mcp/site-audit",
      "headers": {
        "Authorization": "Bearer ${env:TOOLCARGO_API_KEY}"
      }
    }
  }
}

VS Code (Copilot agent mode) — not yet tested

Add this to .vscode/mcp.json. VS Code prompts for the key once and stores it securely.

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "toolcargo-key",
      "description": "ToolCargo API key",
      "password": true
    }
  ],
  "servers": {
    "toolcargo-site-audit": {
      "type": "http",
      "url": "https://toolcargo.com/mcp/site-audit",
      "headers": {
        "Authorization": "Bearer ${input:toolcargo-key}"
      }
    }
  }
}

ChatGPT (developer mode) — not yet tested

Enable developer mode in ChatGPT settings (available on some paid plans).
Create a connector with the server URL below and choose OAuth. ChatGPT cannot send API keys.

server URL

https://toolcargo.com/mcp/site-audit

MCP Inspector — tested ✓

Useful for testing tool calls directly, without an assistant.

terminal

npx @modelcontextprotocol/inspector --cli https://toolcargo.com/mcp/site-audit \
  --transport http --header "Authorization: Bearer YOUR_API_KEY" \
  --method tools/call --tool-name audit_page --tool-arg url=https://example.com

Other clients

Clients that only support local (stdio) servers can use the open-source mcp-remote bridge, which runs locally and forwards to the remote URL:

config

{
  "mcpServers": {
    "toolcargo-site-audit": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://toolcargo.com/mcp/site-audit",
        "--header",
        "Authorization:${TOOLCARGO_AUTH}"
      ],
      "env": {
        "TOOLCARGO_AUTH": "Bearer YOUR_API_KEY"
      }
    }
  }
}

We have not tested every client; if one fails, see troubleshooting and tell us via the request form.