ContextBolt SEO in GitHub Copilot (2026 Setup)

Set it up in GitHub Copilot

Subscribe and get your MCP URL Use the personal-URL compatibility method for the cloud agent. Start a ContextBolt SEO trial or use your subscription. Your private MCP URL arrives by email and looks like https://seo.contextbolt.app/mcp/YOUR_TOKEN. Keep it private, like a password.
Store the URL as an agent secret In your repository settings, add an Agents secret holding your full MCP URL, named with the COPILOT_MCP_ prefix, for example COPILOT_MCP_CONTEXTBOLT_SEO_URL. Only Agents secrets and variables with that prefix reach the MCP configuration. Storing the URL rather than pasting it into the config keeps your token out of a settings screen your whole team can read.
Open the MCP configuration panel In the repository, open Settings, then under Code, planning, and automation in the sidebar choose Copilot, then MCP servers. Add your configuration in the MCP configuration section. You need repository admin rights to see this panel.
Add the server and save Paste a JSON block with mcpServers containing contextbolt-seo, type http, tools set to all with "*", and your URL referenced from the secret. Click Save MCP configuration, then assign Copilot an issue and check the agent's session log to confirm the SEO tools loaded.

The guide covers every client and the compatibility options. The full setup guide

What to ask it

“Before writing this page, check what it should target and who ranks” Assign Copilot an issue for a new page and it runs keyword_research and serp_overview first, so the draft is written against a real target.

“Audit the pages changed in this PR and comment with the issues” Calls page_audit on each changed URL and leaves the findings as a PR comment, turning SEO review into part of code review.

“Find keyword gaps against our main competitor and open issues for the top five” Runs competitor_keywords for the rivals, then ranked_keywords on both sides, and files the gaps as issues so the content backlog builds itself.

“Check our Search Console for pages slipping in position this month” Uses the free Search Console tools to read your real data and summarize what moved, without spending credits.

What it can do in GitHub Copilot

Give the cloud agent live keyword and SERP data
Audit changed pages automatically inside a pull request
Score keyword difficulty before a page gets written
Find the keywords a competitor already ranks for
Turn keyword gaps into issues on your backlog
Connect your own Google Search Console, read-only and free
Works alongside any other MCP servers on the repository
Get a private SEO Dashboard that fills itself with your research, free

ContextBolt SEO in GitHub Copilot: the full guide

GitHub Copilot has two surfaces that speak MCP, and they are configured in completely different places. This page covers the cloud 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 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, planning, and automation in the sidebar, then MCP servers. The MCP configuration section takes a JSON block. Both type and tools are required, and "*" enables every tool:

{
  "mcpServers": {
    "contextbolt-seo": {
      "type": "http",
      "url": "$COPILOT_MCP_CONTEXTBOLT_SEO_URL",
      "tools": ["*"]
    }
  }
}

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. Only Agents secrets and variables whose names start with COPILOT_MCP_ are available to the configuration.

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 Copilot cloud 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.

Frequently asked questions

Something else on your mind? Get in touch.

Is this the same as the VS Code setup?

No, and that is the main thing to get straight. This page covers the cloud agent, the one you assign issues to on github.com, which is configured per repository in Settings under Copilot, then MCP servers. If you want SEO tools in the editor instead, that is Copilot Chat in agent mode reading .vscode/mcp.json, covered on the VS Code page.

Does the cloud agent support remote MCP servers?

Yes, with one limitation worth knowing. GitHub's Copilot cloud agent supports remote MCP servers but does not support ones that authenticate with OAuth. ContextBolt SEO carries its token in the URL path rather than using OAuth, so it connects without a problem.

Can it use MCP prompts and resources too?

No. The cloud agent supports MCP tools only, not resources or prompts. Every ContextBolt SEO capability is exposed as a tool, so nothing is lost here, but it is worth knowing if you add other servers alongside it.

Who can change this configuration?

Repository administrators. The MCP servers panel sits under repository Settings, so anyone without admin rights will not see it. On an organization-owned repo, check whether your org has policies restricting which MCP servers are allowed before you add one.

Should I paste my URL directly into the config?

Prefer a secret. The configuration supports environment variable and secret substitution from the Agents secrets, using the same syntax style as GitHub Actions. Because your ContextBolt token sits inside the URL, storing the whole URL as a secret keeps it out of a settings screen and out of any config you export.

How many credits does an agent session cost?

Research tools cost one credit each and backlink tools cost three each, exactly as they do in an editor. An agent working through an issue may chain several calls, so watch the first few sessions to see what a typical task costs against your 1,000 monthly credits.

Go deeper

Keep reading

All integrations