A Google Search Console MCP server you don’t have to host.
Ask Claude, ChatGPT or Cursor which queries and pages are slipping, why a page isn’t indexed, and what to change, from your real Google Search Console (GSC) data. Connect Google once; no Google Cloud project, service account or credentials file. Search Console reads are free.
query_search_console · inspect_url · 79 tools on the server · no card
Three steps, no Google Cloud.
- Add your site to AuditAE (free, $5 credit, no card).
- Connect Google on the Integrations page, then pick the site’s Search Console property in its Settings → Connections. One sign-in covers every site in the workspace.
- Add the server at
https://auditae.app/api/mcpto your client, below: Claude, ChatGPT, Claude Code, Codex, and VS Code sign in with no key; Cursor and Windsurf use an API key. Then ask it about your search traffic.
Claude, ChatGPT, Claude Code, Codex and Cursor.
Claude
Connects with: Sign-in (OAuth)Opens Claude's Add custom connector dialog with AuditAE filled in. Confirm, then sign in to AuditAE or create a free account in the same step. The connector works in Claude on the web, in Claude Desktop and in Cowork.
https://auditae.app/api/mcp- Claude Free allows one custom connector.
- On Team and Enterprise plans only Owners add custom connectors, from Organization settings → Connectors. Members then connect it from Customize → Connectors.
- Sign-in connects your personal workspace. Team workspaces use an API key.
Then ask “What's my AuditAE balance and what can you do?”
ChatGPT
Connects with: Sign-in (OAuth)ChatGPT adds custom MCP servers as plugins. Four steps; the last one signs you in.
- Open chatgpt.com/plugins, select +, then Add custom MCP server. If you don't see that option, turn on developer mode in ChatGPT's settings (on Business, Enterprise and Edu workspaces an admin does this).
- Name it AuditAE, paste https://auditae.app/api/mcp as the server URL and choose OAuth for authentication.
- Select I understand and want to continue, then Create as a plugin.
- Install the plugin and sign in to AuditAE when ChatGPT asks.
https://auditae.app/api/mcp- Needs a plan that allows custom MCP servers. Check your plan and workspace settings.
- When AuditAE adds tools, open AuditAE at chatgpt.com/plugins and select Refresh.
- Sign-in connects your personal workspace. Team workspaces use an API key.
Then ask “What's my AuditAE balance and what can you do?”
Claude Code
Connects with: Sign-in (OAuth)Run this once in your terminal; --scope user adds AuditAE to every project. Then run /mcp in Claude Code, pick auditae and choose Authenticate to sign in.
claude mcp add --transport http --scope user auditae "https://auditae.app/api/mcp"- Sign-in connects your personal workspace. Team workspaces use an API key.
Then ask “What's my AuditAE balance and what can you do?”
Codex
Connects with: Sign-in (OAuth)One command for the Codex CLI. It detects AuditAE's sign-in and opens your browser; if it doesn't, run codex mcp login auditae. The Codex IDE extension and the ChatGPT desktop app read the same ~/.codex/config.toml: you can paste the block instead, then run codex mcp login auditae (or sign in from the app's MCP settings).
codex mcp add auditae --url "https://auditae.app/api/mcp"[mcp_servers.auditae]
url = "https://auditae.app/api/mcp"
tool_timeout_sec = 300- tool_timeout_sec = 300 gives long citation runs room to finish; Codex's default is 60 seconds.
- Sign-in connects your personal workspace. Team workspaces use an API key.
Then ask “What's my AuditAE balance and what can you do?”
VS Code
Connects with: Sign-in (OAuth)Opens VS Code's install prompt for AuditAE, for GitHub Copilot agent mode. Select Install, then sign in when VS Code asks. Or run MCP: Open User Configuration and add the block below.
{
"servers": {
"auditae": {
"type": "http",
"url": "https://auditae.app/api/mcp"
}
}
}- VS Code caps the tools one request can use (128 at last check), counting its built-in tools and your other servers. If it warns, turn off tools you don't need in the tool picker.
- Sign-in connects your personal workspace. Team workspaces use an API key.
Then ask “What's my AuditAE balance and what can you do?”
Cursor
Connects with: API keyCursor connects with an API key for now. Add this to ~/.cursor/mcp.json, your user config, so the key never sits in a project folder, and replace ae_live_… with your key.
{
"mcpServers": {
"auditae": {
"url": "https://auditae.app/api/mcp",
"headers": {
"Authorization": "Bearer ae_live_…"
}
}
}
}- Sign-in and a one-click install for Cursor aren't available yet, so it needs a key.
- If the tools don't show up, reload Cursor after saving the file.
Then ask “What's my AuditAE balance and what can you do?”
Windsurf
Connects with: API keyWindsurf (Devin Desktop) connects with an API key. Add this to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows; older Windsurf builds read ~/.codeium/windsurf/mcp_config.json) and replace ae_live_… with your key.
{
"mcpServers": {
"auditae": {
"serverUrl": "https://auditae.app/api/mcp",
"headers": {
"Authorization": "Bearer ae_live_…"
}
}
}
}- Cascade allows 100 tools across all your MCP servers, and AuditAE's full set uses most of them. Turn off servers you aren't using.
- The config path has moved between versions; check your version's MCP settings if neither file is read.
Then ask “What's my AuditAE balance and what can you do?”
Other clients
Connects with: Sign-in or API keyMost other clients that speak remote MCP over Streamable HTTP, such as Zed, Cline, Continue, Kiro, Goose or JetBrains, connect to the URL. Clients that support OAuth client metadata documents sign in; the rest send an API key in the Authorization header.
https://auditae.app/api/mcpURL: https://auditae.app/api/mcp
Header: Authorization: Bearer ae_live_…{
"mcpServers": {
"auditae": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://auditae.app/api/mcp",
"--header", "Authorization:${AUTH_HEADER}"
],
"env": { "AUTH_HEADER": "Bearer ae_live_…" }
}
}
}- Clients that only launch local (stdio) servers can bridge to the hosted endpoint with mcp-remote, as in the last block.
- Sign-in connects your personal workspace. Team workspaces use an API key.
Then ask “What's my AuditAE balance and what can you do?”
Want every click spelled out? The step-by-step guide to connecting Claude or ChatGPT covers the same steps for Google Analytics, screen by screen; Search Console uses the same connection. Every client’s options are in the MCP docs.
Performance and index status.
Two free tools over Google’s read-only Search Console scope. Your client picks the dimensions, filters and dates; each call reads from Google, and an identical call within 10 minutes comes from a short cache.
Performance
Freequery_search_console
- Clicks, impressions, CTR and average position, from the Search Analytics API.
- Up to 4 dimensions: query, page, country, device, date, searchAppearance.
- Search types: web, image, video, news, discover, googleNews (web by default).
- Up to 10 filters, all applied together: equals, notEquals, contains, notContains, includingRegex, excludingRegex.
- Up to 1,000 rows per call, with start_row to page. Any date range Search Console keeps (16 months); by default the last 30 days up to 2 days ago.
URL Inspection
Freeinspect_url
- Verdict, coverage and indexing state, robots.txt state and the last fetch result.
- Last crawl time, the canonical Google picked against the one the page declares, sitemaps and referring URLs.
- Rich results Google detected, with their errors and warnings, plus the inspection link and a next step.
- Google's last crawl, not the live page. About 2,000 inspections a day and 600 a minute per property; a repeat within 10 minutes comes from cache.
Queries worth tracking
Freequery_search_console → track_suggestions
- A query-dimension call also returns up to 10 non-brand queries ranking 4–20 with 5+ impressions that the site doesn't track yet.
- Track them with track_keywords (5¢ per keyword per weekly check) to see the Google position every week and whether the AI Overview cites you.
What it doesn’t do: list or submit sitemaps, inspect URLs in batches (one per call; the agent loops), or use the Indexing API, so Request indexing stays in Search Console. Sorting applies to the rows a call returns, so for a true top list, ask for more rows; comparing two periods takes two calls.
Find it, then fix it.
Search Console tells you where you’re slipping. The same connection writes the fix, applies it on WordPress, asks for a recrawl and checks AI answers. Each card is the chain your client runs and what it costs.
“Which pages lost the most clicks over the last 28 days compared with the 28 before?”
query_search_console (page, one call per period) → get_fix_plan on the worst page
Free read + 50¢ for the plan
“Show queries ranking 8–20 with real impressions, and track the best five.”
query_search_console (query; the client filters by position) → track_keywords
Free read + 5¢ per keyword per weekly check
“Pages with lots of impressions but a CTR under 1%: rewrite their titles.”
query_search_console (page) → wp_get_post → wp_set_post_seo → submit_urls
Free read + 5¢ per WordPress write. Not on WordPress? The fix plan's paste-ready steps instead (50¢).
“Is /pricing indexed, which canonical did Google pick, and is its FAQ schema detected?”
inspect_url → validate_schema
Free
“We changed 6 pages today. Ping Bing to recrawl them and check which ones Google has already picked up.”
submit_urls (Bing and IndexNow engines) → inspect_url, then Request indexing at its link for Google
Free
“We rank 4–10 for 'invoice software for freelancers'. Does ChatGPT cite us for it, and who does it cite instead?”
query_search_console → check_brand_citation
Free read + 5–12¢ per engine, plus the fix-it playbook (about 12¢ per answered check that didn't cite the brand and about 45¢ per audit)
A page that ranks but doesn’t get clicked.
Our own property, queried through the same server you’d connect. One page showed up 1,535 times in four weeks at an average position of 11.9, just off page one, and got one click.
Request
query_search_console({
domain: "auditae.app",
dimensions: ["page"],
start_date: "2026-09-14",
end_date: "2026-10-11",
filters: [{ dimension: "page", operator: "contains",
expression: "/chatgpt-brand-monitoring" }],
order_by: "impressions"
})Response (excerpt)
{
"domain": "auditae.app",
"rows": [
{
"keys": { "page": "https://auditae.app/chatgpt-brand-monitoring" },
"clicks": 1,
"impressions": 1535,
"ctr": 0.0007,
"position": 11.9
}
]
}Our read
Position 11.9 with a 0.07% CTR: the page is close to page one and its snippet isn’t earning clicks. Run get_fix_plan on /chatgpt-brand-monitoring (50¢) for a new title and meta and the on-page edits, then inspect_url once Google recrawls it.
Everything else the server does.
Connecting AuditAE for Search Console connects all 79 tools. The Google reads are free; everything else is pay-per-use from one balance, with no subscription. New accounts get $5 of credit. The full tour is on the SEO MCP server page.
Google Analytics 4
2 toolsAny GA4 report by the dimensions and metrics you name, and visits from ChatGPT, Perplexity, Claude, Gemini and Copilot with their landing pages. Same Google connection, free.
Google Analytics MCPFix plans
1 toolget_fix_plan reads your latest audit and the live page, then returns the exact edits: title and meta, the sentence to rewrite, FAQs and schema to add. Steps for WordPress, Next.js, Shopify, Webflow and more. 50¢.
WordPress edits
28 toolsOn a site paired with the free plugin, the agent edits posts, Yoast and Rank Math titles and meta, schema and llms.txt, including Elementor pages. Reads are free, writes 5¢.
WordPress MCP setupTechnical audits and schema
16 toolsA whole-site crawl (1¢ per 10 pages), Core Web Vitals and on-page checks, IndexNow submission, and schema you can generate and validate.
Compared with Screaming FrogRank tracking and SEO data
8 toolsWeekly Google positions with AI Overview presence and citation (5¢ per keyword per weekly check), keyword research, live SERPs (5¢) and keyword metrics (10¢ per call).
AI search citations
13 toolsWhether ChatGPT, Perplexity, Gemini and Google AI Overviews cite you for a prompt, who they cite instead, share of voice and what changed since last time. Checks are 5–12¢ per engine, plus the fix-it playbook.
How citation checks workGSC MCP servers, compared.
The community servers are good if you’re comfortable in Google Cloud, and some do more with Search Console itself, like sitemaps and batch inspection. Hosted connectors skip the setup, mostly on a monthly plan. AuditAE skips both and adds the tools that act on what you find.
| AuditAE (hosted, pay per use) | Self-hosted community servers | Hosted connectors (plans vary) | |
|---|---|---|---|
| Setup | Sign in with Google once in AuditAE and pick the Search Console property | A Google Cloud project with the Search Console API, plus a Desktop OAuth client or a service account (mcp-gsc) | An account with the vendor, then connect Google |
| Hosting | Remote URL, nothing to run | Runs on your machine (Python or Node) | Remote URL. OpenSEO is also open source if you'd rather host it |
| Clients | Claude, ChatGPT, Claude Code, Codex, and VS Code sign in; Cursor and Windsurf use an API key | Local clients that launch the server; web apps need your own hosting | Varies by vendor |
| URL inspection | Yes, free, one URL per call | In some, e.g. mcp-gsc | OpenSEO: up to 10 URLs at once |
| Sitemaps and batch inspection | No. The agent loops inspect_url; sitemaps stay in Search Console | Often yes: mcp-gsc lists sitemap tools and batch URL inspection | Varies by vendor |
| Acting on the data | Fix plans, WordPress edits, IndexNow, AI citation checks and rank tracking: 79 tools on one connection | Search Console data | OpenSEO's Search Console tools are read-only |
| Price | Search Console tools free, no subscription; the rest pay per use from $5 of free credit | Free; you run and maintain it | OpenSEO $10/mo; Windsor.ai has a free plan; Coupler.io needs the Professional plan or higher |
Checked October 13, 2026 on each project’s own page: AminForou/mcp-gsc, OpenSEO, Windsor.ai, Coupler.io. Plans change often, so check before you choose.
Questions worth asking.
Straight answers on the Search Console MCP tools.
Not as of October 2026. Google publishes an official Google Analytics MCP server, but a search on October 13, 2026 found no first-party GSC MCP server. The options are community servers you run yourself, such as mcp-gsc, which need a Google Cloud project and an OAuth client or service account, and hosted connectors such as AuditAE, OpenSEO, Windsor.ai and Coupler.io.
Three steps. Add your site to AuditAE (free, no card). Connect Google on the Integrations page and pick the site's Search Console property in its Settings, under Connections. Then add https://auditae.app/api/mcp to Claude: on the web, in Claude Desktop and in Cowork it's a custom connector you sign in to, and Claude Code adds it with one command. Ask Claude which queries brought clicks last month to check it works.
Yes. Add https://auditae.app/api/mcp in ChatGPT as a custom MCP server with OAuth, sign in to AuditAE, and ChatGPT can call query_search_console and inspect_url for any site in your personal AuditAE workspace; a team workspace needs an API key instead, from a client that sends one, such as Cursor and Windsurf. Custom MCP servers need a ChatGPT plan that allows them, and on Business, Enterprise and Edu workspaces an admin turns on developer mode.
It reads clicks, impressions, CTR and position by query, page, country, device, date, searchAppearance, for web, image, video, news, Discover and Google News results, and Search Console's URL Inspection for one page at a time: index status, last crawl, canonical, sitemaps and rich results. The connection uses Google's read-only Search Console scope (webmasters.readonly), so it can't change settings, submit sitemaps or remove URLs.
URL inspection, yes, and it's free: inspect_url returns whether a page is indexed and why not, the canonical Google chose and the rich results it found. Google doesn't offer an API for Request indexing on ordinary pages, so that stays a button in Search Console; inspect_url returns the link. For Bing, Yandex and other IndexNow engines, submit_urls asks for a recrawl, also free. Google doesn't use IndexNow.
The Search Console tools are free, and so are the Google Analytics ones. An AuditAE account starts with $5 of credit and no card, spent only by paid tools: a fix plan is 50¢, a tracked keyword 5¢ per keyword per weekly check, an AI citation check 5–12¢ per engine plus the fix-it playbook, a WordPress write 5¢. Each tool states its price before your client calls it, and there's no subscription.
Each site uses the Search Console property you pick for it in its Settings, domain or URL-prefix, and you query it by the site's domain. One Google sign-in covers the workspace, so an agency can connect every client's property and ask about any of them from one chat. Sign-in connects your personal workspace. Team workspaces use an API key. Cursor and Windsurf connect with a key, as can other clients that send one.
Ask Search Console. Then fix the page.
Connect Google once, add one URL to Claude, ChatGPT or Cursor, and query Search Console for free. $5 credit for everything else, no card.
Comparing options? See the best MCP servers for SEO.