AI assistants

Connecting Codex

Search Console findings next to the code that causes them, in the Codex CLI, the IDE extension and the Codex app.

Codex reading a CTR analysis from GSC Wizard and tracing the weak titles to the template in the repository that builds them — Codex reads the Search Console finding and the code side by side (example data).

CLI, IDE and app Sign in or API key

Most of what Search Console flags is fixed in code: a title template, a canonical tag, a sitemap generator, a redirect rule. Codex can read the finding and the repository side by side. It reaches your data through the GSC Wizard MCP server at https://mcp.gscwizard.com/mcp, and the Codex CLI, the IDE extension and the Codex app all read the same ~/.codex/config.toml, so you add the server once and it works in all three.

Before you start: you need a GSC Wizard subscription or trial, and your properties connected in the app at tool.gscwizard.com, not in Codex. The setup overview explains both.

Add the server

From any terminal:

codex mcp add gsc-wizard --url https://mcp.gscwizard.com/mcp

This writes an [mcp_servers.gsc-wizard] table into ~/.codex/config.toml.

Sign in

codex mcp login gsc-wizard

Your browser opens GSC Wizard’s sign-in screen. Check the account it says you are signed in as, and untick the box that allows changes if Codex should only read. Then start codex and type /mcp to see the tools.

Check that it works

Ask something you can compare with the app, so you know Codex reads the right account:

List my GSC Wizard properties, then give me clicks, impressions and average position for example.com over the last 28 days, with the dates.

The numbers should match the property dashboard for the same dates, give or take the last settled day, which the answer names.

Use a key, and keep Codex to the tools it needs

Every tool definition costs context on every turn, and the server has more than 130. For a task, list only the tools it needs. The block below is a read-only SEO set, with the key in an environment variable for runs without a browser, such as codex exec and CI.

[mcp_servers.gsc-wizard]
url = "https://mcp.gscwizard.com/mcp"
bearer_token_env_var = "GSCW_API_KEY"
enabled_tools = [
  "list_sites",
  "get_site_summary",
  "query_top_queries",
  "query_top_pages",
  "get_ranking_changes",
  "find_decaying_content",
  "analyze_cannibalization",
  "score_opportunities",
  "inspect_url",
  "audit_onpage_seo"
]
tool_timeout_sec = 120

Codex sends the variable’s value as the bearer token, so the key never sits in the file. Create it on the MCP API keys page, read-only. Drop the bearer_token_env_var line to keep using the browser sign-in. Analyses over a long date range on a large site take longer than a plain lookup, which is what the timeout is for.

Codex reads AGENTS.md at the start of a session. A few lines there save repeating the site in every prompt:

## Search Console
- Property: sc-domain:example.com (use the gsc-wizard MCP tools).
- Before changing titles, canonicals or redirects, check the page's
  queries and clicks with get_page_performance.
- Never call a tool that submits or deletes anything without asking first.

The ready-made SEO skills install into Codex too: npx skills add jbobbink/seo-gsc-wizard.

What to ask Codex

In your own words. Name the property when you have more than one; you never need the tool names.

Find the 20 pages with the lowest CTR for their position, then find the template in this repo that builds their titles and propose better ones.
Inspect the ten newest URLs in our sitemap. For any that are not indexed, check the canonical and robots handling in the code that renders them.
Which queries do two of our pages compete for? Find both pages in the repo and suggest which one should win and how to consolidate.
We moved /blog/ to /articles/ last month. Compare the old and new URLs in Search Console and check the redirect rules for any that are missing.

Selling online? The same connection also answers questions about Merchant Center: free listings, products Google holds back, prices against the market and feed health. Merchant Center in Codex has the prompts and the shopping tools.

Troubleshooting

/mcp does not list gsc-wizard

Run codex mcp list to confirm the entry exists, and check that it is a url entry rather than a command entry. Codex reads the config at startup, so restart it after editing the file.

Every call returns 401

With a key, the variable named in bearer_token_env_var has to be exported in the shell that started Codex and hold the full gscw_live_ key. With the browser sign-in, run codex mcp login gsc-wizard again.

Codex answers for the wrong GSC Wizard account

A GSC Wizard connection added through ChatGPT’s apps, rather than in config.toml, shares ChatGPT’s sign-in. Remove that connection and add it again while you are signed in at tool.gscwizard.com as the right account.

Calls time out

Raise tool_timeout_sec, and narrow the question: one section of the site or a shorter date range answers faster than everything over sixteen months.

Part of Connecting AI assistants. Related: GSC MCP for Codex, Claude, ChatGPT, Gemini, Cursor & VS Code, Grok, Microsoft Copilot.

ChatGPT

Gemini