How to connect Cursor to Google Search Console

Connect a Search Console property once in Ryze AI, add one MCP URL to Cursor, then ask Cursor for queries, pages, sitemaps and the index status of a URL.

Your MCP URL
https://connector.get-ryze.ai/mcpAdd to Cursor

Copies the link and opens the Cursor install prompt for the ryze server. See the steps

See pricing

By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026

Quick answer

The main way to connect Cursor to Google Search Console is the Ryze AI connector. Connect Search Console in Ryze AI with a Google login that has access to your property and save the Site, then add https://connector.get-ryze.ai/mcp to Cursor with the Add to Cursor link or a url entry in mcp.json and sign in when Cursor asks. Cursor then works with 7 Search Console tools: 5 read data, 1 submits a sitemap and 1 removes one.

  1. In Ryze AI open Integrations, click Connect on Google Search Console and approve the Google screen
  2. Check the Site for your workspace and click Save
  3. In Cursor add the Ryze AI server (Add to Cursor link or mcp.json) and finish the sign-in
  4. Start a new Cursor chat, approve the tool call and ask which properties your login can reach

Cursor to Google Search Console at a glance

FactDetail
Main way to connectThe Ryze AI connector, a hosted MCP address that Cursor takes through an install link or one url entry in mcp.json
Address to addhttps://connector.get-ryze.ai/mcp
How Cursor signs inOAuth with PKCE in your browser. Cursor registers itself as a client, so you paste no client ID. A Ryze AI API key in a headers entry is the other option
Google sideOne Google sign-in inside Ryze AI with the Search Console scope, webmasters, which covers reading data and submitting or removing sitemaps
Search Console tools7: the property list, Search Analytics queries, URL inspection, sitemap list, sitemap summary, sitemap submit and sitemap delete
Can Cursor change thingsYes, in two ways only: submit or resubmit a sitemap, and remove one from Search Console. Everything else reads
Other data in the same chatOther platforms connected in the same Ryze AI workspace are served from the same address
Cursor planCursor's MCP page names none. Enterprise admins can limit which servers a team may run
Ryze AI priceSEO Starter at $129 a month with a 3-day free trial, or Paid Ads at $89 a month with a 7-day free trial. Adding the connector costs nothing
Google's own route in CursorNone found. No Search Console MCP server appeared on Google's pages on November 14, 2026. Google's BigQuery MCP server lists Cursor and can read an exported copy of the data
TestedSearch Console calls sent through the connector from Claude Code on November 14, 2026. The steps inside Cursor were not run

Before you start

  • A Cursor install. Cursor's MCP documentation names no plan for using MCP servers. On Enterprise, admins can control which MCP servers users may run in Team Settings > MCP Configuration, so a blocked server needs an admin to allow it.
  • A Google login with access to a Search Console property. The property must be verified. Google's permission levels are Owner, Full user and Restricted user, and Google lists submitting a sitemap for owners and full users. Keep every requested permission checked on the Google screen.
  • A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial; the 7 Search Console tools also work on Paid Ads ($89 per month, 7-day free trial). Adding the connector is free, but the tools need an active plan or trial.

How to connect Cursor to Google Search Console

