By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Claude Code to Google Search Console is the Ryze AI connector. Approve Google inside a Ryze AI workspace and save a Site, register the connector from your shell with claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp, then open /mcp in a Claude Code session, choose ryze and finish the browser sign-in. A fresh session can then query Search Console, with 7 tools in all.
- In Ryze AI open Integrations, find Google Search Console, click Connect and save a Site
- In your terminal run the claude mcp add command with the connector URL
- In Claude Code run /mcp, select ryze and authenticate in the browser
- Pick the workspace, click Allow connection and ask Claude Code to list your properties
Claude Code to Google Search Console at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, a hosted MCP server that Claude Code registers with a single claude mcp add command |
| Server address | https://connector.get-ryze.ai/mcp, one address for every user |
| Sign-in | OAuth 2.0 in your browser, started from /mcp or with claude mcp login ryze. For scripts, a Ryze AI API key passed with --header |
| Search Console tools | 7: property list, Search Analytics queries, URL inspection, sitemap list, sitemap summary, sitemap submit and sitemap delete |
| Can it change Search Console | Yes, in two places. submitSitemap writes and deleteSitemap deletes a sitemap entry. The other 5 tools only read |
| Google access | The webmasters scope, which Google calls read and write access. The login needs access to a verified Search Console property |
| Other data in the same session | Tools for other platforms connected in the same Ryze AI workspace arrive through the same server |
| Claude Code plan | Pro, Max, Ultra, Team, Enterprise or Console, or a provider such as Amazon Bedrock. Anthropic names no extra plan for MCP servers |
| Ryze AI price | SEO Starter is $129 per month with a 3-day free trial, and the tools also run on Paid Ads at $89 per month. Adding the connector costs nothing |
| Google's own option for Claude Code | None found. Google's pages listed no Search Console MCP server, connector or plugin on November 14, 2026 |
| Last tested | Calls sent through the connector from Claude Code on November 14, 2026. Sign-in endpoints checked November 19, 2026 |
Before you start
- A Claude Code account. Anthropic says Claude Code requires a Pro, Max, Ultra, Team, Enterprise or Console account; the free claude.ai plan does not include it. It can also run through Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry. Anthropic's MCP page names no extra plan for remote MCP servers.
- A Google login with access to a verified Search Console property. Ryze AI asks Google for the webmasters scope. Per Google's permissions table, submitting a sitemap is open to owners and full users, so a restricted user may find the two sitemap changes unavailable. Google's table covers the Search Console interface, and no call here tested a restricted login.
- A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial, Paid Ads is $89 per month with a 7-day free trial and Agency is $279 per month. Connecting the connector is free, but the 7 Search Console tools need an active plan or trial.
How to connect Claude Code to Google Search Console
Two steps happen in Ryze AI, four in Claude Code. The connector URL is the same for every user.
Connect Google Search Console in Ryze AI
Create a Ryze AI account or sign in, open Integrations in the left sidebar and find Google Search Console with the Search integrations box or the Analytics filter. Click Connect, sign in to Google and approve access, keeping every requested permission checked. You can also ask the Ryze AI agent in Claude to connect Google Search Console, which sends a one-time link that works once and for 24 hours.
Confirm the Site
Back in Ryze AI, check the Site (Ryze AI pre-selects the one that matches the workspace domain), change it if needed and click Save. Until a Site is saved the card shows Require setup.
Register the connector in Claude Code
In your terminal, not inside a claude session, run: claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp. Claude Code stores the server with local scope by default. Add --scope user to make it available in all your projects. Until you sign in, claude mcp list marks it as needing authentication.
Sign in from Claude Code
Inside Claude Code run /mcp, select ryze, press Enter and choose Authenticate, or run claude mcp login ryze in the shell. Add --no-browser to print the sign-in URL instead of opening a browser, for example over SSH; the paste step needs an interactive terminal, so connect with ssh -t.
Allow the workspace
On the Ryze AI page, sign in if asked, choose the workspaces Claude Code can use and click Allow connection. Check the result with claude mcp get ryze.
Start a new session and list your properties
Tool search is on by default in Claude Code, so MCP tools load on demand. Ask: List every Search Console property my login can access with its permission level, then show the top 20 queries by clicks for the last 28 days. The tool that lists properties selects no site on its own, so name the property you want in later questions.
The Ryze AI help article for Google Search Console covers the Google side of the connection, and the Claude Code MCP docs cover the client commands.
Sources: Claude Code MCP, MCP quickstart. Checked November 14, 2026.
OAuth, API key and claude.ai connectors
Claude Code accepts the Ryze AI connector three ways. Pick the one that matches where the session runs.
CLI with OAuth (recommended for a personal machine)
claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --scope userThis is the flow in the steps above. The scope flag decides who gets the server: local (the default) is the current project only, user covers every project on your machine, and project writes a .mcp.json file that teammates share and approve themselves when they next open an interactive session. A scope is fixed once the server is added, so moving it means removing the entry and adding it again.
CLI with a Ryze AI API key
claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp --header "Authorization: Bearer rk_live_..."Create the key under Workspace Settings, Profile, API keys, Create key, and copy it before leaving the page because it is shown once. Per the Ryze AI help center the key works on /mcp and not on /sse. claude mcp add stores the entry without testing the key, and a rejected Authorization header marks the connection as failed in Claude Code with no OAuth fallback, so swap in a fresh key rather than waiting for a browser window.
claude.ai connectors inside Claude Code
If you already added Ryze AI at claude.ai/customize/connectors, Claude Code can reuse it. Log in to Claude Code with that same claude.ai subscription account and run /mcp, where the connector is marked as coming from claude.ai. Team and Enterprise plans let only admins add servers in claude.ai. This path is skipped when the session uses ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, apiKeyHelper, a third-party provider, an Anthropic profile or a setup-token credential; /status shows which one is active. If the same URL was also added with claude mcp add, that entry wins and /mcp lists the claude.ai copy as hidden.
Scripts and limits
Non-interactive runs (claude -p and the Agent SDK) cannot start the OAuth flow, so sign in beforehand with /mcp or claude mcp login ryze, or use an API key. Claude Code warns when a tool result exceeds 10,000 tokens and keeps MCP output to 25,000 tokens by default; anything longer is written to a file and the conversation receives its path. Set MAX_MCP_OUTPUT_TOKENS to raise the limit. A Search Console request for 25,000 rows can run long, so ask for fewer rows or a shorter date range. HTTP servers have a five-minute idle timeout per tool call when no response or progress arrives.
Claude Code and MCP: the facts in one table
| Topic | What Anthropic's docs say |
|---|---|
| Adding a server | claude mcp add --transport http <name> <url> for a hosted server, or claude mcp add <name> -- <command> for one that runs locally. Both are typed in the shell |
| Files it writes | ~/.claude.json for local and user scope, .mcp.json at the project root for project scope. Paths like ~/.claude/mcp.json are ignored |
| Transports | Streamable HTTP for remote servers and stdio for local ones. SSE still works but is deprecated, and WebSocket can only be set in the JSON config |
| OAuth | OAuth 2.0. Claude Code reads the server's protected resource metadata first, then its authorization server metadata. A 401 or 403 answer flags the server as needing authentication, and the browser returns to a loopback port |
| Static credentials | --header or -H at add time, or a headers object. A rejected Authorization header leaves the server failed instead of starting OAuth |
| Tool approval | From v2.1.283, interactive terminal and VS Code sessions with no mode set start in auto mode when the session supports it. A second model, the classifier, then reviews actions instead of you, except those an allow, ask or deny rule settles. Rules use the form mcp__<server>__<tool> |
| Checking status | claude mcp list and claude mcp get in the shell. Inside a session, /mcp shows the tool count next to each connected server, and /mcp reconnect all retries failed ones |
| Loading tools | Tool search is on by default: names load at start, full definitions when Claude needs them |
| Plan | The MCP page sets no plan of its own. By default anyone running Claude Code can add a server with claude mcp add; on Team and Enterprise only admins add claude.ai connectors |
| Admin controls | managed-mcp.json for a fixed server set, allow and deny lists, and a switch that turns off claude.ai connectors |
| Cloud sessions | Local and user entries stay in ~/.claude.json on your machine, so a cloud session does not see them. A cloud session on one repository reads that repository's .mcp.json |
Sources: Claude Code MCP, MCP quickstart, Permission modes, Permissions, Managed MCP, Cloud environments, Claude Code setup. Checked November 14, 2026.
Claude web, ChatGPT and Cursor
The same URL works in other MCP clients. Google Search Console is connected once in Ryze AI, so nothing changes on the Google side.
Claude on the web and Desktop
In Customize, Connectors, click + Add and choose Add custom connector. Name it Ryze AI and paste https://connector.get-ryze.ai/mcp. The free plan allows one custom connector, and Team and Enterprise plans need an Owner to add it first.
ChatGPT
Per OpenAI, ChatGPT Business and Enterprise/Edu on the web get full custom MCP support, while Pro can connect custom MCP servers with read and fetch permissions only. Choose Add custom MCP server under Plugins, enter the URL and select OAuth.
Cursor
Put the entry in ~/.cursor/mcp.json for every project or .cursor/mcp.json for one. Cursor signs in with OAuth and PKCE and by default asks before it uses an MCP tool.
{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }Google Search Console permissions and scopes
Three things decide what Claude Code can do in Google Search Console.
- Which Google login
- Ryze AI connects with Google sign-in (OAuth) and the Search Console scope, webmasters, which covers reading data and submitting or removing sitemaps. Keep every requested permission checked on the Google screen. The login needs access to a verified Search Console property.
- Which properties
- The agent can list every property the connected login can access, with its permission level, using listSites. After connecting you confirm one Site for the workspace. Several Google logins can be added to one workspace with Add one more account, each with its own Site, and one is the primary the agent uses by default. Separate clients belong in separate workspaces.
- Read, write and delete
- 5 tools only read. submitSitemap writes and deleteSitemap deletes, and both change Search Console. Removing a sitemap takes it out of Search Console and leaves the sitemap file on your site untouched.
Sources: Ryze AI Google Search Console guide and Google's Search Console API authorization page.
The Google scope of the default connection
Clicking Connect on the Google Search Console card makes Ryze AI ask Google for the Search Console scope called webmasters. Google lists a second scope, a read-only one, that the default connection does not use.
| Scope | Google's description | Role on this connection |
|---|---|---|
| webmasters | Read/write access | Requested by Ryze AI. Google lists sitemaps.submit and sitemaps.delete with this scope only, which is why the default connection holds it. The 5 read tools use methods that Google also allows with the read-only scope |
| webmasters.readonly | Read-only access | Not requested by the default connection |
Search Console permission levels
Inside Search Console, the permission level of the connected login sets the ceiling. listSites returns the level for each property, and Google's API names four values: siteOwner, siteFullUser, siteRestrictedUser and siteUnverifiedUser. The table below describes Google's interface; the pages read here do not map each level to API methods, and no call tested a write with a restricted login.
| Permission level | What Google says | What it means for Claude Code |
|---|---|---|
| Owner | Has full control over properties in Search Console. A verified owner proved ownership with a token, and a delegated owner was granted ownership by a verified owner | Google lists Submit sitemap and URL Inspection for owners |
| Full user | Has view rights to all data and can take some actions | Google lists Submit sitemap and URL Inspection for full users |
| Restricted user | Has simple view rights on most data | Google's table shows URL Inspection as fetch only and leaves the Submit sitemap cell empty. Performance data is listed for this level |
| Associate | Can take certain actions on behalf of your site or access certain data, but cannot open or view the account or data directly | Not a login for reading data through Claude Code |
Not included in the connection: a tool to request indexing, to remove a URL from Google or to verify a property. Index coverage for every URL of a site is not available through the API either, because URL Inspection checks one URL at a time.
Sources: Search Console API authorization, searchanalytics.query reference, sitemaps.submit reference, sitemaps.delete reference, Sites reference, Users and permissions. Checked November 14, 2026.
Removing access
To remove access, disconnect Google Search Console on its card in Ryze AI. In Claude Code, run claude mcp logout ryze and then claude mcp remove ryze: Anthropic's docs say remove deletes the tokens Claude Code stored but does not revoke them at the server that issued them.
What Claude Code can do in Google Search Console
The Ryze AI connector exposes 7 Google Search Console tools. Five only read and two change Search Console.
| Tool | Type | What it does |
|---|---|---|
| google_search_console__listSites | Read | Lists every Search Console property the connected login can access, with permission levels. |
| google_search_console__runRawSearchAnalytics | Read | Runs a Search Analytics query by query, page, country, device, search appearance or date, for web, image, video, news or Discover results, up to 25,000 rows per request. |
| google_search_console__inspectUrl | Read | Inspects one URL's index status through the URL Inspection API: coverage, verdict, last crawl, canonical, indexing state, mobile usability and rich results. |
| google_search_console__listSitemaps | Read | Lists the sitemaps Search Console knows for a property, with last submitted and downloaded dates, errors, warnings and submitted counts. |
| google_search_console__getIndexationSummary | Read | Returns a sitemap summary for a property: number of sitemaps, submitted URLs, errors, warnings and pending items. |
| google_search_console__submitSitemap | Write | Submits or resubmits a sitemap to Search Console for a property. |
| google_search_console__deleteSitemap | Delete | Removes a sitemap from Search Console for a property; the sitemap file on the site is not touched. |
submitSitemap and deleteSitemap change Search Console, and the other 5 tools only read. To see those two calls before they run, use Claude Code's permission rules: a rule names one tool as mcp__<server>__<tool>, or all of a server's tools as mcp__<server>__*, where <server> is the name you gave in claude mcp add, and it can allow, ask or deny. Interactive sessions on v2.1.283 or later begin in auto mode where it is available, and a classifier then reviews actions in your place, so add an ask rule if you want a prompt. In Claude, you can set write and delete tools to Needs approval under Customize, Connectors, Ryze AI, Tool permissions. The Ryze AI chat has its own Tool approvals setting, which starts on Skip all approvals and can be switched to Approve write & delete or Manual approve.
Limits in numbers
These are Google's limits for the Search Console API, as the pages read on November 14, 2026 state them. They bind every caller of the API, the Ryze AI connector included. QPM is queries per minute and QPD is queries per day. The last three rows cover the Ryze AI tools and Claude Code.
| Limit | Value |
|---|---|
| Search Analytics request rate | Per site 1,200 QPM and per user 1,200 QPM. Per project 30,000,000 QPD and 40,000 QPM |
| Search Analytics load | Short-term quota is measured in 10 minute chunks and long-term quota in 1 day chunks. Google says queries grouped or filtered by page and query string are the most expensive, and load rises with the date range. If you exceed your quota, wait 15 minutes and try again. Every quota event returns the same quota exceeded error |
| URL Inspection request rate | Per site 2,000 QPD and 600 QPM. Per project 10,000,000 QPD and 15,000 QPM |
| Sites and sitemaps | Per user 20 queries per second and 200 QPM. Per project 100,000,000 QPD |
| Rows per request | 1 to 25,000, with 1,000 as the default. A request for 25,001 was refused in the November 14, 2026 test |
| Paging | Re-run the same query and raise startRow by 25,000 until a response has 0 rows. A startRow past the end returns a successful response with zero rows |
| Rows per day | Google says the Search Analytics method exposes a maximum of 50K rows of data per day per search type, sorted by clicks |
| Data delay | Data is typically available after 2 to 3 days. With dataState all the data includes fresh data that may be incomplete; with final, or no value, only finalized data comes back |
| History | Search Console keeps data for the last 16 months |
| Dates and time zone | startDate and endDate use YYYY-MM-DD in Pacific Time. Results are sorted by clicks, highest first, unless you group by date, which sorts by date, oldest first |
| URL Inspection scope | One URL per call, and only the version in the Google index. You cannot test the indexability of a live URL, and the URL must sit under the property |
| Ryze AI tool inputs | Every tool takes a workspace and an optional connection_id, and all but listSites take a siteUrl. runRawSearchAnalytics caps a request at 25,000 rows and is repeated with startRow for more. Dimensions are query, page, country, device, searchAppearance and date, and types are web, image, video, news and discover |
| Ryze AI sitemap counts | listSitemaps returns submitted counts, errors and warnings. Google marks the indexed count in its sitemap reference as deprecated, so do not rely on it |
| Claude Code output | A warning past 10,000 tokens. The default cap is 25,000 tokens, and MAX_MCP_OUTPUT_TOKENS changes it |
Sources: Search Console API usage limits, searchanalytics.query reference, Getting all your data, URL Inspection reference, Sitemaps reference, Data retention, Performance report dates, Claude Code MCP. Checked November 14, 2026.
Calls tested through the default connection
Every row is one call that Claude Code sent through the Ryze AI connector on November 14, 2026, over the default connection to a Domain property. Three asked for data and three were broken on purpose to capture Google's replies. The property belongs to a real account, so the table names fields and outcomes and leaves out names, domains and values.
| Tool | What Claude Code sent | What came back |
|---|---|---|
| listSites | Only the workspace | Worked |
| runRawSearchAnalytics | 7 days, dimension query, an equals filter on a random 20-letter string | Worked, with an empty result. The whole response was one key, responseAggregationType set to byProperty, and no rows key |
| runRawSearchAnalytics | 90 days, dimension query, rowLimit 120, dataState all, an includingRegex filter on query | Worked. Each row carried keys, clicks, impressions, ctr and position, ordered by clicks, highest first. Fewer rows than rowLimit came back, so no second page was needed |
| runRawSearchAnalytics | 7 days, dimension query, rowLimit 25001 | Refused by Google with HTTP 400 |
| runRawSearchAnalytics | keyword as a dimension, which does not exist | Refused by Google with HTTP 400 |
| runRawSearchAnalytics | An endDate before the startDate | Refused by Google with HTTP 400 |
First 3 prompts to run and 10 jobs
Each answer comes from your own property, so this page describes what comes back instead of showing sample numbers.
1. Find your property, then list top queries
List every Search Console property my login can access with its permission level. For the main one, show the top 25 queries by clicks over the last 28 days, with impressions, CTR and average position.
Tools used: google_search_console__listSites, google_search_console__runRawSearchAnalytics
What comes back: The properties your login reaches with a permission level for each, then rows with the query, clicks, impressions, CTR and position, highest clicks first. Search Console data runs 2 to 3 days behind, so the last days of the range are thin.
2. Pages ranking just outside the click positions
Group the last 90 days by page and query for this property, then list pages whose average position sits just outside the top results, with their impressions and CTR.
Tools used: google_search_console__runRawSearchAnalytics
What comes back: A table of page and query pairs with clicks, impressions, CTR and position. Google calls queries grouped by page and query the most expensive, so a long range can be slow. This call was not run in the November 14, 2026 test.
3. Check one URL and the sitemaps
Inspect the index status of this URL and report the verdict, last crawl and canonical. Then list the property's sitemaps with their errors and warnings.
Tools used: google_search_console__inspectUrl, google_search_console__listSitemaps
What comes back: The URL's coverage, verdict, last crawl, canonical, mobile usability and rich results, then each sitemap with its last submitted and downloaded dates. It covers one URL per call. These tools were not run in the test.
Google leaves anonymized queries out of the query report to protect user privacy. Average position is Google's figure for the topmost result from your site.
10 jobs to hand to Claude Code
Nine jobs Claude Code can do through the connector and one it cannot, each with the Search Console tool behind it. In the test on November 14, 2026, only listSites and runRawSearchAnalytics were called. The other tools had their definitions loaded and were left uncalled.
| Job | Ask Claude Code | Tool | Works on the default connection |
|---|---|---|---|
| List properties | Which Search Console properties can my connected Google login access, and with what permission level? | google_search_console__listSites | Yes. Called in the test |
| Top queries | Show the top queries by clicks and impressions for the last 28 days, with CTR and average position. | google_search_console__runRawSearchAnalytics | Yes. Called in the test, grouped by query |
| Brand or question queries | Show only the queries that contain a word or match a pattern, for example question words or brand terms. | google_search_console__runRawSearchAnalytics | Yes. Called in the test with equals and includingRegex filters on query |
| Pages just outside click positions | Which pages rank just outside the positions that earn clicks, and for which queries? | google_search_console__runRawSearchAnalytics | Yes. Grouping by page was not run in the test |
| Country, device or search appearance | Split clicks and impressions by country, device or search appearance. | google_search_console__runRawSearchAnalytics | Yes. Not run in the test |
| Trend for one page | Show the day-by-day trend for this page, to see whether a published article earns impressions and clicks. | google_search_console__runRawSearchAnalytics | Yes. Grouping by date was not run in the test |
| Image, video, news or Discover | Report performance in image, video, news or Discover results instead of web results. | google_search_console__runRawSearchAnalytics | Yes. Not run in the test |
| Index status of one URL | Inspect this URL and give me coverage, verdict, last crawl, canonical, mobile usability and rich results. | google_search_console__inspectUrl | Yes. One URL per call. Not run in the test |
| Sitemap health and changes | List every sitemap with its errors and warnings, give a property summary, then resubmit this sitemap or remove a stale one. | google_search_console__listSitemaps, google_search_console__getIndexationSummary, google_search_console__submitSitemap, google_search_console__deleteSitemap | Yes, with the webmasters scope. The two changes were not run, because they alter Search Console. Google lists Submit sitemap for owners and full users |
| Request indexing or remove a URL | Ask Google to index this new page, or remove this URL from Google. | None | No. No tool requests indexing, removes URLs or verifies a property. Use Search Console itself |
7 ways to connect Claude Code to Google Search Console
Claude Code accepts hosted servers through claude mcp add --transport http, local servers through claude mcp add <name> -- <command>, and plugins, so 7 ways can bring Search Console data into it. This guide treats the Ryze AI connector as the main way: Google is approved once inside Ryze AI, and Claude Code needs one command and a browser sign-in, with no code to write and no Google Cloud project to create. The other 6 were read on their own pages on November 14, 2026. Each row gives the setup as it applies to Claude Code, and none of the 6 was run for this guide.
| Way | Runs where | Setup in Claude Code | What it reaches in Search Console | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI. The same address works in Claude, ChatGPT, Cursor and other MCP clients | claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp, then /mcp to sign in. A Ryze AI API key sent with --header, or a connector added on claude.ai, also works. Google sign-in happens inside Ryze AI | 7 tools: property list, Search Analytics queries, URL inspection, sitemap list, sitemap summary, sitemap submit and sitemap delete. No tool requests indexing | SEO Starter is $129 per month with a 3-day free trial, and Paid Ads at $89 per month also runs the tools. The connector itself is free |
| Composio | Hosted by Composio | Composio's Claude Code page gives two routes. Via Composio Connect you add its MCP to Claude, start Claude Code, run /mcp, select Composio and click Authenticate. Via its SDK a script prints a claude mcp add --transport http command with a Composio API key header, and Composio lists a Claude Pro, Max or API billing account as the prerequisite | 14 tools on the toolkit page, read and write, including Add Site, Delete Site, Verify Site Ownership and Inspect URL | Pricing page: Free plan with 10,000 tool calls a month, Standard at $18 per seat per month. Its Search Console toolkit FAQ gives a different free-plan figure, so check the page you use |
| Windsor.ai | Hosted by Windsor.ai | In Claude Code, run claude mcp add --transport http windsor https://mcp.windsor.ai, then sign in to Windsor.ai and connect Search Console once | Read only, with no URL inspection. Clicks, impressions, CTR and position, plus fields such as words_in_query. Its search type field covers web, image, video and news; Discover and Google News data are not included | 30-day trial, then a Forever Free plan with 1 data source. Basic is $23 per month, or $19 on the annual toggle |
| Coupler.io | Hosted by Coupler.io, on a copy of your Search Console data that it syncs on a schedule | Build a Search Console data flow, add Custom MCP as its destination to get a token and a server URL, then add both to a client. Coupler.io's page names Claude Code, Codex and Cursor for this step | Read-only access to the synced data. No sitemap management, URL submission or Indexing API calls. Refresh as often as every 15 minutes | Free plan at $0 with manual refresh. Starter is $32 per month, or $24 billed annually. The page read did not show which plans include MCP |
| AminForou/mcp-gsc, open source | On your machine, started by the assistant with uvx mcp-search-console | Create your own Google OAuth client or a service account key, then add a command entry to the assistant's config. The README gives snippets for Claude Desktop, Cursor and Codex CLI and does not name Claude Code, so a Claude Code entry is the reader's own work with claude mcp add -- followed by the command | README: 20 tools, 15 of them named in its table, among them list_properties, get_search_analytics, inspect_url_enhanced, batch_url_inspection and manage_sitemaps. add_site, delete_site and delete_sitemap are disabled by default | Free, MIT license. 2,202 GitHub stars, last push November 6, 2026 |
| Bulk data export to BigQuery with Google's BigQuery MCP server | Google Cloud. The MCP endpoint is https://bigquery.googleapis.com/mcp | Two Google features that Google does not describe as one Search Console connector. In Search Console, a property owner sets up the daily export. Google's client guidance for its remote MCP servers has a Claude Code section | Performance data only, from the day the export starts, without anonymized queries. No URL inspection and no sitemap actions. The first export can take up to 48 hours | Subject to Google Cloud storage and query costs, with a free usage level. The BigQuery MCP page states no price for the server |
| Search Console API with your own code | Google's servers. The API is an HTTP REST service | You write or run code against it with OAuth 2.0 and the webmasters or webmasters.readonly scope, in a Google Cloud project with the API enabled. Google's API pages describe no MCP endpoint | Search Analytics, sitemaps, sites and URL Inspection. Add and delete a site are available in the API and have no Ryze AI tool | Google: all use of the API is free of charge, within usage limits |
Options that do not fit this job
- A Google MCP server for Search Console. None was found on Google's pages on November 14, 2026. Google's list of products with a remote MCP server has 87 rows and no Search Console row, and its MCP repository lists 16 remote and 16 open-source servers with no Search Console entry. Google does publish an open-source MCP server for Google Analytics, which is a different product.
- Developer Knowledge MCP server. Google hosts it at https://developerknowledge.googleapis.com/mcp and Google's page gives a Claude Code command for it, with an API key header. It lets Claude Code search and read Google's developer documentation, and returns no data from a Search Console account.
- AI-powered configuration inside Search Console. Google announced it on December 4, 2025 as an experimental feature that applies filters and comparisons in the Performance report from a natural language request. It runs in the Search Console interface, supports only the Performance report for Search results, limits each user to 20 requests per day and is visible to a small percentage of users. It is not a connector for an outside assistant.
- Zapier MCP. Zapier lists Claude Code among its popular clients, but no Google Search Console page was found on Zapier on November 14, 2026: five addresses for it returned HTTP 404. That is a finding about those addresses, not a statement from Zapier that it cannot connect to Search Console.
Which one to pick
Ryze AI is the best Google Search Console connector for Claude Code when you want a hosted URL with Google sign-in handled for you and the same server for other platforms, but you pay for a Ryze AI plan, your data passes through Ryze AI, and it has no tool to request indexing or add a site. If you want to own the pipeline, the Search Console API and bulk export to BigQuery need no Ryze AI plan, and the BigQuery route keeps history in your own tables, though it starts on the day you turn it on. Composio and Windsor.ai fit teams that already run them for other apps, and Coupler.io fits teams that want a synced copy refreshed on a schedule. The mcp-gsc server is a free local option that needs your own Google credentials. Several of these can be registered in Claude Code at once under different names.
Sources: Google MCP supported products, Google MCP repository, Search Console API overview, Search Console API pricing, Bulk data export, BigQuery MCP server, Configure MCP in an AI application, Developer Knowledge MCP server, AI-powered configuration, Composio Search Console toolkit, Composio Claude Code page, Composio pricing, Windsor.ai Search Console MCP, Windsor.ai pricing, Coupler.io Search Console MCP, Coupler.io pricing, mcp-gsc on GitHub, Zapier MCP quickstart, Claude Code MCP. Checked November 14, 2026.
Claude Code, Search Console and MCP: dates that matter
| Date | What happened |
|---|---|
| January 31, 2022 | The URL Inspection API launched, with a quota of 2,000 queries per day and 600 per minute per Search Console property. |
| February 21, 2023 | Google announced bulk data export of Search Console performance data to BigQuery. |
| April 9, 2025 | The Search Analytics API gained hourly data: the HOUR dimension with dataState HOURLY_ALL, for up to 10 days. The Ryze AI tool definition lists neither, and neither was tested. |
| June 18, 2025 | Anthropic announced remote MCP server support in Claude Code. Version 1.0.27, dated the same day in the changelog, added Streamable HTTP servers and OAuth for remote servers. |
| December 4, 2025 | Google announced AI-powered configuration for the Performance report as an experimental feature. |
| December 10, 2025 | The BigQuery remote MCP server went into Preview. It is also the date of the earliest entry in the Google Cloud MCP servers release notes, which never mention Search Console. |
| February 18, 2026 | Claude Code 2.1.46 began loading connectors added on claude.ai. |
| April 20, 2026 | Google's BigQuery release notes marked the BigQuery MCP server Generally Available. |
| June 3, 2026 | Google introduced Search Generative AI performance reports in Search Console. The post does not say whether that data is in the API or in bulk data export. |
| June 22, 2026 | Claude Code 2.1.186 added claude mcp login and claude mcp logout for signing in to a server from the shell. |
| August 2026 | Ryze AI was listed in the Anthropic Directory, with the Community label. The listing gives a month, not a day. |
| September 28, 2026 | Claude Code 2.1.284 made interactive terminal and VS Code sessions start in auto mode on every plan and provider when no permission mode is set. Version 2.1.283, on September 25, had made that change for third-party providers and sessions with telemetry off. |
| November 6, 2026 | The community server mcp-search-console reached version 0.4.2 on PyPI, its newest on November 14, 2026. |
| November 14, 2026 | Google's supported-products list (stamped November 12), its MCP repository and the Search Console API pages showed no Search Console MCP server, connector or plugin. |
Sources: URL Inspection API launch, Bulk data export announcement, Hourly data, AI-powered configuration, Search Generative AI performance reports, BigQuery release notes, Google Cloud MCP release notes, Claude Code changelog, Remote MCP in Claude Code, Ryze AI in the Anthropic Directory, mcp-search-console on PyPI. Checked November 14, 2026.
How this guide was tested
Checks for this page ran on two days: calls from Claude Code through the connector on November 14, 2026, and a look at the connector's sign-in endpoints on November 19, 2026. Each row is one check and what it returned.
| What was run | What came back |
|---|---|
| A request to https://connector.get-ryze.ai/mcp with no sign-in (November 19) | HTTP 401, with a WWW-Authenticate header that points to the protected resource metadata. Claude Code's docs say a server that answers 401 is marked as needing authentication. |
| The authorization server file on the connector's host (November 19) | It loaded. It names the authorize, token and register endpoints, the authorization code and refresh token grants, the PKCE methods S256 and plain, and the scopes mcp:read and mcp:write. |
| The 7 Search Console tool definitions, loaded from the connector's tool list (November 14) | Each came back under its exact name as 5 read tools, 1 write tool and 1 delete tool. Every tool takes a workspace and an optional connection_id, and all but listSites require a siteUrl. |
| One property list (November 14) | listSites worked. |
| Two Search Analytics reads (November 14) | One with an equals filter on a random string came back empty. One over 90 days with a regex filter on query returned rows, as the tested calls table shows. |
| Three calls built to fail (November 14) | Each came back as HTTP 400 from Google. The exact messages are in the errors table. |
Not run for this page: the setup steps inside Claude Code. The claude mcp add command, the /mcp sign-in, the workspace choice and claude mcp get were not run for this guide; they follow Anthropic's Claude Code docs as read on November 14, 2026, and Ryze AI's own setup steps. The calls ran in a Ryze AI test workspace with a Search Console connection, and the Connect and Site steps in Ryze AI are not part of this record. The API key route and the claude.ai connector route were not tried. inspectUrl, listSitemaps and getIndexationSummary were not run. submitSitemap and deleteSitemap were not run, because they change Search Console. Grouping by page, country, device, search appearance or date, and the image, video, news and Discover types, were not run. No call tested a restricted-user login or hit a quota. The other ways in the table were not run.
Errors and fixes
Exact Search Console messages from the test
These three messages came back during the test on November 14, 2026. The connector returned each failure as Error 400 followed by Google's JSON error body. The messages contain no ID, email, domain or name from the account.
| Message | Cause | Fix in Claude Code |
|---|---|---|
| '25001' is not a valid row limit value. For valid row limit values see https://developers.google.com/webmaster-tools/search-console-api-original/v3/searchanalytics/query#rowLimit. | rowLimit was above the maximum of 25,000 rows per request. Google's reply came as HTTP 400, reason invalidParameter. | Ask for 25,000 rows or fewer and page with startRow. |
| Invalid value at 'dimension[0]' (type.googleapis.com/google.searchconsole.v1.searchanalytics.ApiDimension), "keyword" | The dimension name does not exist. Search terms are the dimension query. Google's reply was HTTP 400, status INVALID_ARGUMENT. | Use query, page, country, device, searchAppearance or date. |
| Invalid date range defined by startDate and endDate. End date cannot precede the start date. | The end date was earlier than the start date. | Swap the dates. Both use YYYY-MM-DD. |
Two other messages are documented and did not come up in the test: quota exceeded, which Google returns for every quota event and which asks you to wait 15 minutes, and request timed out, which the Ryze AI tool definition names as the answer when Search Console does not respond in time.
Sources: Search Console API usage limits, searchanalytics.query reference. Checked November 14, 2026.
Other problems
- Claude Code says the server failed to connect with an API key
- If a configured Authorization header is rejected, Claude Code reports the connection as failed and does not fall back to OAuth. Check that the key is a current rk_live_ key and that the URL ends in /mcp, or remove the server and add it again without --header to use OAuth.
- claude -p or an Agent SDK run cannot sign in
- Those runs cannot run the OAuth flow. Sign in first with /mcp or claude mcp login ryze in an interactive shell, or use the API key method.
- The server does not load from .mcp.json
- Project-scoped servers wait for approval in an interactive session before they connect. Approve it when Claude Code asks.
- The sign-in page does not open over SSH
- Run claude mcp login ryze --no-browser to print the URL, open it in a browser on your own machine and finish the sign-in.
- No Search Console tools appear
- If the connector was added before Google Search Console was connected, remove and re-add it with claude mcp remove ryze and claude mcp add, then start a new session. Tool search is on by default, so tools are loaded on demand and may not be listed up front.
- The Google Search Console card shows Require setup
- No Site is saved yet. Open the card in Ryze AI, check the Site and click Save.
- Claude Code can only list workspaces
- The Search Console tools need an active Ryze AI plan or free trial. Without one, the connector can only list workspaces and connect platforms. Start the trial in Ryze AI and retry.
- A query comes back empty
- A filter that matches nothing returns a response with no rows key, as the test showed for an equals filter on a random string. Check the filter, the search type and the date range, and remember that data runs 2 to 3 days behind.
- A call times out or quota runs out
- Per the Ryze AI tool definition, resend a timed-out request once on its own, never in parallel, and if it times out again narrow it with a shorter date range, one dimension and no regex filter. If Google reports quota exceeded, wait 15 minutes. Claude Code also has a five-minute idle timeout for HTTP servers.
- A result is saved to a file
- Claude Code warns above 10,000 tokens, and above its 25,000-token default it writes the result to a file and gives the session the path. Ask for fewer rows or a shorter date range, or raise MAX_MCP_OUTPUT_TOKENS.
- A property is missing or access is refused
- Ryze AI sees only the properties the connected Google login can access. Ask Claude Code to run listSites to see the properties and permission levels the login has, or add another Google login with Add one more account. The refusal message for a login without access was not captured in the test.
- Sitemap changes fail for a restricted login
- Google's table lists Submit sitemap for owners and full users and leaves the restricted user cell empty. No call tested this, so treat it as a likely cause and check the login's permission level with listSites.
Terms on this page
- MCP
- Model Context Protocol, which Anthropic open-sourced on November 25, 2024. Claude Code uses it to call tools on outside servers such as the Ryze AI connector.
- Server scope in Claude Code
- Where claude mcp add saves a server: local for one project, user for all your projects, project for a shared .mcp.json. It has nothing to do with Google's OAuth scopes.
- Domain property
- A Search Console property that aggregates data for all subdomains, protocols and subpaths of the property. In the API its siteUrl is written sc-domain:example.com, and it needs DNS verification unless it sits on a Google product such as Blogger or Google Sites.
- URL-prefix property
- A property that includes only URLs with the specified prefix, including the protocol. In the API a URL-prefix siteUrl must include a trailing slash.
- Average position
- Google defines it as the average position of the topmost result from your site.
- Anonymized queries
- Queries Google omits from the report to protect user privacy. Bulk data export leaves them out too.
- dataState
- A Search Analytics setting. With all, the API includes fresh data that may be incomplete; with final or no value, only finalized data comes back.
Sources: Model Context Protocol announcement, Claude Code MCP, Property types, URL Inspection reference, Performance report metrics, Anonymized queries, searchanalytics.query reference. Checked November 14, 2026.
Frequently asked questions
How do I connect Claude Code to Google Search Console?
Connect Google Search Console in a Ryze AI workspace and save a Site, then run claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp. Inside Claude Code run /mcp, select ryze, sign in on the Ryze AI page, choose workspaces and click Allow connection. Check it with claude mcp get ryze.
Is there a Google Search Console connector for Claude Code?
Yes. The Ryze AI connector at https://connector.get-ryze.ai/mcp serves 7 Search Console tools to Claude Code, and Composio, Windsor.ai and Coupler.io also host Search Console connectors that name Claude Code on their pages. Google lists none of its own.
Does Google Search Console have an MCP server?
None was found on Google's pages on November 14, 2026. Google's list of products with a remote MCP server has no Search Console row, its MCP repository has no Search Console entry and the Search Console API pages mention no MCP. Google documents the Search Console API and bulk data export to BigQuery instead.
What is the Google Search Console MCP URL for Claude Code?
For the Ryze AI connector it is https://connector.get-ryze.ai/mcp, added with claude mcp add --transport http. Third-party servers have their own addresses, such as https://mcp.windsor.ai for Windsor.ai, and the open-source mcp-gsc server has no URL because it runs on your machine.
Which Search Console connector should I use with Claude Code?
Use the Ryze AI connector if you want a hosted URL and Google sign-in handled for you, and accept that it needs a Ryze AI plan. If you want to keep the pipeline yourself, the Search Console API or a BigQuery export needs no Ryze AI plan but needs your own code or Google Cloud project.
Can Claude Code change my Search Console settings?
In two ways only. submitSitemap submits or resubmits a sitemap and deleteSitemap removes one from Search Console, leaving the file on your site untouched. The other 5 tools only read, and there is no tool to request indexing, remove URLs from Google or verify a property.
Can Claude Code request indexing for a URL?
No. The 7 tools include inspectUrl, which reports the index status of one URL, but none asks Google to crawl or index a page. Request indexing in Search Console itself.
Which Claude plan do I need for Claude Code?
Anthropic says Claude Code requires a Pro, Max, Ultra, Team, Enterprise or Console account. The free claude.ai plan does not include it. Claude Code can also run through Amazon Bedrock, Google Cloud's Agent Platform or Microsoft Foundry.
Should I use OAuth or an API key?
OAuth through /mcp is the simplest for a personal machine. An API key from Workspace Settings, Profile, API keys suits scripts, because claude -p and Agent SDK runs cannot run the OAuth flow. The key works on the /mcp endpoint only.
How many rows can one Search Console query return?
Up to 25,000 rows per request. Google's default is 1,000, and a request for 25,001 was refused with HTTP 400 in the November 14, 2026 test. For more rows, repeat the call with startRow until a response has 0 rows.
Why is the last day or two missing from my data?
Google says Search Console data is typically available after 2 to 3 days. Asking with dataState all includes fresh data, but some of those rows may be incomplete. Search Console keeps the last 16 months.
Does it work with Domain and URL-prefix properties?
The November 14, 2026 test ran against a Domain property, whose siteUrl is written sc-domain:example.com. Google's API also takes URL-prefix properties, which need a trailing slash. Run listSites to see how Search Console lists each property.
What does the claude mcp add scope change?
Local scope, the default, keeps the server to the current project and out of version control. User scope loads it in all your projects. Project scope writes .mcp.json so the team shares it, and each person approves it in an interactive session.
Why do the Search Console tools not show up?
If the connector was added before Search Console was connected, remove and re-add it, then start a new session. Run /mcp to check the server status. If a claude.ai connector is missing, you must be logged in with a claude.ai subscription account.
How much does it cost?
Connecting the connector is free, but the 7 Search Console tools need an active Ryze AI plan or free trial. SEO Starter is $129 per month with a 3-day free trial, Paid Ads is $89 per month with a 7-day free trial and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect Search Console from Claude Code?
Run claude mcp logout ryze, then claude mcp remove ryze, because remove alone does not revoke the stored tokens. To remove Google access, disconnect Google Search Console on its card in Ryze AI.