Connect SiteGuru to your AI with MCP

The SiteGuru MCP server lets you connect your SiteGuru data straight to your AI assistant. Instead of opening reports, you can ask Claude things like "What should I fix first on my site?" and it pulls the answer from your live SiteGuru data and explains it in plain English.

This guide walks you through getting a key and connecting it to Claude Code and Claude Desktop.

What you can do with it

Once connected, you can ask your AI assistant about any site in your account. A few examples:

• "What should I fix first on example.com?" This gets your prioritised to-do list, the same "what to do next" guidance you see in SiteGuru.
• "Which pages on example.com are missing a meta description, or have a title that's too long?"
• "Is example.com fully indexed? Which pages aren't?"
• "Give me a summary of the biggest SEO issues on example.com and how to fix them."

Because your AI assistant can combine this with everything else it knows, you can go further, for example asking it to draft new meta descriptions for the pages that are missing one, or to turn your to-do list into a prioritised plan.

What you'll need

Who can use it

Access is tied to your account: a key can reach exactly the sites you can access in SiteGuru, and nothing else. Access is checked on every request, so if a site is later removed from your account, the key can no longer reach it.

What data is available today

Right now the MCP gives your AI assistant access to your audit data:

• Your prioritised to-do list (what to fix next)
• Indexation status
• On-page reports: page titles, meta descriptions, headings, image alt text, structured data, canonical URLs and page speed

Keyword and performance data are coming soon. We'll update this article when they're available.

Step 1: Create your MCP 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. For security it's stored hashed, so we can't show it again. If you lose it, just revoke it and create a new one.

On the same page you'll find your Server URL:

https://mcp.siteguru.co/mcp

You'll need both the key and the Server URL in the next step.

Step 2: Connect your AI tool

You can connect any tool that supports remote MCP servers. Below are the steps for Claude Code and Claude Desktop. In both cases your key is sent as a Bearer token.

Claude Code

Run this command in your terminal, replacing YOUR_KEY with the key you just created:

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

That's it. Start (or restart) Claude Code and ask it something about your site to confirm it's connected.

Claude Desktop

Claude Desktop connects to the MCP server through your claude_desktop_config.json file.

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

1. Open Claude Desktop and go to Settings → Developer → Edit Config. This opens (or creates) claude_desktop_config.json.
   • On macOS the file lives at ~/Library/Application Support/Claude/claude_desktop_config.json
   • On Windows it's at %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, just 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.

Step 3: Ask your first question

To check everything works, ask your assistant:

Which sites do I have in SiteGuru?

It should list the sites on your account. Then try:

What should I fix first on example.com?

(replacing example.com with one of your own sites). Your assistant will fetch your to-do list and walk you through the top issues. The first time it uses the connection, your AI tool may ask you to approve the SiteGuru tools, allow them to continue.

Some inspiration: more questions

Getting oriented

• Which sites can I check with SiteGuru?
• What should I work on first for example.com?

Audit a specific page

• What's wrong with my homepage on example.com?"
• Give me a full audit of /pricing on example.com: title, H1, meta description, everything.

Find specific problems across the whole site

• Which pages on example.com are missing a meta description?
• Show me every page with its H1. I want to see which ones are missing or duplicated.
• Are there any broken internal links on example.com?
• Show me canonical URL issues on example.com, anything pointing to a redirect or 404?

Indexation, Google, and the sitemap

• Which pages on example.com are not indexed by Google?
• Is my sitemap healthy? Any URLs in it that 404 or redirect?

Page speed

• How fast are my pages on example.com? Show me the slowest ones first.

Backlinks

• Give me a backlink overview for example.com: total backlinks, referring domains, spam score.
• Which backlinks have a high spam score or are broken? Anything I should worry about?

Site-wide technical checks

• Run all the site-wide technical checks on example.com. SSL, robots.txt, 404 handling, all of it.

Managing your keys

You can create a separate key for each tool you connect, which makes it easy to revoke one without affecting the others. On the API access page you can see when each key was last used and revoke any key you no longer need.

If you think a key has been exposed, revoke it straight away and create a new one. Revoking takes effect immediately.

Troubleshooting

• SiteGuru isn't showing up / the tools aren't available. Fully restart your AI tool after connecting. For Claude Desktop, make sure Node.js is installed and your claude_desktop_config.json is valid JSON (a missing comma will stop all servers from loading).
• Authentication or "unauthorized" errors. Your key is probably wrong or has been revoked. Create a new key on the API access page and update your config.
• "No sites found" or a site can't be reached. A key only reaches the sites on its owner's account. Check you're using the key from the right account, and that the site is still in your account.
• Claude Desktop connects but immediately drops. Double-check the env / Authorization:${SITEGURU_AUTH} setup above, the space in Bearer YOUR_KEY needs to live in the environment variable, not on the --header line.

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