Integrations · MCP client

SEOBolt for Claude Code

Add SEOBolt as an MCP server and Claude Code can crawl your site, read the audit, apply the fix plan to your repository, and re-crawl to confirm the score went up.

Available on every plan, including Free

Setup

  1. 1. Create an API key

    In SEOBolt, open Dashboard → Settings → API Keys and create a key (sk_live_…).

  2. 2. Add the remote server

    One command, nothing to install. Replace sk_live_YOUR_KEY with a key from Dashboard → Settings → API Keys.

    claude mcp add --transport http seobolt https://seobolt.app/mcp --header "Authorization: Bearer sk_live_YOUR_KEY"
  3. 3. Or run the npx package (stdio)

    Same tools, runs locally with Node.js.

    claude mcp add seobolt -e SEOBOLT_API_KEY=sk_live_YOUR_KEY -- npx -y mcp-server-seobolt
  4. 4. Check the connection

    Run /mcp inside Claude Code and confirm seobolt is listed, then ask for your projects.

  5. 5. Install the SEO skills (optional)

    Copies seven SEOBolt workflow skills (page brief, ship page, Monday review, fix existing pages, GEO check, link outreach, agent rules) into .claude/skills. Then type /seo-weekly-review.

    npx -y mcp-server-seobolt skills install

What you can do

MCP toolWhat it does
seo_projectsList all SEO projects with health scores and stats
seo_set_competitorsSet a project's competitor list (domains or names, max 20).
seo_auditGet the SEO audit (health score, page count, issues summary) for a project
seo_issuesGet detailed SEO issues with fix recommendations, grouped by type, with affected URLs
seo_start_crawlStart a new SEO crawl for a project.
seo_fix_planGet the full prioritized fix plan for a project: every site-wide issue with a ready-to-apply code snippet and the affected URLs.
seo_fix_suggestionsGet specific code fix suggestions with HTML snippets for a particular page URL
seo_content_scoreScore a page's SEO optimization for a target keyword.
seo_compareCompare two pages head-to-head on SEO metrics.
seo_get_checkout_urlGet a checkout URL to upgrade to a paid plan.
seo_domain_ratingGet the Domain Rating (DR) for any domain.
seo_keyword_difficultyCheck how hard it is to rank for a keyword.
seo_content_gapFind topics that competitors rank for but you don't.
seo_link_prospectsFind domains that link to competitors but not to you.
seo_gsc_content_opportunitiesFind keywords a site ALREADY ranks for in Google Search Console but does not target on-page — the highest-ROI content play.
seo_gsc_realityExplain WHY a site's top pages do (or don't) get traffic — fuses each page's real GSC numbers (impressions/clicks/position) with a live on-page crawl and returns an honest per-page verdict plus a single headline naming the true growth bottleneck (on-page hygiene vs. authority/rank vs. snippet/CTR).
seo_gsc_prune_candidatesFind pages worth pruning from a connected Google Search Console property: 0 clicks and <50 impressions over the window (default 90 days).
seo_gsc_repointFind pages whose top Google Search Console query is not reflected in the live title/H1 (connected GSC + live crawl).
seo_gsc_cannibalizationFind keyword cannibalization in a connected Google Search Console property: queries where 2+ URLs of the site each get at least 10% of the query's impressions.
seo_gsc_secondary_keywordsList every query a page already ranks top-10 for in a connected Google Search Console property, grouped by overlap, with a suggested title (≤60 chars) covering the top 2-3 secondary queries.
seo_gsc_content_decayFind pages losing traffic in connected Google Search Console: the last 28 days (or `days`) vs the window before, per page.
seo_gsc_low_ctrFind pages and queries in connected Google Search Console with high impressions but a CTR well below what their average position should earn (expected-CTR curve by position from public CTR studies): ≥200 impressions, position ≤20, CTR under half the expected value.
seo_gsc_index_coverageCheck whether Google has indexed your pages, using the Search Console URL Inspection API (real Google data, free quota 2,000/day per property).
seo_core_web_vitalsCore Web Vitals (mobile) from Google PageSpeed Insights for a URL, or for the first pages (≤5) of a project's latest crawl.
seo_brand_mentionsBrand Radar: find pages that mention your brand or domain without linking to you (unlinked mentions = easy link requests).
seo_find_contactFind how to contact a website for outreach: emails published on the page and on the same site's /contact, /contact-us, /about and /write-for-us pages (mailto links, visible text, Cloudflare-protected addresses), plus its contact page / contact form URL.
seo_ai_citationsAI citation check (GEO): ask an AI engine with live web search (OpenAI Responses API + web_search) up to 10 buyer prompts and report, per prompt, whether your domain is cited, whether your brand is mentioned, which other domains are cited, and an answer excerpt.

Example prompts

Claude Code integration FAQ

Do I need a paid SEOBolt plan for Claude Code?

No. API keys, the REST API, and the MCP server work on every plan, including Free. What each tool can do follows your plan's limits: the number of crawls, pages per crawl and project count depend on the plan, Brand Radar tools (brand mentions and contact lookups) need Starter or above, and AI citation checks and Google Search Console tools need Pro or above. The API key comes from Dashboard → Settings → API Keys.

Remote endpoint or npx package?

Both expose the same tools. The remote endpoint (https://seobolt.app/mcp) needs nothing installed. The npx package (mcp-server-seobolt) runs locally over stdio and needs Node.js.

Can Claude Code edit my site's code with the fix plan?

seo_fix_plan returns each issue with a code snippet and the affected URLs. A coding agent can apply those to your repository; you deploy, then seo_start_crawl and seo_audit confirm the score went up.

Is my API key safe in the config?

The key is sent only to seobolt.app as a Bearer token. Keep the config file out of version control and revoke the key in Settings if it leaks.

Can I add SEOBolt as a one-click connector instead?

Not yet. The remote endpoint takes a Bearer API key and does not offer OAuth sign-in, which one-click connectors in claude.ai, Claude Desktop and ChatGPT require. Use the config above.

Related