← All posts
Guide

How to Connect SEO Tools to Claude Code (2026 Setup Guide)

One claude mcp add command per tool: which SEO platforms have an official MCP server, the exact command to add each one to Claude Code, what auth it needs, and where there is no good option yet.

··12 min read

To connect an SEO tool to Claude Code, you add that tool's MCP server with one claude mcp add command. A remote server takes --transport http and a URL, and you sign in with /mcp. A local server takes -- followed by the command that starts it, with any API key passed through --env. Semrush, Ahrefs, DataForSEO and Google Merchant Center publish official servers. For Bing Webmaster Tools and Display & Video 360 you have to rely on community servers. Google Trends has no MCP route of its own.

This guide gives the exact command for each tool, what credentials it needs, and a couple of prompts to test it. For background on what MCP is and why it matters for search work, start with our MCP for SEO guide. This page is only about setup.

How does claude mcp add work?

Every tool below uses the same pattern. Anthropic's Claude Code MCP documentation is the reference. Here is what you need from it.

Remote (HTTP) servers. The vendor hosts the server. You give Claude Code a URL:

claude mcp add --transport http <name> <url>

If the server uses OAuth, start Claude Code, run /mcp, pick the server and choose Authenticate. A browser window opens for the vendor's login. If it uses an API key instead, pass it as a header with --header "Authorization: Bearer <key>".

Local (stdio) servers. Claude Code starts the server as a process on your machine. Everything after -- is the command to run it:

claude mcp add --env API_KEY=your-key --transport stdio <name> -- npx -y some-mcp-server

One gotcha from the docs: --env accepts several KEY=value pairs. If the server name comes right after it, the CLI reads the name as another pair and rejects it. Put another option, such as --transport stdio, between them, or put the name first.

Scopes. --scope decides where the config is saved and who sees it:

ScopeStored inAvailable inShared via git
local (default)~/.claude.json, under the project pathThis project onlyNo
project.mcp.json in the repo rootThis project onlyYes
user~/.claude.jsonAll your projectsNo

Use user for tools you want everywhere, such as your Search Console connection. Use project when the whole team should get the same server when they clone the repo. Use local for anything holding a personal key.

Google Search Console and GA4

Google doesn't publish a Search Console MCP server. Its official MCP list has no Search Console entry. You have two options: a hosted server or one you run yourself.

Hosted (GenieSeo). GenieSeo is our hosted server. It puts 23 Search Console tools, 12 GA4 tools and 2 PageSpeed tools behind one OAuth URL:

claude mcp add --transport http --scope user genieseo https://seo.geniedial.in/mcp

Run /mcp, choose genieseo and sign in with Google. Search Console uses Google's webmasters scope, which sitemap submission needs. Site deletion tools are disabled on the hosted server. GA4 is read-only (analytics.readonly). The free plan covers one Search Console property and one GA4 property with 200 tool calls a month. The full walkthrough, with project-scope setup and troubleshooting, is on the Claude Code integration page.

Self-hosted. mcp-gsc is an open-source Python server for Search Console only. You create your own Google Cloud OAuth client or service account. For GA4 on its own, Google maintains an official Google Analytics MCP server. It runs locally and uses your Application Default Credentials. Its README gives this Claude Code command:

claude mcp add analytics-mcp \
  -e "GOOGLE_APPLICATION_CREDENTIALS=PATH_TO_CREDENTIALS_JSON" \
  -e "GOOGLE_CLOUD_PROJECT=YOUR_PROJECT_ID" \
  -- pipx run analytics-mcp

It's read-only unless you start it with --allow-write and grant the analytics.edit scope.

Prompts to try:

  • "Find queries where we rank 8–20 with over 1,000 impressions in the last 28 days, then open the matching page templates in this repo."
  • "Compare organic sessions by landing page in GA4 for the last 30 days against the 30 before, and list pages that lost more than 20%."

PageSpeed Insights

Google doesn't publish a PageSpeed Insights MCP server either. You can call the PageSpeed Insights API yourself. Without an API key it has a low quota, so for regular use you create a key in Google Cloud.

