Connect your AI agent to ScaleBop SEO

ScaleBop SEO runs an MCP server, so an AI agent such as Claude Code or Cursor can work with your SEO data directly. It is included in every plan.

Your agent can:

• list your sites and see each one’s audit score, open issues and connections;
• read the technical issues from your latest audit;
• read keyword rankings, with where each number came from;
• read Search Console clicks, impressions and position day by day, for the whole site, one page or one query;
• see what changed between your last two audits, what changed on your pages, and the notes and Google algorithm updates around a date, to work out why traffic moved;
• read AI-assistant checks and see which sites AI search cites for your topics;
• get a copy-paste fix for an issue, written for how your site is built (Lovable, Next.js, WordPress, Shopify and others);
• recheck a page once a fix is live, so the issue is confirmed fixed rather than assumed;
• see what the ScaleBop agent changed, ask it to run, and undo one of its changes.

Your agent can’t edit your site directly. Changes only happen through the ScaleBop agent, so your autopilot setting still decides what is applied.

1. Create a key

1. In ScaleBop SEO, open Settings → MCP (AI agents).
2. Under Create a key, give it a name (for example “Claude Code”) and choose the access:
   • Read only: the agent can read everything above and get fixes.
   • Read and run agent: it can also ask the ScaleBop agent to run and undo agent changes.
3. If the workspace has more than one project, choose All projects or Only some and tick the projects the key may use. To the agent, any other project doesn’t exist.
4. Choose Create key and copy the key. It starts with seo_live_ and is shown only once.

The page then shows the configs below with your key already filled in.

Only the workspace owner or a manager can create keys, because a key can read every project in the workspace unless you limit it. Treat it like a password.

2. Add it to your agent

The server URL is shown on the same page, with a copy button. For the hosted service it is https://seo.scalebop.com/mcp.

Claude Code

Run this in your terminal, replacing the key with yours:

claude mcp add --transport http scalebop https://seo.scalebop.com/mcp --header "Authorization: Bearer seo_live_YOUR_KEY"

Then restart Claude Code.

Cursor

Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to use it in every project:

{
  "mcpServers": {
    "scalebop": {
      "url": "https://seo.scalebop.com/mcp",
      "headers": {
        "Authorization": "Bearer seo_live_YOUR_KEY"
      }
    }
  }
}

Don’t commit this file with your key in it.

Other agents

Any MCP client that connects to a remote server over Streamable HTTP and can send a custom Authorization header works the same way. Clients that only connect with OAuth sign-in, such as ChatGPT connectors, aren’t supported yet.

3. Ask something

Try:

• “What should I fix first on my site?”
• “Give me the fix for the missing titles, for my stack.”
• “Which sites does AI search cite instead of mine?”
• “Why did traffic to the pricing page drop last month?”
• “I’ve fixed the missing title on the homepage. Check it worked.”
• “What did the ScaleBop agent change last week? Undo the title change on the pricing page.”

For step-by-step routines, see Agent recipes.

How the numbers are labelled

Each result says where its numbers came from and how old they are:

• A Search Console position is Google’s average across real searchers. A checked position is one result ScaleBop saw at one moment from one location. They measure different things, so a movement is only reported when both ends come from the same source.
• An AI-assistant check says whether the model searched the web or answered from memory. The citation landscape counts only answers where it searched, and says when the sample is too small to call.

Rechecking a page

After you or your agent deploy a fix, ask for a recheck of the page. ScaleBop fetches that one page (honouring your robots.txt) and runs the audit’s checks on it. Issues it no longer finds are marked fixed in your latest audit. Issues that need the whole site to confirm, such as duplicate titles, orphan pages or broken links, wait for the next full audit, and the result says which those are.

A recheck needs the project’s domain to be verified, works only on pages of that domain, and is limited to 30 per project per hour. If the page is erroring when it’s rechecked, nothing is marked fixed.

Running the agent

Run the agent follows your workspace’s autopilot setting. On the default, suggest, it proposes changes for you to approve and writes nothing to your site. The result always says which setting was in force.

When your workspace is read-only (for example, after a trial ends), your agent can still read everything, but running the agent and undoing changes are refused until you reactivate a plan.

Revoke a key

Open Settings → MCP (AI agents) and choose Revoke next to the key. Any agent using it is cut off straight away. Each key shows when it was last used.

Keys for all projects also work with the ScaleBop SEO public API. Keys limited to some projects work with MCP only.

Troubleshooting

• 401 Unauthorized: the key is missing, mistyped or revoked. Check the Authorization: Bearer seo_live_… header, or create a new key.
• Tools don’t appear: restart your agent. Most clients only read their server list at startup.
• “This API key is read-only”: create a key with Read and run agent access.
• “This workspace is read-only”: reactivate a plan in Settings → Billing.
• Project ids: tools take ids like prj_ABCDEFGHJKLM from the list of projects. Number ids are refused.
• 429 Too many requests: wait a minute and try again.
• “No project with id …” for a project you can see in the app: the key is limited to other projects. Create a key that includes it.
• 403 from the public API with a limited key: the public API needs a key for all projects.