By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Codex to Google Search Console is the Ryze AI connector. Connect Google Search Console on its card in Ryze AI, then run codex mcp add ryze --url https://connector.get-ryze.ai/mcp followed by codex mcp login ryze. One entry serves the Codex CLI, the ChatGPT desktop app and the IDE extension, you create no Google Cloud project, and 5 of the 7 Search Console tools only read data.
- In Ryze AI open Integrations, click Connect on Google Search Console and sign in to Google with every permission checked
- Check the Site for the workspace and click Save
- In Codex run codex mcp add ryze --url https://connector.get-ryze.ai/mcp
- Run codex mcp login ryze, sign in on the Ryze AI page and click Allow connection
Codex to Google Search Console at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, a hosted MCP server that Codex reaches as a Streamable HTTP address |
| Server address | https://connector.get-ryze.ai/mcp |
| Commands in Codex | codex mcp add ryze --url https://connector.get-ryze.ai/mcp, then codex mcp login ryze for the browser sign-in |
| Google sign-in | Google OAuth with the Search Console scope webmasters, on a login that has access to a verified Search Console property. No Google Cloud project to create |
| Search Console tools | 7: 5 read tools, 1 write tool (submitSitemap) and 1 delete tool (deleteSitemap) |
| Can it change Search Console | Yes, in two ways: it can submit or resubmit a sitemap and remove one from Search Console. It has no tool to request indexing, remove URLs from Google or verify a property |
| Other data in the same chat | Any other platform connected in the same Ryze AI workspace is reachable through the same ryze entry |
| Codex surfaces | CLI, ChatGPT desktop app and IDE extension, all reading one config.toml. Free and Go plans get the desktop app only, subject to rollout |
| Ryze AI price | SEO Starter is $129 per month with a 3-day free trial; the 7 tools also work on Paid Ads at $89 per month with a 7-day free trial. Adding the connector is free; the tools need an active plan or trial |
| Google's own route for Codex | None found. Google's pages listed no Search Console MCP server, connector or plugin on November 14, 2026 |
| Last tested | November 14, 2026: 6 Search Console calls through the connector, from Claude Code. Nothing was run inside Codex |
Before you start
- An OpenAI plan that includes Codex. OpenAI lists Codex in ChatGPT Free, Go, Plus, Pro, Business, Edu and Enterprise. Its pricing page shows Free and Go with Codex in the desktop app only, subject to rollout, so on those plans use the desktop app steps. Plus and higher add the CLI and the IDE extension. Codex also runs with an OpenAI API key in the CLI, SDK or IDE extension, billed at API pricing. OpenAI's MCP page sets no plan condition for adding a server.
- A Google login with access to a verified Search Console property. Google's permission table gives owners and full users the Submit sitemap action, and restricted users can view performance data. Whether a restricted user's login can run submitSitemap through the API was not tested. A Domain property covers every subdomain and protocol; a URL-prefix property covers only URLs under its exact prefix.
- A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial, because Search Console feeds the Ryze AI SEO agent. Paid Ads is $89 per month with a 7-day free trial and Agency is $279 per month; the 7 Search Console tools work on any active plan or trial. Adding the connector is free.
How to connect Codex to Google Search Console with the CLI
Two steps happen in Ryze AI and three in Codex. The server 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.
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.
Add the Ryze AI server to Codex
Run codex mcp add ryze --url https://connector.get-ryze.ai/mcp. In the ChatGPT desktop app or the IDE extension, use the MCP servers settings instead (see the sections below). All three share one MCP configuration.
Sign in and allow the connection
Run codex mcp login ryze, sign in on the Ryze AI page and click Allow connection. Without a local browser, add --no-browser, open the printed URL and paste the full redirect URL back into the terminal. Inside a running CLI session, /mcp login ryze starts the same sign-in.
Check the server and ask your first question
Run codex mcp list, or type /mcp inside the Codex TUI, to see the ryze server. If the connector was added before Search Console was connected, remove and re-add it, then start a new session. Then ask: List the Search Console properties this login can access.
codex mcp add ryze --url https://connector.get-ryze.ai/mcpcodex mcp login ryzeFrom a terminal this is the shortest route. codex mcp add writes the ryze entry into ~/.codex/config.toml, and codex mcp login opens the Ryze AI sign-in in your browser. Check the result with codex mcp list, or with /mcp inside the codex TUI. Your Google sign-in stays with Ryze AI; Codex holds only its own Ryze AI sign-in.
The Ryze AI help article for Google Search Console covers the Google side of the connection, and the Ryze AI agent API help page covers API keys.
Sources: OpenAI Codex MCP docs, Codex CLI command reference, Ryze AI Google Search Console guide. Checked November 14, 2026.
ChatGPT desktop app and IDE extension
The ChatGPT desktop app and the IDE extension read the same MCP configuration as the CLI, so a server added in one place appears in the other two. Both use a short form in place of commands, followed by a restart.
ChatGPT desktop app (Codex)
- Open Settings, then select MCP servers.
- Select Add server, enter the name ryze, choose Streamable HTTP and enter https://connector.get-ryze.ai/mcp.
- Save, then select Restart.
- Select Authenticate next to ryze and complete the Ryze AI sign-in. Type /mcp in the composer to view connected servers.
Codex IDE extension
- Open the gear menu, then select MCP servers.
- Select Add server, enter the name ryze, choose Streamable HTTP and enter https://connector.get-ryze.ai/mcp.
- Save, then select Restart extension.
- Select Authenticate and complete the Ryze AI sign-in.
config.toml
To keep the server in a file, edit ~/.codex/config.toml, or a project .codex/config.toml in a trusted project. OAuth is the default for an HTTP server; run codex mcp login ryze to sign in. A Search Analytics query can return up to 25,000 rows, so the example raises the per-call timeout and sets an output budget for that tool.
[mcp_servers.ryze]
url = "https://connector.get-ryze.ai/mcp"
# Optional: raise the defaults (10 and 60 seconds)
startup_timeout_sec = 20
tool_timeout_sec = 120
[mcp_servers.ryze.tools.google_search_console__runRawSearchAnalytics]
output_token_limit = 20000For a Ryze AI API key instead of OAuth, add bearer_token_env_var = "RYZE_API_KEY" to the same table and set that environment variable to your rk_live_ key. Adding --bearer-token-env-var RYZE_API_KEY to codex mcp add writes the same setting from the command line. Do not paste the key into the file.
Codex Cloud tasks are left out on purpose. The one cloud remark on OpenAI's MCP page is that local servers and transports may be missing there, and the Codex Cloud page says nothing about MCP, so this guide makes no claim that the connector works in a cloud task. The steps inside Codex were also not run end to end for this guide.
What OpenAI documents about MCP in Codex
| Topic | What OpenAI's documentation says |
|---|---|
| Where servers are added | codex mcp add in a shell, Settings > MCP servers in the desktop app, the gear menu > MCP servers in the IDE extension, or a [mcp_servers.<name>] table in config.toml |
| Shared by | Codex CLI, the ChatGPT desktop app and the Codex IDE extension. OpenAI calls them the local Codex clients; one setup serves all three |
| Config files | ~/.codex/config.toml for you. A project .codex/config.toml loads only after you trust the project |
| Transports | STDIO, a local process started by a command, and Streamable HTTP, a server at an address. The MCP page names no third one |
| Sign-in to a remote server | OAuth by default, through Client ID Metadata Documents or dynamic client registration. A bearer token read from an environment variable and custom headers are the other options |
| Tool approval | default_tools_approval_mode per server: auto, prompt, writes or approve. tools.<tool>.approval_mode overrides one tool. enabled_tools and disabled_tools work as allow and deny lists |
| Timeouts and output | 10 seconds to start a server and 60 seconds per tool call by default, both adjustable per server. tools.<tool>.output_token_limit sets a per-tool output budget |
| Admin control | An approved mcp_servers list in requirements.toml, matched on the server name and, for a remote server, its URL. An empty list turns off every MCP server |
| Plan | The MCP page names no plan for adding a server. The CLI and the IDE extension come with Plus and higher or an API key; Free and Go have the desktop app only, subject to rollout |
Sources: OpenAI Codex MCP docs, Codex CLI command reference, Codex pricing, Codex managed configuration. Checked November 14, 2026.
Claude, 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
Open Customize, then Connectors, click Add, choose Add custom connector and enter https://connector.get-ryze.ai/mcp. Click Connect, sign in on the Ryze AI page, choose the workspaces and click Allow connection. Anthropic lists custom connectors on Free, Pro, Max, Ultra, Team and Enterprise, with one custom connector on Free.
ChatGPT
OpenAI says full custom MCP support is for ChatGPT Business and Enterprise/Edu on the web, and Pro can connect custom MCP servers with read and fetch permissions only. On the web, open Plugins, select the plus button, then Add custom MCP server, enter the URL and select Create as a plugin. ChatGPT on the web does not read your local Codex configuration.
Cursor
Add the server to .cursor/mcp.json with the same URL, then sign in on the Ryze AI page when Cursor asks.
{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }Source for the ChatGPT steps: OpenAI's page on connecting a server to ChatGPT. Checked November 14, 2026.
Google access and scopes
Three things decide what Codex can reach in Google Search Console.
- Which Google login
- Ryze AI holds the Google sign-in you approved, with the Search Console scope webmasters. The login needs access to a verified Search Console property. You do not create a Google Cloud project to use the connector.
- Which property
- listSites returns the properties the login can access, with permission levels, and its definition says no site is selected for you, so the other tools take a siteUrl you name. A Domain property is written sc-domain:example.com and a URL-prefix property needs its trailing slash. In the Ryze AI app you also confirm a Site for the workspace after connecting.
- More than one login
- Several Google logins can be connected to one workspace with Add one more account, each with its own Site. One is the primary (set with the star) and the agent uses it by default; the tools take an optional connection_id for another login. The help center advises a separate workspace for each client, and one Claude or ChatGPT connection can cover up to 20 workspaces.
The scopes and roles behind each request
Ryze AI reaches Search Console with the Google login you approved, so the scope and the permission level on that login bound what Codex can do. Google lists sitemaps.submit and sitemaps.delete with the read and write scope only, which is why the connection asks for it.
| Scope or permission | What it covers, per Google | In the Ryze AI connection |
|---|---|---|
| webmasters | Read and write access to Search Console. Required by sitemaps.submit and sitemaps.delete; the read methods accept it too | Requested. It covers reading data and submitting or removing sitemaps |
| webmasters.readonly | Read-only access. Accepted by searchanalytics.query, urlInspection.index.inspect, sites.list and sitemaps.list | Not the scope Ryze AI requests |
| Owner | Full control over properties in Search Console. A verified owner proved ownership with a token; a delegated owner was granted ownership by a verified owner | The highest level; nothing about owners is needed beyond the property access |
| Full user | View rights to all data and some actions. Google's table lists Submit sitemap and URL Inspection for full users | Can use the read tools; whether the sitemap tools succeed through the API was not tested |
| Restricted user | Simple view rights on most data. Performance data is viewable; Submit sitemap is blank in Google's table and URL Inspection is listed as Fetch only | Whether this login can run submitSitemap through the API was not tested |
| Associate | A person or account that can take certain actions on behalf of the site, without opening Search Console data directly | Not a login that reads data through the connection |
Not part of the connection: a tool to request indexing, remove URLs from Google or verify a property, index coverage for every URL of a site in one call (URL Inspection checks one URL at a time), and a Search Console API key flow, since Google says its API accepts OAuth 2.0 only.
Sources: Search Console API authorization, sitemaps.submit reference, sitemaps.delete reference, Search Console permissions help, property types help and the Ryze AI Google Search Console guide. Checked November 14, 2026.
Removing access
To remove access, disconnect Google Search Console under Integrations in Ryze AI. On the Codex side, codex mcp logout ryze deletes the stored sign-in and codex mcp remove ryze deletes the entry. To pause the server and keep its settings, set enabled = false in the [mcp_servers.ryze] table.
What Codex can do in Google Search Console
The Ryze AI connector exposes 7 Google Search Console tools: 5 read, 1 write and 1 delete. Codex calls them by these names through the ryze server.
| 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. |
Every tool takes a workspace and an optional connection_id for a specific connected Google login. All but listSites also need a siteUrl. Google marks the indexed count inside a sitemap's contents as deprecated, so rely on submitted counts, errors and warnings. The tools need an active Ryze AI plan or free trial; without one, the connector can only list workspaces and connect platforms.
Approvals in Codex
submitSitemap and deleteSitemap change Search Console, and the other 5 tools only read. In config.toml, default_tools_approval_mode can be auto, prompt, writes or approve; writes asks for tools not marked read-only, which fits this server. Per-tool overrides use tools.<tool>.approval_mode, and disabled_tools turns the two changing tools off for a read-only setup. The same ryze entry also carries the tools of other platforms connected in your workspace, so an enabled_tools list keeps Codex to the Search Console names if that is all it should use. The Ryze AI chat itself starts on Skip all approvals; pick Approve write & delete or Manual approve in its Tool approvals picker if you use it too. Scheduled tasks in Ryze AI run without an approval step.
[mcp_servers.ryze]
url = "https://connector.get-ryze.ai/mcp"
default_tools_approval_mode = "writes"
# Read-only setup: turn the two tools that change Search Console off
disabled_tools = [
"google_search_console__submitSitemap",
"google_search_console__deleteSitemap",
]Search Console and Codex limits in numbers
| Limit | Figures |
|---|---|
| Search Analytics request rate | Per site 1,200 queries per minute; per user 1,200 per minute; per Google Cloud project 30,000,000 per day and 40,000 per minute |
| Search Analytics load | Short-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 are the most expensive, and load grows with the date range. Google says to wait 15 minutes after exceeding quota |
| Rows per request | 1 to 25,000, default 1,000. The connector's tool says 25,000 at most, and a request for 25,001 was refused with HTTP 400 in the November 14 test |
| Paging | Repeat the query with startRow raised 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 method exposes at most 50K rows of data per day per search type, sorted by clicks |
| URL Inspection | One URL per call. Per site 2,000 per day and 600 per minute; per project 10,000,000 per day and 15,000 per minute. Only the version in Google's index is available, not a live test |
| Sites and sitemaps | Per user 20 per second and 200 per minute; per project 100,000,000 per day |
| Data delay | Data is typically available after 2 to 3 days. dataState final returns finalized data and all includes fresh data |
| History kept | Search Console keeps data for the last 16 months |
| Time zone | startDate and endDate are YYYY-MM-DD in Pacific time |
| Filters | Operators contains, equals, notContains, notEquals, includingRegex and excludingRegex (RE2 syntax) on country, device, page, query and searchAppearance. Filter groups combine with and only |
| Codex waiting time and output | 10 seconds to start a server, 60 seconds per tool call. output_token_limit budgets one tool's output, before a 20% serialization allowance |
Google's quota error is the same for every quota event, so the message does not say which bucket ran out. Ask for narrow date ranges and one dimension at a time when you run many queries, and ask for page and query together only when you need both.
Sources: Search Console API usage limits, searchanalytics.query reference, getting all your data, URL Inspection reference, sitemaps reference, 16 months of data, OpenAI Codex MCP docs. Checked November 14, 2026.
First 3 prompts to run
Each answer comes from your own property, so this page describes what comes back instead of showing sample numbers.
1. Find the property
List every Search Console property this Google login can access, with the permission level on each.
Tools used: google_search_console__listSites
What comes back: The properties the login can access with permission levels. Use the siteUrl it returns in later prompts. It ran in the November 14 test.
2. Top queries for a date range
For <siteUrl>, give the top 100 queries by clicks over the last 90 days with impressions, CTR and average position. Name the date range.
Tools used: google_search_console__runRawSearchAnalytics
What comes back: One row per query with clicks, impressions, ctr and position, ordered by clicks, highest first. A query grouped by query ran in the test; fewer rows than the limit means no second page is needed.
3. Pages that rank just outside the click positions
For <siteUrl>, group the last 28 days by page and query and show the pages whose average position is between 8 and 20, with their impressions.
Tools used: google_search_console__runRawSearchAnalytics
What comes back: Rows keyed by page and query. Grouping by page and query is the most expensive Search Analytics shape, so keep the range short. This grouping was not run in the test.
Only two tools change anything. Asking Codex to request indexing for a URL or to verify a property will fail, because the connector has no tool for either.
10 jobs to hand to Codex
Ten jobs you can give Codex, with the Ryze AI tool behind each one. The last column says whether the default connection covers it. Only the first three ran in the test; the rest follow the tool definitions and the facts file.
| Job | What to ask Codex | Tool | Default connection |
|---|---|---|---|
| Property inventory | List every property this login can reach, with the permission level on each. | google_search_console__listSites | Covered. Ran in the test |
| Top queries | Top queries by clicks and impressions for a date range, with CTR and average position. | google_search_console__runRawSearchAnalytics | Covered. Ran in the test |
| Query filters | Only the queries that contain a word or match a pattern, such as brand terms or question words. | google_search_console__runRawSearchAnalytics | Covered. Equals and includingRegex filters ran in the test |
| Near-miss pages | Pages that rank just outside the click-earning positions, with the queries they rank for. | google_search_console__runRawSearchAnalytics | Covered; grouping by page was not run |
| Country and device split | Clicks and impressions by country, device or search appearance. | google_search_console__runRawSearchAnalytics | Covered; not run |
| One page over time | A day-by-day trend for one page, to see whether a new article earns impressions and clicks. | google_search_console__runRawSearchAnalytics | Covered; grouping by date was not run |
| Other result types | Performance in image, video, news or Discover results instead of web results. | google_search_console__runRawSearchAnalytics | Covered; not run |
| Index status of a URL | Coverage, verdict, last crawl, canonical, mobile usability and rich results for one URL. | google_search_console__inspectUrl | Covered; one URL per call and not run |
| Sitemap health | Every sitemap with last submitted and downloaded dates, errors and warnings, plus a property summary. | google_search_console__listSitemaps, google_search_console__getIndexationSummary | Covered; not run |
| Submit or remove a sitemap | Submit or resubmit a sitemap, or remove a stale one from Search Console. | google_search_console__submitSitemap, google_search_console__deleteSitemap | Covered by the read and write scope; not run because it changes Search Console. Removing a sitemap leaves the file on the site |
5 ways to connect Codex to Google Search Console
Five routes lead from Codex to Search Console data. Composio, Coupler.io and the open source mcp-gsc project name Codex on their own pages. Google's BigQuery route does not name it, so that reading rests on two documents and no tested setup. The Ryze AI connector is the main way here: one codex mcp add command covers all three Codex surfaces, with no Google Cloud project. Google's own pages list no Search Console MCP server, and the pages for the other routes were read on November 14, 2026.
| Way | Where it runs | Setup in Codex | What it reaches in Search Console | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, with one address for every user | codex mcp add ryze --url https://connector.get-ryze.ai/mcp and codex mcp login ryze, or Add server in the desktop app or IDE extension. One entry serves all three | 7 tools: Search Analytics, URL Inspection of one URL, sitemap lists and summary, and submitting or removing a sitemap. Sign-in is Google OAuth with the webmasters scope | SEO Starter is $129 per month with a 3-day free trial; Paid Ads is $89 per month with a 7-day free trial |
| mcp-gsc (AminForou, open source) | On your computer, started by Codex as a local command (uvx mcp-search-console). Version 0.4.2 on November 6, 2026, with 2,202 GitHub stars on November 14 | Add the config snippet from its README to ~/.codex/config.toml. You create your own Google OAuth client of type Desktop app, or a service account key, in Google Cloud | Its README lists 20 tools and names 15, among them list_properties, get_search_analytics, compare_search_periods, inspect_url_enhanced, batch_url_inspection of up to 10 URLs and manage_sitemaps. add_site, delete_site and delete_sitemap are disabled by default | Free, MIT licence |
| Composio | Hosted by Composio | Add https://connect.composio.dev/mcp as a Streamable HTTP server and sign in to Composio. Composio's Search Console page lists Codex among its assistants, and Composio says it manages OAuth and token refresh | 14 tools on its toolkit page, read and write, including Search Analytics Query, Inspect URL, Submit Sitemap, Delete Site and Verify Site Ownership | Free is $0 with 10,000 tool calls a month for up to 3 members. Standard is $18 per seat per month. Its toolkit page FAQ states a different free figure, so check the page you buy from |
| Coupler.io | Hosted by Coupler.io, over Search Console data it syncs on a schedule | Set up a Search Console data flow, add Custom MCP as its destination, generate a token and paste the server URL and token into Codex. Its page names Codex among the clients that accept a remote MCP URL | Read-only access to the synced data. No sitemap management, URL submission or Indexing API calls. Refresh can be every 15 minutes at the shortest | Free is $0 with 1 data source and manual refresh. Starter is $32 per month, or $24 billed annually |
| Google bulk export and the BigQuery MCP server | Google Cloud. Search Console exports performance data daily to BigQuery, and Google's BigQuery remote MCP server at https://bigquery.googleapis.com/mcp reads it | Set up the export in Search Console for one property, then add the BigQuery server. Google says its remote servers do not support Dynamic Client Registration or Client ID Metadata Documents, and its client guidance does not name Codex, so whether Codex completes the sign-in is not stated | Performance data 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 | Google Cloud storage and query costs apply, with a free usage level |
Options that do not fit Codex
- Google's Search Console API with your own code. Google documents it as an HTTP REST service with OAuth 2.0 and calls it free of charge within usage limits. Its pages describe no MCP endpoint, so using it means writing your own code, and there is no server to add to Codex.
- Windsor.ai. Its Search Console page says the hosted connector is read-only with no URL inspection, and names Claude, ChatGPT, Gemini and Copilot. It names Codex only for its open source server, so no Codex setup is described here.
- Zapier MCP. Zapier lists Codex among its popular MCP clients, but on November 14, 2026 its Google Search Console pages returned HTTP 404, so no Search Console actions were confirmed.
- ahonn/mcp-server-gsc. An open source server with one tool, search_analytics, and a service account for sign-in. Its README shows a Claude Desktop configuration and does not mention Codex.
- Developer Knowledge MCP server. Google hosts it for searching its developer documentation, and it names Codex as a client. It returns documentation pages and has no access to your Search Console data.
- AI-powered configuration in Search Console. It sits in the Performance report of the web interface, is experimental, and Google limits each user to 20 requests a day. It is not a connector for an outside assistant.
Which one to pick
Ryze AI is the best way to connect Codex to Google Search Console when you want queries, URL inspection and sitemap actions in one hosted server with no Google Cloud project, with one caveat: it needs a Ryze AI plan or trial, and your Search Console data passes through Ryze AI. Choose mcp-gsc when you want the server on your own machine and accept creating a Google OAuth client and installing Python tooling, or its larger tool list. Composio fits a team that already routes other apps through it. Coupler.io suits reporting from a synced copy that refreshes on a schedule. The BigQuery route fits teams that already keep Search Console data in BigQuery, and it was not tested with Codex.
Sources: Google Cloud remote MCP servers, Google MCP repository, Search Console API home, mcp-gsc README, mcp-search-console on PyPI, Composio Search Console toolkit, Composio pricing, Coupler.io Search Console MCP, Coupler.io pricing, bulk data export help, BigQuery MCP server docs, OpenAI Codex MCP docs, Ryze AI Google Search Console integration. Checked November 14, 2026.
Sources for the options that do not fit: Search Console API pricing, Windsor.ai, Zapier MCP quickstart, ahonn/mcp-server-gsc, Developer Knowledge MCP server, AI-powered configuration. Checked November 14, 2026.
Codex, Google 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 for each Search Console property. |
| February 21, 2023 | Google announced bulk data export from Search Console 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 does not list it, and it was not tested. |
| October 3, 2025 | Codex CLI 0.44.0 added support for Streamable HTTP MCP servers, the transport the Ryze AI connector uses. |
| October 6, 2025 | Codex CLI 0.45.0 brought experimental OAuth sign-in for MCP servers. |
| December 10, 2025 | The BigQuery remote MCP server entered Preview. Google's Cloud MCP release notes, newest entry September 14, 2026, have no Search Console entry. |
| April 20, 2026 | Google's BigQuery release notes mark the BigQuery MCP server as generally available. |
| June 3, 2026 | Google introduced Search generative AI performance reports in Search Console. Its post does not say whether the data reaches the API or bulk export. |
| July 9, 2026 | Codex became part of the ChatGPT desktop app on macOS and Windows. |
| October 7, 2026 | Codex CLI 0.161.0 added /mcp login <name> for signing in from a running session. |
| November 6, 2026 | mcp-search-console 0.4.2 reached PyPI, the newest version on November 14. It requests the read-only scope by default. |
| November 13, 2026 | Codex CLI 0.169.0 came out. It keeps project configuration and MCP servers off in untrusted directories for codex exec. |
| November 14, 2026 | Google's supported-products list for remote MCP servers (stamped November 12), its MCP repository and the Search Console API pages showed no Search Console MCP server, connector or plugin. |
Sources: Codex changelog, Codex CLI 0.44.0, 0.45.0 release notes, URL Inspection API launch, bulk data export announcement, hourly data announcement, generative AI performance reports, Google Cloud MCP release notes, BigQuery release notes, mcp-search-console on PyPI. Checked November 14, 2026.
How this guide was tested
The Ryze AI connector's Google Search Console tools were tested on November 14, 2026, from Claude Code, against a Domain property in a Ryze AI test workspace. The run made 6 Search Console calls, all read-only, and loaded the definitions of all 7 tools. No account name, domain or metric value is shown here.
| What was run | What came back |
|---|---|
| Loaded the definitions of all 7 tools by exact name | Every name in the tools table resolved, with 5 read, 1 write and 1 delete tool as listed. |
| listSites | Worked. |
| runRawSearchAnalytics, 7 days, dimension query, rowLimit 25001 | Refused by Google with HTTP 400. The message is in the errors section below. |
| runRawSearchAnalytics with the dimension keyword, which does not exist | Refused with HTTP 400 and status INVALID_ARGUMENT. No data returned. |
| runRawSearchAnalytics with an end date before the start date | Refused with HTTP 400. No data returned. |
| runRawSearchAnalytics, 7 days, dimension query, an equals filter on a random 20-letter string | Worked and returned no rows. The whole response was responseAggregationType byProperty, with no rows key. |
| runRawSearchAnalytics, 90 days, dimension query, rowLimit 120, dataState all, an includingRegex filter on query | Worked. Each row had keys, clicks, impressions, ctr and position, ordered by clicks, highest first. Fewer rows than the limit came back, so no second page was needed. |
Not run: inspectUrl, listSitemaps and getIndexationSummary, and grouping by page, country, device, search appearance or date, and the image, video, news and Discover types. submitSitemap and deleteSitemap were not run, because they change Search Console. No call tested a restricted-user login or hit a quota. Nothing was run inside Codex: no codex mcp add, no codex mcp login and no tool call from the CLI, the ChatGPT desktop app or the IDE extension. Those steps follow OpenAI's Codex documentation as read on November 14, 2026, and the routes in the comparison are described from their pages.
Codex and Google Search Console errors and fixes
- '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.
- HTTP 400, reason invalidParameter. rowLimit was above 25,000. Ask for 25,000 rows or fewer and page with startRow. Google's current reference is https://developers.google.com/webmaster-tools/v1/searchanalytics/query.
- Invalid value at 'dimension[0]' (type.googleapis.com/google.searchconsole.v1.searchanalytics.ApiDimension), "keyword"
- HTTP 400, status INVALID_ARGUMENT. The dimension name does not exist; search terms are the dimension query. Use query, page, country, device, searchAppearance or date.
- Invalid date range defined by startDate and endDate. End date cannot precede the start date.
- HTTP 400. The end date was earlier than the start date. Swap them; both are YYYY-MM-DD.
- quota exceeded
- Documented by Google and not triggered in the test. Google says the error is the same for every quota event and to wait 15 minutes. Ask for a shorter date range and fewer dimensions, and do not group by page and query unless needed.
- request timed out
- Documented in the connector's tool definition and not triggered in the test. It means Search Console did not answer that request in time. Resend it once on its own, never in parallel, then narrow it with a shorter date range, one dimension and no regex filter.
- An empty result with no rows key
- Not an error. The test query with a filter nothing matched returned only responseAggregationType byProperty. Check the filter, the property and the date range, and remember data arrives after 2 to 3 days.
- Search Console tools do not appear in Codex
- If the connector was added before Search Console was connected in Ryze AI, remove the ryze server, add it again, sign in and start a new session.
- A call fails on the siteUrl
- listSites says no site is selected for you. Pass the exact siteUrl it returns: sc-domain:example.com for a Domain property, or the full URL with a trailing slash for a URL-prefix property.
- codex mcp login opens no browser
- Run codex mcp login ryze --no-browser, open the printed URL on another device and paste the full redirect URL back into the terminal.
- The server times out on start or on a call
- Codex waits 10 seconds to start a server and 60 seconds per tool call by default. Raise startup_timeout_sec or tool_timeout_sec in the [mcp_servers.ryze] table.
- Output is cut off
- Set tools.google_search_console__runRawSearchAnalytics.output_token_limit in config.toml, or ask for fewer rows and one dimension.
- The ryze table in a project config.toml is ignored
- Codex reads a project's .codex/config.toml only in a trusted project, and since CLI 0.169.0 codex exec keeps project MCP servers off in an untrusted directory. Trust the project, or move the table to ~/.codex/config.toml.
- A tool replies that a subscription is required
- The Search Console tools need an active Ryze AI plan or free trial. Start the trial, then retry.
- No CLI or IDE extension on a Free or Go plan
- OpenAI lists Codex on those plans in the desktop app only, subject to rollout. Use the desktop app steps.
Sources: Search Console API usage limits, searchanalytics.query reference, OpenAI Codex MCP docs, Codex changelog. Checked November 14, 2026.
Terms on this page
- MCP
- The Model Context Protocol, which Codex uses to call tools on outside servers such as the Ryze AI connector.
- Streamable HTTP
- The transport Codex uses for a server it reaches at an address. Its other transport, STDIO, starts a local process.
- Domain property
- A Search Console property that aggregates data for all subdomains, protocols and subpaths. In the API its siteUrl is written sc-domain:example.com, and Google requires DNS record verification for it.
- URL-prefix property
- A property that includes only URLs with the specified prefix, including the protocol. In the API it 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 Performance report to protect user privacy. Bulk export to BigQuery leaves them out too.
- startRow
- The Search Analytics parameter that skips rows. Raise it by 25,000 per request to page through a large result.
Sources: OpenAI Codex MCP docs, property types help, average position help, anonymized queries in the Performance report, searchanalytics.query reference. Checked November 14, 2026.
Frequently asked questions
How do I connect Codex to Google Search Console?
Connect Google Search Console on its card in Ryze AI and save a Site. Then run codex mcp add ryze --url https://connector.get-ryze.ai/mcp, run codex mcp login ryze, sign in on the Ryze AI page and click Allow connection.
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, its MCP repository and the Search Console API documentation have no Search Console entry. Google does publish an open source MCP server for Google Analytics, and a BigQuery server that can read Search Console bulk export data.
What is the Google Search Console MCP URL for Codex?
With Ryze AI it is https://connector.get-ryze.ai/mcp. Google lists no Search Console address. The open source mcp-gsc server runs as a local command and has no address.
Is there a Google Search Console connector for Codex?
Yes, from outside Google. The Ryze AI connector, Composio and Coupler.io can all be added to Codex as remote or local MCP servers, and the open source mcp-gsc project shows a Codex config.toml snippet in its README. The Ryze AI steps were not run inside Codex for this guide.
Can Codex change my Search Console settings?
In two ways. submitSitemap submits or resubmits a sitemap and deleteSitemap removes one from Search Console, leaving the file on your site. The other 5 tools read. There is no tool to request indexing, remove URLs from Google or verify a property.
Which Codex plan do I need?
OpenAI lists Codex in ChatGPT Free, Go, Plus, Pro, Business, Edu and Enterprise. Free and Go get Codex in the desktop app only, subject to rollout. Plus and higher add the CLI and the IDE extension. OpenAI's MCP page names no plan condition for adding a server.
Which Google permission does the login need?
Access to a verified Search Console property. Ryze AI asks Google for the webmasters scope, which covers reading data and submitting or removing sitemaps. Keep every requested permission checked on the Google screen. Whether a restricted user's login can submit a sitemap through the API was not tested.
Does Codex sign in to Google directly?
Not with the Ryze AI connector. Codex signs in to Ryze AI through OAuth or a Ryze AI API key, and Ryze AI holds the Google sign-in. With mcp-gsc, your own Google credentials are read by the local server.
Can Codex show which pages rank just outside the top results?
You can ask for it. runRawSearchAnalytics groups clicks, impressions, CTR and position by page and query, and you can filter the result to an average position range. Grouping by page and query is the most expensive shape, so keep the date range short. That grouping was not run in the November 14 test.
How many rows can one Search Console query return?
Up to 25,000 rows per request, and Google refused 25,001 with HTTP 400 in the November 14 test. Page with startRow in steps of 25,000. Google also says the method exposes at most 50K rows per day per search type, sorted by clicks.
Why is Search Console data from the last two days missing?
Google says data is typically available after 2 to 3 days. dataState final returns finalized data only, and dataState all includes fresh data. Search Console keeps the last 16 months.
Can I connect more than one Google login or site?
Yes. Several Google logins can be connected to one workspace, each with its own Site, with one primary. The tools take an optional connection_id, and you name the siteUrl in the prompt. Keep a separate workspace for each client.
Can I run the Ryze AI connector and another server in Codex at the same time?
Yes. Each server is its own [mcp_servers.<name>] table in config.toml, for example ryze and mcp-gsc, and the CLI, the desktop app and the IDE extension read both. OpenAI advises turning off servers you do not need, because each adds context to your messages.
Does this work in Codex cloud tasks?
This page does not claim it does. OpenAI's MCP page covers the CLI, the desktop app and the IDE extension, its Codex Cloud page does not mention MCP, and the connector was not tested in Codex.
How much does it cost to connect Codex to Google Search Console?
Adding 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. Google says the Search Console API is free within usage limits, and Codex is billed under your OpenAI plan or API pricing.