GenieSeo includes run_pagespeed_insights and compare_pagespeed_insights on the same URL as above, with no Google Cloud key needed. They return lab Core Web Vitals and, where Chrome has enough traffic for the URL, real-user field data. Tool arguments and a worked example are on the PageSpeed Insights for Claude Code page.

For local debugging, Google's Chrome DevTools MCP records performance traces in a real Chrome instance. Its README installs it in Claude Code as a plugin: /plugin marketplace add ChromeDevTools/chrome-devtools-mcp, then /plugin install chrome-devtools-mcp@chrome-devtools-plugins. Its README notes that performance tools may send trace URLs to the CrUX API, and you can turn that off with --no-performance-crux.

  • "Run PageSpeed Insights on our three highest-traffic templates (mobile) and rank the LCP problems by how many URLs share the template."
  • "Record a performance trace of localhost:3000/pricing and tell me what blocks rendering."

Google Trends

This one needs some care. Google has never offered a public Trends API for general use. In July 2025 it announced a Google Trends API in alpha, with five years of rolling data, unscaled values and comparisons across dozens of terms. As of November 2026 the page still says Google is accepting applications for alpha testers and prioritizing developers with a clear use case. There's no official MCP server for it.

That leaves three routes:

  • Scraper-based community servers. Most "Google Trends MCP" projects wrap pytrends or scrape the Trends site. They break when Google changes the site's internals, and Google can rate-limit them.
  • SERP APIs. SerpApi's MCP server has a single search tool that works with any SerpApi engine, including its Google Trends API. Its README gives: claude mcp add --transport http serpapi https://mcp.serpapi.com/mcp --header "Authorization: Bearer YOUR_SERPAPI_API_KEY". It's a paid API.
  • The alpha API. If Google accepts your application, wrap the API in a small MCP server yourself.

GenieSeo has Trends tools in its codebase, but they aren't enabled on the hosted server, so connecting GenieSeo won't give you Trends data.

  • "Pull Google Trends interest for 'standing desk' vs 'sit stand desk' in the US over 5 years, monthly, and flag seasonality."

Bing Webmaster Tools

Microsoft doesn't ship an MCP server for Bing Webmaster Tools, but the Bing Webmaster API is public and needs only an API key. You generate the key in Bing Webmaster Tools under Settings, API access. Several community servers wrap it. mcp-server-bwt (MIT, Python, on PyPI) is maintained and documents a Claude Code command:

claude mcp add bwt -e BING_WEBMASTER_API_KEY=YOUR_API_KEY -- uvx mcp-server-bwt

You need uv installed for uvx. The server exposes write tools too, such as URL blocking and site removal, so approve tool calls one at a time instead of auto-allowing the whole server.

  • "List my verified sites in Bing Webmaster Tools and show the top 20 queries by clicks for the main one."
  • "Compare Bing and Google clicks for our /blog/ pages and list posts that do noticeably better on Bing."

Google Merchant Center

Google now has an official route here: the Merchant API MCP Access Service, an experimental alpha. Google says it can change without notice and recommends trying it on a test account first. It exposes read tools such as list_products, get_product_by_name and report_search, plus low-risk writes such as create_data_source. It shares quota with your normal Merchant API calls.

The endpoint is remote, but it takes an OAuth access token in a header rather than an interactive login. Google's docs give this command:

claude mcp add --transport http merchant-api https://merchantapi.googleapis.com/mcp --scope local \
  --header "Authorization: Bearer {ACCESS_TOKEN}" \
  --header "X-Goog-User-Project: {GOOGLE_CLOUD_PROJECT_ID}"

The token needs the https://www.googleapis.com/auth/content scope. Google's docs say the X-Goog-User-Project header is required when you use user Application Default Credentials. Google access tokens are short-lived, so a token pasted into the config stops working once it expires. A cleaner setup is a project-scoped .mcp.json that reads the token from an environment variable you refresh. See the security section below.

  • "List products in Merchant Center with disapproval issues and group them by issue type."
  • "Which product titles in the feed are missing the brand name? Draft fixes as a CSV in this repo."

Display & Video 360

