Connect SiteGuru to Claude Code & Claude Desktop

This guide connects your SiteGuru data to Claude (Claude.ai and Claude Desktop) and to Claude Code, so you can ask Claude what to fix on your site and it answers from your live SiteGuru data. New to the SiteGuru MCP? Start with the MCP overview for what it does and what you'll need.

You need a SiteGuru plan that includes MCP access, and your SiteGuru Server URL:
https://mcp.siteguru.co/mcp

There are two ways to connect. The one-click method is easiest and stores no secret; the API key method is handy for Claude Code, CI or scripting.

Option A: One-click connection (recommended)

Claude Desktop and Claude.ai

1. Open Settings → Connectors and choose Add custom connector. 
   
2. Paste the SiteGuru Server URL https://mcp.siteguru.co/mcp and click Add. Don't fill out the fields under Advanced Settings.
3. Claude opens a SiteGuru page in your browser. You're already signed in, so just click Allow to approve access to your SEO data.
4. SiteGuru now appears as a connected tool. Enable it in a chat and ask away.

Claude Code

Run this in your terminal:

claude mcp add --transport http siteguru https://mcp.siteguru.co/mcp

Claude Code opens your browser to sign in to SiteGuru and click Allow. Once approved, the connection is ready, no key required. Ask Claude Code something about your site to confirm.

Option B: Connect with an API key

Prefer a key, or using a setup that doesn't support the one-click flow? You can connect with a personal key instead.

Step 1: Create your key

In SiteGuru, open Account settings → API access. Click Create key, give it a name (for example "Claude Desktop"), and copy the key straight away. Your key is shown only once, so if you lose it, revoke it and create a new one.

Claude Code (with a key)

Replace YOUR_KEY with the key you created:

claude mcp add 
--transport http siteguru https://mcp.siteguru.co/mcp 
--header "Authorization: Bearer YOUR_KEY"

Claude Desktop (with a key)

Claude Desktop connects through your claude_desktop_config.json file.

Before you start: Claude Desktop needs Node.js installed, as it uses the mcp-remote helper to reach remote servers.

1. Open Claude Desktop and go to Settings → Developer → Edit Config. This opens (or creates) claude_desktop_config.json.
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
2. Add a siteguru entry under mcpServers, replacing YOUR_KEY with your key:

{
  "mcpServers": {
    "siteguru": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.siteguru.co/mcp",
        "--header",
        "Authorization:${SITEGURU_AUTH}"
      ],
      "env": {
        "SITEGURU_AUTH": "Bearer YOUR_KEY"
      }
    }
  }
}

Why the key is in env: the Bearer token contains a space, and passing it directly on the --header line can break the connection. Putting Bearer YOUR_KEY in an environment variable and referencing it as Authorization:${SITEGURU_AUTH} avoids that. If you already have other servers under mcpServers, add the siteguru block alongside them.

3. Save the file and fully restart Claude Desktop (quit and reopen, don't just close the window).

SiteGuru will now appear as a connected tool in Claude Desktop.

Ask your first question

To check the connection, ask Claude:
Which sites do I have in SiteGuru?

Then try
What should I fix first on example.com?
(using one of your own sites).
The first time it uses the connection, Claude may ask you to approve the SiteGuru tools, allow them to continue. For more prompt ideas, see the MCP overview.

Managing the connection

One-click connections can be removed any time from Settings → Connectors in Claude. If you connected with an API key, revoke it on the SiteGuru API access page, revoking takes effect immediately.

Troubleshooting

• SiteGuru isn't showing up. Fully restart Claude after connecting. For Claude Desktop, make sure Node.js is installed and your claude_desktop_config.json is valid JSON, a missing comma stops all servers loading.
• "MCP access isn't included in your plan" on the Allow screen. The MCP server needs a plan that includes MCP access. Upgrade and reconnect.
• Authentication or "unauthorized" errors. For one-click, reconnect and click Allow again. For a key, it's probably wrong or revoked, create a new one and update your config.
• "No sites found." A connection only reaches the sites on its owner's account. Check you're using the right account, and that the site is still in your account.
• Claude Desktop connects but immediately drops (key method). The space in Bearer YOUR_KEY must live in the env variable, not on the --header line, see the config above.

Still stuck? Get in touch and we'll help you get connected.