ContextBolt SEO in GitHub Copilot (2026 Setup)

GitHub Copilot has two surfaces that speak MCP, and they are configured in completely different places. This page covers the cloud coding agent, the one you assign an issue to and that opens a pull request on its own. For SEO tools inside the editor, see the VS Code setup.

The cloud agent is the more interesting of the two for SEO, because it turns research into something that happens automatically as part of your workflow rather than something you remember to do.

What changes when the agent has SEO tools

Assign Copilot an issue that says “add a comparison page for X” and, without SEO tools, it writes whatever seems reasonable. With ContextBolt SEO connected, it can check what the page should target, look at who currently ranks, and write against real data before it opens the PR.

The pattern that pays off fastest is auditing inside pull requests. Point the agent at the pages a PR changed, have it run page_audit on each, and it leaves the findings as a review comment. SEO review stops being a separate task someone forgets.

The repository MCP configuration

The cloud coding agent needs the personal-URL compatibility method. Copy the full private URL from your ContextBolt SEO welcome email.

Open your repository, go to Settings, then Copilot under Code & automation in the sidebar, then Coding agent. The MCP configuration section takes a JSON block:

{
  "mcpServers": {
    "contextbolt-seo": {
      "type": "http",
      "url": "$COPILOT_MCP_CONTEXTBOLT_SEO_URL"
    }
  }
}

Store the full MCP URL as an agent secret rather than pasting it inline. The configuration supports secret and environment variable substitution drawn from the Agents secrets on the repository, using the same syntax style as GitHub Actions. Because your ContextBolt token lives inside the URL path, the whole URL is the thing worth protecting. Check GitHub’s current docs for the exact secret naming convention your organization expects, since the prefix requirements have shifted between releases.

You need repository admin rights to see this panel. On an organization-owned repository, confirm your org’s MCP policy allows third-party servers before adding one.

The OAuth limitation, and why it does not bite here

GitHub’s coding agent supports remote MCP servers but does not support servers that authenticate using OAuth. That rules out a number of hosted MCP services.

Use ContextBolt SEO’s personal-URL compatibility option here. Its token is in the URL path, so the cloud agent does not need an interactive sign-in. The shared OAuth URL on its own will not authenticate this connection. It is worth knowing this constraint if you are evaluating several SEO MCP servers at once, because it quietly disqualifies some of them from this surface.

The agent also supports MCP tools only, not resources or prompts. Every ContextBolt SEO capability is a tool, so nothing is missing.

Watch your first few sessions

An agent chaining research across a whole issue can spend more credits than a single question in an editor. Research tools cost one credit each, backlink tools cost three. Check the session logs on your first few tasks to learn what a typical issue costs, then size that against your 1,000 monthly credits.

The full tour of tools and workflows is in the ContextBolt SEO guide, and the background on how an SEO MCP server works sits alongside it.