We couldn't find an official MCP server for Display & Video 360. Google's MCP list doesn't include one. The official Google Ads MCP server covers Google Ads only, not DV360. The building blocks are the Display & Video 360 API for entities and the Bid Manager API for reporting.

Community servers exist. One example is dv360-ads-mcp-server, a Python server that reads a service-account key from a DV360_SERVICE_ACCOUNT environment variable. It's a small project, so read the code before you hand it a service account with access to your partner's advertisers. Once it's installed in a virtualenv, add it as a stdio server that points at that Python interpreter and the server script. For agencies, the safer move is often a service account scoped to a single advertiser.

  • "Show spend, impressions and CTR by line item for advertiser X over the last 7 days and flag line items pacing under 80%."

Semrush

Semrush runs an official remote server. Its developer docs list the endpoint as https://mcp.semrush.com/v2/mcp, streamable HTTP only, and give this Claude Code command:

claude mcp add semrush https://mcp.semrush.com/v2/mcp -t http

Then run /mcp, select Semrush MCP and choose Authenticate. OAuth is the default. For clients without OAuth, Semrush accepts an Authorization: Apikey YOUR_API_KEY header. Per the same page, access needs a plan with API units. Semrush One Starter, Pro+, SEO Classic Pro and Guru include 50,000 units. Business and Advanced plans need an API units package. Traffic & Market data needs a separate Trends API subscription. Older guides cite a /v1/mcp path, so use the URL in Semrush's current docs.

  • "Pull the top 50 organic keywords for competitor.com in the US database and show which ones we don't rank for."
  • "Get backlink referring domains gained by competitor.com in the last 30 days."

Ahrefs

Ahrefs replaced its old local npm server with a remote one. The GitHub repo is now archived and points to the remote server. The Claude Code guide gives:

claude mcp add ahrefs https://api.ahrefs.com/mcp/mcp -t http

Run /mcp, authenticate, sign in to Ahrefs, pick a workspace and approve access. According to the Ahrefs MCP introduction, the remote server is available on paid plans. Calls made through it draw from your monthly API units, so a "pull everything" prompt can be expensive.

  • "Show the 20 pages on our domain with the most referring domains, and check which of them return non-200 status codes."
  • "Find keywords where competitor.com ranks top 5 and we rank 11–30."

DataForSEO

DataForSEO maintains an official MCP server, now at v3. It comes in two forms. The hosted remote server uses OAuth:

claude mcp add --transport http dataforseo https://mcp.dataforseo.com/v3/mcp

Then authenticate with /mcp. Or run it locally over stdio with your API login and password, available from the DataForSEO dashboard:

claude mcp add --env DATAFORSEO_LOGIN=your_login --env DATAFORSEO_PASSWORD=your_password \
  --transport stdio dataforseo -- npx -y dataforseo-mcp-server@latest

DataForSEO bills per API request, so check the cost of a task before you ask Claude to run SERP checks across thousands of keywords.

  • "Get live Google SERPs (US, desktop) for these 15 keywords and tell me which have AI Overviews or featured snippets."
  • "Pull search volume and keyword difficulty for every H1 in our /guides/ folder."

Which SEO tools have an official MCP server?

ToolOfficial MCP server?TransportAuthSource
Google Search ConsoleNo (third-party only)HTTP (GenieSeo) or stdio (mcp-gsc)Google OAuthGenieSeo, mcp-gsc
GA4Yes (Google)stdioApplication Default Credentialsgoogle-analytics-mcp
PageSpeed InsightsNoHTTP (GenieSeo)Google OAuth via GenieSeoPageSpeed for Claude Code
Google TrendsNo; API is in alpha—Alpha approvalTrends API
Bing Webmaster ToolsNo (community)stdioAPI keymcp-server-bwt
Google Merchant CenterYes, alphaHTTPOAuth access token headerMerchant API MCP
Display & Video 360No (community)stdioService accountDV360 API
SemrushYesHTTPOAuth or API keySemrush MCP
AhrefsYesHTTPOAuthAhrefs MCP
DataForSEOYesHTTP or stdioOAuth or login/passwordmcp-server-typescript

