Claude Code is Anthropic’s command-line interface for Claude. It runs in your terminal, reads your codebase, and can use MCP servers to connect to external tools and data, including live SEO research from ContextBolt SEO.
This is the integration where ContextBolt SEO is at its best, because Claude Code has file access. Every keyword, SERP, domain, and competitor lookup you run gets mirrored to a ./seo-findings/ folder in your project as markdown. Your research stops vanishing into the chat and becomes a searchable, git-trackable record you build up over time.
Why SEO data belongs in your terminal
If you are shipping a site or an app, you are already in the terminal. Asking “how hard is it to rank for this, and who’s already there?” without switching to a dashboard keeps you in flow. Claude Code calls the right tool, returns the numbers inline, and writes them to disk so next week’s question starts from what you already know instead of from scratch.
Because these are MCP tools, Claude Code chains them. “Find ten low-difficulty keywords around home espresso, check which ones my competitor already ranks for, and tell me the gaps” is one prompt, not ten dashboard sessions.
Config file alternative
If you prefer editing config directly, add ContextBolt SEO to .mcp.json in your project root:
{
"mcpServers": {
"contextbolt-seo": {
"type": "http",
"url": "https://seo.contextbolt.app/mcp/YOUR_TOKEN"
}
}
}Two things worth flagging. First, Claude Code requires "type": "http" for remote servers. Leave it out and the connection fails silently. Second, your URL contains a personal token, so if you commit .mcp.json to a public repo, swap the token for an env var like ${CONTEXTBOLT_SEO_URL} and set it locally. The full setup, tools, and workflows are in the ContextBolt SEO guide.
How to connect ContextBolt SEO to Claude Code
-
Subscribe and get your MCP URL
Subscribe to ContextBolt SEO ($35/month for 1,000 lookups). Your private MCP URL arrives by email and looks like https://seo.contextbolt.app/mcp/YOUR_TOKEN. Treat it like a password and keep it out of public repos.
-
Add it with one command
In your terminal run: claude mcp add --transport http contextbolt-seo https://seo.contextbolt.app/mcp/YOUR_TOKEN. Add --scope user before the name to make it available in every project; leave it off to scope the server to the current repo only.
-
Confirm the connection
Run claude mcp list and you should see contextbolt-seo with a connected status. Then start a session and ask 'what SEO tools do you have?'. If it lists keyword, SERP, domain, and competitor tools, you are live.
-
Connect your Search Console (optional, free)
Ask 'connect my Google Search Console'. Claude Code hands you a link, you approve read-only access on Google's consent screen, and your real clicks, positions, and quick wins are readable too. The Search Console tools are free and never spend your monthly lookups.
Example prompts for ContextBolt SEO + Claude Code
Once connected, try asking Claude Code:
Claude Code calls keyword_research and returns related terms with volume, difficulty, and intent, so you can plan content without leaving the terminal.
Chains keyword_difficulty and serp_overview in one prompt. You get a difficulty score and the live page-one results to model your post on.
Runs ranked_keywords then competitor_keywords. A ready-made content map plus the rivals you would never have named off the top of your head.
Calls backlink_gap and hands back a spam-scored prospect list, a ready-made outreach shortlist. Backlink calls cost three lookups each.
What you can do with ContextBolt SEO in Claude Code
Run keyword research in plain English, no query builder
Score how hard a keyword is to rank for before you write
See who ranks in Google's top 10 for any query
Size up any domain's traffic, keywords, and authority
Find the keywords a competitor already ranks for
Spot backlink gaps: who links to rivals but not you
Connect your own Google Search Console, read-only and free
Save every lookup to ./seo-findings/ as markdown you can grep and commit