Two steps happen in Google and Ryze AI, two in Cursor, and one when you ask. The connector URL is the same for every user.

  1. 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 with every requested permission checked.

  2. Check 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.

  3. Add the Ryze AI server to Cursor

    Either use the Add to Cursor link on this page or the Ryze AI developers page, which opens a cursor:// install link for a server named ryze at https://connector.get-ryze.ai/mcp, or create ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project) with the url entry shown below.

    { "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }
  4. Sign in from Cursor

    Confirm the install in Cursor. Cursor runs OAuth with PKCE and dynamic client registration, so there is no client ID or secret to enter. Sign in on the Ryze AI page and click Allow connection. You can manage or toggle the server from the Customize page in the sidebar.

  5. Ask your first question in Cursor

    Start a new chat in Cursor, approve the tool call when Cursor asks, and try: List the Search Console properties my login can access, then show the top 20 queries by clicks for the last 28 days.

The Ryze AI help center page for Google Search Console covers the Google Search Console side of the connection. Cursor does not have its own Ryze AI help page; the Ryze AI developers page has the Add to Cursor link and the matching config.

Sources: Cursor MCP documentation, checked November 13, 2026; Ryze AI Google Search Console guide.

mcp.json, API key and Cloud Agents

mcp.json

Save this as ~/.cursor/mcp.json for every project or .cursor/mcp.json for one project. Cursor accepts remote servers through the url field and handles the OAuth sign-in itself.

{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }

Cursor supports stdio, SSE and Streamable HTTP transports. For OAuth it reads the server's protected resource metadata (RFC 9728) and registers as a public client through dynamic client registration. After sign-in, manage or toggle the server from the Customize page in the sidebar.

mcp.json with a Ryze AI API key

If you prefer a key to the browser sign-in, add a headers entry and set RYZE_API_KEY in your environment to the rk_live_ key from Ryze AI under Workspace Settings > Profile > API keys. Keep the key out of files you commit.

{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp", "headers": { "Authorization": "Bearer ${env:RYZE_API_KEY}" } } } }

Cloud Agents

Cursor Cloud Agents keep their own MCP sign-ins on Cursor's servers, separate from the sign-in on your desktop. If a Cloud Agent needs Search Console data, connect the Ryze AI server for it as well.

Cursor's MCP support in one table

TopicWhat Cursor's documentation says
Config file locations~/.cursor/mcp.json covers every project you open; .cursor/mcp.json inside a repository covers that repository alone
Entry for a hosted serverA server name under mcpServers that holds a url. An optional headers object can sit beside it
Local serversSupported over stdio, for servers that Cursor starts on your computer
Transportsstdio, SSE and Streamable HTTP
Signing in to a serverOAuth for any server that asks for it. Cursor registers as a public client without a secret through dynamic client registration, or you give it fixed client credentials in mcp.json
Values Cursor fills in${env:NAME} for an environment variable, plus ${userHome}, ${workspaceFolder}, ${workspaceFolderBasename} and ${pathSeparator}
Approving tool callsCursor asks first by default. With Auto-review on, allowlisted MCP tools run at once and the rest pass through Cursor's classifier
What Cursor uses from a serverTools, resources, prompts and elicitation
Where to manage serversCustomize in the sidebar. Team admins have Dashboard > Plugins & MCPs and Team Settings > MCP Configuration, and Enterprise admins can set an MCP Allowlist
Cloud AgentsCan call MCP servers, with sign-ins held apart from the desktop app
Install linkcursor://anysphere.cursor-deeplink/mcp/install, carrying the server name and a base64 copy of its config
Plan or server capCursor's MCP page states neither

Sources: Cursor MCP documentation, Cursor MCP install links. Checked November 13, 2026.

Claude and ChatGPT

The same URL works in other MCP clients. Google Search Console is connected once in Ryze AI, so nothing changes on the Google Search Console side.

Claude

Add https://connector.get-ryze.ai/mcp as a custom connector under Customize > Connectors, pick the workspace and start a new chat. If the connector was added before Search Console was connected, remove and re-add it, then start a new chat.

ChatGPT

In ChatGPT on the web, open Plugins, add a custom MCP server with the same URL and choose OAuth, then sign in to Ryze AI, pick the workspace and start a new conversation. OpenAI gives full custom MCP support on Business and Enterprise/Edu, and read and fetch only on Pro. Re-add the server if Search Console was connected in Ryze AI afterwards, so the tool list refreshes.

Google Search Console access and scopes

Two sign-ins are involved: Google for Search Console access and Ryze AI for the connector. Three things decide what Cursor can reach.

Which property
The Google login must have access to the property, and you check the Site for the workspace after connecting. Several Google logins can be connected to one workspace with Add one more account, each with its own Site, and one is the primary (set with the star). Tools take an optional connection_id to name another login.
What Cursor can change
Two things in Search Console: submit or resubmit a sitemap, and remove a sitemap from the property. The sitemap file on your site stays untouched. There is no tool to request indexing, remove a URL from Google or verify a property.
What Cursor asks first
Cursor asks for approval before using MCP tools by default and follows the same Run Modes as terminal commands, so each tool call waits for your click unless you allowlist the tool. To keep the two changing tools behind a click, leave them off your allowlist.

Scope needed per job

Ryze AI connects with the Search Console scope called webmasters. The table maps each job to the access it needs.

JobScope needed
Run Search Analytics querieswebmasters or webmasters.readonly; the connection holds webmasters
Inspect one URLwebmasters or webmasters.readonly
List properties and sitemapswebmasters or webmasters.readonly
Submit or delete a sitemapwebmasters only, so these two tools need the read and write scope
Add or remove a property, request indexing, verify ownershipNot available: the connector has no tool for them

The two Google scopes

What Cursor can reach in Search Console comes from two things: the scope you approve on Google's consent screen and the permission level your Google login holds on the property. Google writes that you need appropriate access (owner, full, read) to any account you reach through the API. The scope table below quotes what Google says each scope allows.

ScopeGoogle's descriptionIn practice
webmastersRead/write accessThe scope the Ryze AI connection holds. It covers the 5 read tools and the two sitemap tools that change things, because Google lists sitemaps.submit and sitemaps.delete with this scope only
webmasters.readonlyRead-only accessNot the one Ryze AI holds. Google accepts it for Search Analytics, URL Inspection, sites.list and sitemaps.list

Not included: sites.add and sites.delete, so Cursor cannot add a property to your list or remove one, and no tool requests indexing, removes URLs from Google or verifies ownership. Google's permissions table describes the Search Console interface and does not map each permission level to API methods, so a restricted login was not tested with a sitemap write. If a write fails, check the level with listSites first.

Sources: Search Console API authorizing, searchanalytics.query reference, sitemaps.submit reference, sitemaps.delete reference, Search Console permissions. Checked November 14, 2026.

Removing access

To remove access, disconnect Google Search Console on its card in Ryze AI or remove Ryze AI from your Google Account's third-party access page. In Cursor, toggle the ryze server off from Customize or delete its entry from mcp.json.

What Cursor can do in Google Search Console

The Ryze AI connector exposes 7 Search Console tools: 5 read, 1 write and 1 delete.

ToolTypeWhat it does
google_search_console__listSitesReadLists every Search Console property the connected login can access, with permission levels.
google_search_console__runRawSearchAnalyticsReadRuns 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__inspectUrlReadInspects one URL's index status: coverage, verdict, last crawl, canonical, indexing state, mobile usability and rich results.
google_search_console__listSitemapsReadLists the sitemaps Search Console knows for a property, with last submitted and downloaded dates, errors, warnings and submitted counts.
google_search_console__getIndexationSummaryReadReturns a sitemap summary for a property: number of sitemaps, submitted URLs, errors, warnings and pending items.
google_search_console__submitSitemapWriteSubmits or resubmits a sitemap to Search Console for a property.
google_search_console__deleteSitemapDeleteRemoves a sitemap from Search Console for a property. The sitemap file on the site is not touched.

Search Console data arrives 2 to 3 days late and Google keeps 16 months of it. Index coverage for every URL of a site is not available through the API, so inspection runs one URL at a time. A URL-prefix property leaves out traffic outside that exact prefix, while a Domain property covers all subdomains and protocols. The tools work only while the Ryze AI workspace has an active plan or free trial.

Cursor asks before it runs an MCP tool by default. Keep that default if you want to review each call, or allowlist only the read tools. In the Ryze AI chat, submitSitemap and deleteSitemap follow the Tool approvals setting, which starts on Skip all approvals and can be switched to Approve write & delete or Manual approve. Scheduled tasks run without an approval step.

Search Console limits in numbers

Google applies these limits to the Search Console API, so they hold for any server that calls it. Rows come from Google's pages as read on November 14, 2026, unless a row names the test, the Ryze AI tools or Cursor.

LimitNumber
Search Analytics request rate1,200 queries per minute per site and per user. Per project: 30,000,000 per day and 40,000 per minute
Search Analytics loadShort-term quota is measured in 10 minute chunks and long-term quota in 1 day chunks. Queries grouped or filtered by page and query string cost the most, and load grows with the date range. Past the quota, Google says to wait 15 minutes and try again
URL Inspection2,000 queries per day and 600 per minute per site. Per project: 10,000,000 per day and 15,000 per minute
Sites and sitemaps20 queries per second and 200 per minute per user. Per project: 100,000,000 per day
Rows per request1 to 25,000, with 1,000 when you name no limit. Re-run the query with startRow raised by 25,000 until a response comes back with 0 rows
Rows per dayGoogle says the method exposes a maximum of 50K rows of data per day per search type, sorted by clicks
Data delayData is typically available after 2-3 days. dataState all adds fresh data that may be incomplete, while final or no value returns finalized data only
HistorySearch Console keeps data for the last 16 months
Time zonestartDate and endDate are YYYY-MM-DD in Pacific Time
FiltersDimensions country, device, page, query and searchAppearance, with operators such as contains, equals, notContains, notEquals and regex. Only the and group type is listed
URL Inspection scopeOne URL per call, and only the version in the Google index. Google says you cannot test the indexability of a live URL
Ryze AI tool inputrunRawSearchAnalytics states a maximum of 25,000 rows per request. A rowLimit of 25001 was refused with HTTP 400 in the test
CursorNo cap on servers or tools appears on its MCP page

Sources: Search Console API usage limits, Getting all your data, searchanalytics.query reference, urlInspection.index.inspect reference, Search Console data retention, Search Console API pricing. Checked November 14, 2026.

Calls tested through the default connection

Claude Code sent these 6 calls through the Ryze AI connector on November 14, 2026, on the default connection to a Domain property. Cursor did not send them. Three calls asked for data and worked, and three were built to fail. The property belongs to a real account, so this table shows field names and outcomes only.

ToolWhat was sentWhat came back
listSitesThe workspace and nothing elseThe call worked
runRawSearchAnalytics7 days, dimension query, rowLimit 25001Refused by Google with HTTP 400
runRawSearchAnalyticsA dimension named keyword, which does not existRefused by Google with HTTP 400, status INVALID_ARGUMENT
runRawSearchAnalyticsAn end date before the start dateRefused by Google with HTTP 400
runRawSearchAnalytics7 days, dimension query, an equals filter on a random 20-letter stringWorked with an empty result: the whole response was responseAggregationType byProperty and no rows key
runRawSearchAnalytics90 days, dimension query, rowLimit 120, dataState all, an includingRegex filter on queryWorked. Each row carried keys, clicks, impressions, ctr and position, ordered by clicks with the highest first. Fewer rows than rowLimit came back, so no second page was needed

First 3 prompts to run

1. Find the property and the top queries

List the Search Console properties I can access with my permission level, then show the top 25 queries by clicks for the last 28 days with impressions, CTR and average position.

Tools used: google_search_console__listSites, google_search_console__runRawSearchAnalytics

What comes back: A list of properties, then a table of queries from your own property. Search Console data runs 2 to 3 days behind, so the newest days are missing.

2. Find pages that rank near the click zone

Group the last 90 days by page and query, keep rows with an average position between 8 and 20 and at least 100 impressions, and sort them by impressions.

Tools used: google_search_console__runRawSearchAnalytics

What comes back: A list of page and query pairs that sit just outside the top results. Grouping by page and query is the most expensive kind of Search Analytics query, so a shorter date range may be needed.

3. Check a sitemap and one URL

List the sitemaps for this property with their last downloaded dates, errors and warnings, then inspect the URL of my newest article and tell me its coverage, canonical and last crawl.

Tools used: google_search_console__listSitemaps, google_search_console__inspectUrl

What comes back: Sitemap rows with dates, errors and warnings, then the index status of one URL. Nothing in Search Console is changed.

Each answer comes from your own property, so this page describes what comes back instead of showing sample numbers. Replace the names in the prompts with ones from your property.

10 jobs to hand to Cursor

Ten jobs to type into a Cursor chat, each with the tool that answers it. listSites and runRawSearchAnalytics were called from Claude Code in the test on November 14, 2026. The other tools were loaded and left uncalled. The last job is one this connection cannot do.

JobAsk CursorToolWorks on the default connection
Property listList every Search Console property my login can reach and the permission level on each.google_search_console__listSitesYes, run in the test
Top queriesShow the top queries for the last 28 days with clicks, impressions, CTR and average position.google_search_console__runRawSearchAnalyticsYes, run in the test
Query filterShow only queries that contain how to or match a question pattern, for the last 90 days.google_search_console__runRawSearchAnalyticsYes. Equals and regex filters on query were run in the test
Near-miss pagesWhich pages rank just outside the positions that earn clicks, and for which queries?google_search_console__runRawSearchAnalyticsYes. Grouping by page was not run in the test
Country and device splitSplit clicks and impressions by country, then by device, for the last month.google_search_console__runRawSearchAnalyticsYes. Not run in the test
One page over timeChart daily clicks and impressions for one article since it was published.google_search_console__runRawSearchAnalyticsYes. Grouping by date was not run in the test
Discover, news, image and videoShow Discover performance instead of web results for the last 28 days.google_search_console__runRawSearchAnalyticsYes. Result types other than web were not run in the test
Index statusInspect this URL and tell me its verdict, last crawl and canonical.google_search_console__inspectUrlYes. One URL per call, 2,000 a day per site
Sitemap healthList my sitemaps with errors and warnings, and give me the property summary.google_search_console__listSitemaps, google_search_console__getIndexationSummaryYes. Not run in the test
Request indexingAsk Google to index this new URL now.NoneNo. No tool requests indexing, so use the Search Console interface

7 ways to connect Cursor to Google Search Console

Seven ways can put Search Console data into Cursor, because Cursor takes both hosted addresses and servers that run on your computer. This guide treats the Ryze AI connector as the main way: Google is approved once inside Ryze AI, and Cursor keeps one address and a browser sign-in, with no Google Cloud project and no key file on your machine. The other six were read on their own pages on November 14, 2026. None of them was run for this guide.

WayRuns whereSetup in CursorWhat it reaches in Search ConsolePrice
Ryze AI connector (the main way)Hosted. The same address carries the other platforms connected in the workspaceThe Add to Cursor link or a url entry in mcp.json, then the browser sign-in7 tools: 5 read, 1 sitemap submit, 1 sitemap delete. No indexing requestsSEO Starter at $129 a month with a 3-day free trial, or Paid Ads at $89 a month with a 7-day free trial; the connector itself is free
mcp-gsc by AminForou (PyPI package mcp-search-console), open sourceOn your computer, started by Cursor with uvx mcp-search-consoleAn entry in ~/.cursor/mcp.json as the README shows, after you create your own OAuth client ID of type Desktop app in Google Cloud, or use a service account key and add its email under Users and permissions in Search Console. The README also lists a one-click install in the Cursor MarketplaceThe README mentions 20 tools and its table names 15, among them search analytics, URL inspection, batch inspection of up to 10 URLs and sitemap management. add_site, delete_site and delete_sitemap are off by default and need GSC_ALLOW_DESTRUCTIVE=true. Since 0.4.2 it asks for the read-only scope by defaultFree, MIT license. 2,202 GitHub stars on November 14, 2026, last push November 6, 2026
ComposioHostedComposio lists Cursor among its assistants. The remote address is https://connect.composio.dev/mcp, and you authorize Google Search Console on first use14 tools that read and write, among them Add Site, Delete Site, Inspect URL, Search Analytics Query, Submit Sitemap, Verify Site OwnershipPricing page: Free with 10,000 tool calls a month, Standard $18 per seat per month. Its toolkit page gives a different free figure, 100,000 calls, so check the page you use
Coupler.ioHosted, on a copy of the data that Coupler.io syncs on a scheduleBuild a Search Console data flow, add Custom MCP as its destination, generate a token and paste the server URL into Cursor. The page names Cursor and the token goes in an Authorization: Bearer headerRead-only on synced data. No sitemap management, URL submission or Indexing API calls. Refresh as often as every 15 minutesFree plan with manual refresh and 1 data source. Starter is $32 a month, or $24 billed annually
Windsor.aiHostedWindsor's page lists Claude, ChatGPT, Gemini and Copilot. Cursor appears there only in the column for its open-source server, so check Windsor's own guides before relying on itRead-only: clicks, impressions, CTR and position plus a few extra fields. No URL inspection, and Discover and Google News data are left outFree after a 30-day trial with 1 data source. Basic is $23 a month, or $19 billed annually
ahonn/mcp-server-gsc, open sourceOn your computer, started with npxThe README shows an npx config for Claude Desktop; an mcpServers entry in Cursor takes the same command. Needs a service account through GOOGLE_APPLICATION_CREDENTIALSOne tool, search_analytics, with a rowLimit default of 1,000 and a maximum of 25,000Free. 286 GitHub stars, last push September 4, 2026
Google BigQuery MCP over a bulk data exportGoogle Cloud (BigQuery); the export is a Search Console settingTurn on Bulk data export for a property, then add https://bigquery.googleapis.com/mcp to Cursor. Google's client guidance has a Cursor section. Google's remote MCP servers do not support Dynamic Client Registration, so you use Application Default Credentials or an OAuth client you createPerformance data only, from the day the export starts, with anonymized queries left out. No URL inspection and no sitemap actions. Query results stop at 3,000 rows. Google does not describe the pair as a Search Console connector and this guide did not run itGoogle Cloud storage and query costs, with a free usage level. Only property owners can set up the export

Options that do not fit this job

  • Google's own Search Console MCP server. None was found on Google's pages on November 14, 2026. The supported-products list for Google remote MCP servers has no Search Console row, Google's MCP repository has no entry for it, and the 14 Search Console API pages opened contain no mention of MCP. Windsor.ai's page makes the same statement, as a vendor and not as Google.
  • The Search Console API on its own. It is free and subject to usage limits, but it is a REST API for your own code with OAuth 2.0 and a Google Cloud project, not a connector Cursor can add by address. Google's API pages describe no MCP endpoint.
  • Google Developer Knowledge MCP server. Google lists Cursor as a client, but it searches Google's developer documentation and holds none of your Search Console data.
  • Zapier MCP. Zapier lists Cursor among its popular clients, but no Google Search Console page was found on Zapier on November 14, 2026: the addresses tried returned 404. That is an observation, not a statement from Zapier that the connection is impossible.
  • AI-powered configuration inside Search Console. An experimental feature in the Performance report that applies filters and comparisons from a plain-language request. It runs in the Google interface, covers only the Performance report for Search results and is limited to 20 requests per user per day. It does not connect an outside assistant.

Which one to pick

Ryze AI is the best way to connect Cursor to Google Search Console when you want queries, URL inspection and sitemaps in a chat with nothing to install or keep running, with one caveat: it cannot add or verify a property or request indexing, and the Search Analytics tools return raw rows that you sort yourself in chat. Choose mcp-gsc if you want a local server you control, with batch inspection and your own Google Cloud credentials. Both can sit in mcp.json at the same time. Composio suits teams that already use it for other apps. Coupler.io and Windsor.ai suit teams that already pipe marketing data through them. The BigQuery route suits teams that already keep a Search Console export in BigQuery.

Sources: Google MCP supported products, Google MCP repository, Search Console API, mcp-gsc on GitHub, mcp-search-console on PyPI, mcp-server-gsc on GitHub, Composio Google Search Console toolkit, Composio pricing, Coupler.io Google Search Console MCP, Coupler.io pricing, Windsor.ai Google Search Console MCP, Windsor.ai pricing, Zapier MCP quickstart, Bulk data export help, BigQuery MCP server, Google MCP authentication, Developer Knowledge MCP server, AI-powered configuration. Checked November 14, 2026.

Cursor side: Cursor MCP documentation, checked November 13, 2026. Ryze AI side: Ryze AI Google Search Console guide.

Google Search Console and MCP: dates that matter

DateWhat happened
January 31, 2022The URL Inspection API launched, with 2,000 queries per day and 600 per minute per Search Console property.
February 21, 2023Google announced bulk data export to BigQuery.
April 9, 2025The Search Analytics API gained hourly data: an HOUR dimension and dataState HOURLY_ALL, for up to 10 days. The Ryze AI tool definition does not list hour, and it was not tested.
December 4, 2025Google announced AI-powered configuration for the Performance report as an experimental feature.
December 10, 2025Google's BigQuery release notes added the BigQuery remote MCP server in Preview. The earliest entry in Google Cloud's MCP release notes has the same date, and none of its entries mention Search Console.
April 20, 2026Google's BigQuery release notes list the BigQuery MCP server as Generally Available.
June 3, 2026Google introduced Search Generative AI performance reports in Search Console. The post does not say whether that data reaches the API or bulk export.
August 11, 2026Google last updated the searchanalytics.query reference page.
November 6, 2026mcp-search-console 0.4.2, the newest release on November 14, 2026, went to PyPI. It asks for the read-only scope by default.
November 12, 2026Google last updated its list of products with a remote MCP server. It has no Search Console row.

Sources: URL Inspection API launch, Bulk data export announcement, Hourly data in the API, AI-powered configuration, Search Generative AI performance reports, BigQuery release notes, Google Cloud MCP release notes, mcp-search-console on PyPI, Google MCP supported products. Checked November 14, 2026.

How this guide was tested

The Search Console calls ran on November 14, 2026, through the Ryze AI connector on a test workspace with Google Search Console connected through the default Google sign-in. Here is what was checked and what came back.

What was runWhat came back
The Search Console tool list, loaded from Claude Code through the connectorAll 7 definitions loaded by their exact names, with 5 read, 1 write and 1 delete.
One listSites callIt worked.
Two Search Analytics reads with filtersBoth worked: one empty result, and one with rows that carried keys, clicks, impressions, ctr and position.
Three requests made wrong on purposeEach came back as Error 400 with Google's JSON error inside. Their messages are in the errors table.

Not run for this page: any step inside Cursor. No server was added to mcp.json, no install link was opened, and no sign-in or tool call was made from Cursor, so those steps follow Cursor's MCP documentation as read on November 13, 2026. The calls came from Claude Code, which reaches the same server and the same 7 tools. inspectUrl, listSitemaps and getIndexationSummary were not called. submitSitemap and deleteSitemap were not called either, 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, and no call was sent to hit a quota or tested a restricted login. No call was made through any other way in the table.

Cursor and Google Search Console errors and fixes

Exact error messages from the test

Google returned these 3 messages in the test on November 14, 2026, each inside an Error 400 from the connector. If Cursor shows one of them, the row explains it.

MessageWhat it meansWhat to do in Cursor
'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. 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"keyword is not a dimension. Search terms are the dimension query. 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. HTTP 400, reason invalidParameter.Swap the dates. Both are YYYY-MM-DD.

Two more messages did not come up in the test. Google's limits page says the quota exceeded error is the same for every quota event, so wait 15 minutes and narrow the query. The tool definition for runRawSearchAnalytics names a request timed out answer for a request Search Console did not answer in time: resend it once on its own, then use a shorter date range, one dimension and no regex filter.

Source: Search Console API usage limits. Checked November 14, 2026.

Other problems

The Search Console tools do not appear in Cursor
If Search Console was connected in Ryze AI after the server was added, remove the ryze entry and add it again, then start a new chat so the tool list refreshes.
Cursor never asks me to sign in
Open Customize in the sidebar, find the ryze server and reconnect it. Cursor reads the connector's protected resource metadata and registers itself, so no client ID is needed.
The Ryze AI card says Require setup
No Site is saved yet. Open the Google Search Console card in Ryze AI, check the Site and click Save.
A tool answers that access is insufficient
Run listSites and look at the permission level on the property. Pick a property where your login is an owner or a full user, or ask an owner to raise the level. Submitting a sitemap is listed for owners and full users in Google's permissions table.
Queries are empty or the newest days are missing
Search Console data typically arrives after 2 to 3 days. Move the end date back, or ask for dataState all and read the newest rows as incomplete.
The wrong property comes back
The listSites definition says no site is selected for tool calls, so name the siteUrl. Domain properties are written sc-domain:example.com, and URL-prefix properties need the trailing slash.
A broad query is slow or times out
Shorten the date range, use one dimension and drop the regex filter. Grouping by page and query is the most expensive kind of query.
A Cloud Agent cannot reach Search Console
Cloud Agents keep their own MCP sign-ins on Cursor's servers. Connect the Ryze AI server for the agent separately from your desktop.
The server is blocked on a team account
Enterprise admins can allowlist which servers and tools the team may run. Ask an admin to allow the Ryze AI server in Team Settings > MCP Configuration.
The tools reply that a subscription is required
The Search Console tools need an active Ryze AI plan or free trial. Start the trial, then retry.

Terms on this page

MCP
Model Context Protocol. Cursor speaks it to reach tools that live outside the editor, such as the Ryze AI connector or a local Search Console server.
mcp.json
The file in which Cursor lists its MCP servers: ~/.cursor/mcp.json for all projects, .cursor/mcp.json for a single one.
Domain property
A property that Google says aggregates data for all subdomains, protocols and subpaths. In the API its siteUrl is written sc-domain:example.com, and ownership is verified with a DNS record.
URL-prefix property
A property that includes only URLs with the specified prefix, protocol included. In the API the prefix needs a trailing slash.
Average position
Google defines it as the average position of the topmost result from your site.
CTR
The click count divided by the impression count. The API returns a value from 0 to 1.
Anonymized queries
Queries Google omits from the report to protect user privacy. They are also left out of bulk data export.

Sources: Property types, Performance report metrics, Performance report and anonymized queries, searchanalytics.query reference. Checked November 14, 2026.

Frequently asked questions

How do I connect Cursor to Google Search Console?

Connect Google Search Console in Ryze AI under Integrations, check the Site, then add https://connector.get-ryze.ai/mcp to Cursor with the Add to Cursor link or a url entry in mcp.json. Sign in when Cursor asks.

Does Google Search Console have an MCP server?

No Google Search Console MCP server was found on Google's pages on November 14, 2026. Google's list of remote MCP servers has no Search Console row, and the Search Console API pages mention no MCP. Hosted connectors such as the Ryze AI connector and local servers such as mcp-gsc fill the gap.

Is there a Google Search Console MCP server for Cursor?

Yes, from other vendors. The Ryze AI connector at https://connector.get-ryze.ai/mcp is hosted and has 7 Search Console tools. The open-source mcp-gsc runs on your computer and its README shows a Cursor config and a Cursor Marketplace install.

What is the Search Console MCP server URL for Cursor?

For the Ryze AI connector it is https://connector.get-ryze.ai/mcp, one address for every user. A local server such as mcp-gsc has no address to paste, because Cursor starts it from a command entry in mcp.json.

Why does the Search Console tool say my permissions are insufficient?

Your Google login probably lacks the right permission level on that property. Ask Cursor to run listSites, read the permission level for each property and pick one where you are an owner or a full user. Google's table lists submitting a sitemap for those two levels.

What does an MCP server for Search Console do that the Search Console interface does not?

It lets Cursor ask in plain language and run Search Analytics queries, inspect a URL and list sitemaps without opening the interface. Google's interface has its own limited AI configuration feature, which runs only inside the Performance report and is capped at 20 requests per user per day.

Which should I use, Ryze AI or a local server?

Use the Ryze AI connector for a hosted address, a browser sign-in and nothing to run on your machine, accepting that it cannot add or verify properties or request indexing. Use mcp-gsc if you want a local server on your own Google Cloud credentials, with batch inspection of up to 10 URLs.

What Google access do I need?

A Google login with access to a verified Search Console property. Ryze AI connects with the webmasters scope, which covers reading data and submitting or removing sitemaps. Keep every requested permission checked.

Can Cursor change my Search Console settings?

Only sitemaps. The submitSitemap tool submits or resubmits one and deleteSitemap removes one from Search Console, leaving the file on your site alone. Cursor cannot request indexing, remove URLs from Google, add a property or verify one.

Which Cursor plan do I need?

Cursor's MCP documentation names no plan. On Enterprise, admins can control which MCP servers users may run in Team Settings > MCP Configuration.

Does Cursor ask before running a Search Console tool?

By default, yes. Cursor asks for approval before using MCP tools and follows the same Run Modes as terminal commands. You can allowlist the read tools and leave submitSitemap and deleteSitemap on the prompt.

How much Search Console data can Cursor read?

Search Analytics returns up to 25,000 rows per request, and you page with startRow for more. Google keeps 16 months of history and its data is typically available after 2 to 3 days.

Can I connect more than one Search Console account?

Yes. Connect several Google logins to one workspace with Add one more account, each with its own Site, and set one as primary with the star. Tools accept an optional connection_id. The help center advises a separate workspace for each client.

Can I use a Ryze AI API key instead of the browser sign-in?

Yes. Add a headers entry with Authorization set to Bearer followed by your rk_live_ key from Workspace Settings > Profile > API keys, and keep the key in an environment variable such as RYZE_API_KEY.

How much does it cost to connect Cursor to Google Search Console?

Adding the connector costs nothing, but the 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.

Connect Google Search Console to Cursor

Google Search Console connects once in Ryze AI, then Cursor queries Search Analytics, inspects URLs and lists sitemaps for the property you pick. SEO Starter is $129 per month with a 3-day free trial; annual billing takes 30% off the first year.

Need help? Read the Ryze AI help center page for Google Search Console or email Ryze AI support.