Set up Site Audit in Claude Code

Before you start

• Claude Code installed (we tested version 2.1.268).
• A ToolCargo account and an API key with the Site Audit scope — create one on the dashboard. The key is shown once.

Set it up

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

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

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

Replace YOUR_API_KEY with your key. Don't commit keys to a repository — the .mcp.json form reads it from an environment variable.

Check it works

1. Start claude and run /mcp: toolcargo-site-audit should show as connected with 4 tools.
2. Ask: “Audit https://example.com with ToolCargo.” You should get an outcome line, counts and findings, and — because you're signed in — a link to the saved report.

Your dashboard shows each step as it happens: account created, AI client connected, first tool call completed.

If something goes wrong

401 or “failed to connect”

The key is wrong, revoked or missing the Site Audit scope. Create a new key and re-run the add command (remove the old server first with claude mcp remove toolcargo-site-audit).

The tools don't appear

Check the URL ends in /mcp/site-audit and the transport is http. Restart Claude Code after adding.

“Monthly limit reached”

You've used this month's calls. They reset on the 1st (UTC); refused URLs and our errors aren't counted.

More in troubleshooting, or contact support.

Remove it

claude mcp remove toolcargo-site-audit, then revoke the key on the dashboard.