How do you keep API keys and data safe?

Claude Code with several SEO servers connected can reach paid APIs, client accounts and write endpoints. Set it up with that in mind.

Keep keys out of committed files. A --env or --header value added with the default local scope lives in ~/.claude.json, outside the repo. With --scope project it goes into .mcp.json, which is meant to be committed. In that case, reference environment variables instead of literal keys. Claude Code expands ${VAR} and ${VAR:-default} in a server's command, args, env, url and headers:

{
  "mcpServers": {
    "merchant-api": {
      "type": "http",
      "url": "https://merchantapi.googleapis.com/mcp",
      "headers": {
        "Authorization": "Bearer ${GMC_ACCESS_TOKEN}",
        "X-Goog-User-Project": "${GCP_PROJECT_ID}"
      }
    }
  }
}

Each teammate sets the variables in their own shell, and the file stays safe to commit. If a variable isn't set, Claude Code loads the config with a warning and uses the literal ${VAR} text, so a missing key shows up as an auth error, not a silent fallback. Prefer OAuth servers where you can: there's no long-lived key to leak, and access can be revoked from the vendor's side. Treat per-user token URLs, including GenieSeo's /mcp/u/<token> fallback, like passwords.

Pick scope deliberately. User scope is convenient, but it means a client project can reach every account you've connected. If you work across several clients, put each client's credentials in that client's repo with local scope.

Watch for prompt injection. SEO tools return text written by other people: SERP snippets, competitor page titles, anchor text, product descriptions, page content from a crawl. Any of it can contain instructions aimed at an AI agent. When Claude reads that output in the same session where it can edit your repo or call write tools, there is a real risk. Keep write-capable tools on manual approval: Bing site removal, Merchant Center data source creation, sitemap submission, GA4 writes. Read diffs before accepting them. Be wary of a session that fetches untrusted content and then wants to do something you didn't ask for.

Where to go next

Start with the data you check most often. For most sites that's Search Console, so add it first and add others as you need them. The setup walkthrough is on the Claude Code integration page, and recipes has ready-made prompts that combine Search Console, GA4 and PageSpeed data in one Claude Code session.

Frequently asked questions

Do I need a separate MCP server for every SEO tool?+

Usually, yes. Each vendor's server speaks to its own API with its own credentials, so Semrush, Ahrefs and DataForSEO are three entries in Claude Code. Some servers bundle related Google APIs: GenieSeo covers Search Console, GA4 and PageSpeed Insights behind one URL. Claude Code loads all connected servers at once, so one prompt can draw on several.

Will connecting many MCP servers slow Claude Code down?+

Every connected server adds its tool definitions to Claude's context, so a dozen servers with hundreds of tools costs context and can make tool selection less precise. Add servers per project with the local or project scope instead of putting everything in user scope, and remove ones you no longer use with claude mcp remove.

Can I use these SEO MCP servers in Claude Desktop or claude.ai too?+

Remote HTTP servers with OAuth (GenieSeo, Semrush, Ahrefs, DataForSEO) can also be added as custom connectors in Claude's web and desktop apps. Local stdio servers such as the Bing Webmaster or Google Analytics ones run on your machine, so they work in Claude Desktop through its config file but not on claude.ai.

Is there an official Google Search Console MCP server from Google?+

Not as of November 2026. Google's own list of MCP servers (github.com/google/mcp) includes Google Analytics, BigQuery, Chrome DevTools and Cloud products, but no Search Console server. Search Console access in Claude Code comes from third-party servers: hosted ones like GenieSeo or open-source ones you run yourself, such as mcp-gsc.

Do these servers cost money on top of my Claude plan?+

Most do. Semrush and Ahrefs require a paid subscription and draw from API units, DataForSEO bills per API request, and GenieSeo has a free plan with 200 tool calls a month plus paid plans. The Google APIs behind GA4, Merchant Center and PageSpeed have free quotas, but you set up your own Google Cloud project to use them directly.

Plug Search Console into Claude in 60 seconds.

One MCP URL, every AI client. No local setup, no API keys.