A Google Analytics and Search Console MCP server with nothing to set up.
Ask Claude, ChatGPT or Cursor about your GA4 traffic and your Search Console queries. Connect Google once in AuditAE and point your client at one URL — no Google Cloud project, no service account, no credentials file. The Google tools are free.
query_search_console · query_google_analytics · get_ai_referral_traffic · 72 tools on the server · no card
Three steps, no Google Cloud.
- Add your site to AuditAE (free, $5 credit, no card).
- Connect Google in the site’s Settings and pick its GA4 property and Search Console site. 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, no key needed. Then ask it about your 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 to Google Analytics walks through each screen, from adding the site to the first GA4 question.
Questions people actually run.
Your client picks the dimensions, metrics and date ranges. The last prompt is the one only this server answers: it joins your Google rankings with whether AI answers cite you for the same query.
“Which queries lost the most clicks in the last 28 days compared with the 28 before?”
query_search_console (query, two date ranges)
Free
“Show pages with over 1,000 impressions and a CTR under 1% — those titles need rewriting.”
query_search_console (page, ordered by impressions)
Free
“How did sessions and conversions from organic search change month over month, by landing page?”
query_google_analytics (landingPagePlusQueryString, sessionDefaultChannelGroup)
Free
“We rank 4–10 for 'best invoicing app 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 checked
Everything else the server does.
Connecting AuditAE for your Google data connects all 72 tools. The Google queries 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.
AI search citations
13 toolsCheck whether ChatGPT, Perplexity, Gemini and Google AI Overviews cite you for a prompt, who they cite instead, share of voice across a prompt set, content gaps, and competitor prompts. Checks are 5–12¢ per engine.
How citation checks workFix plans
1 toolget_fix_plan reads your latest audit and the live page, then returns the exact edits: the sentence to rewrite, FAQs and schema to add, title and meta. Steps for WordPress, Next.js, Shopify, Webflow and more. 50¢.
WordPress edits
26 toolsOn a site paired with the free plugin, the agent edits posts, Yoast and Rank Math meta, schema and llms.txt, including Elementor pages. Reads are free, writes 5¢.
WordPress MCP setupTechnical audits and schema
12 toolsCore Web Vitals and on-page checks, a site crawl, agent-readiness, tech-stack detection, a backlink summary, IndexNow submission, and schema you can generate and validate.
Account and client portals
9 toolsList your sites, check your balance, create a top-up link, and share a live client portal with traffic, Google search and AI visibility.
Hosted vs run-it-yourself.
The open-source Google Analytics and Search Console MCP servers are good if you’re comfortable in Google Cloud. If you’d rather not create a project and a credentials file for every property, this is the shortcut.
| AuditAE (hosted) | Self-hosted servers | |
|---|---|---|
| Setup | Sign in with Google once, pick the property | Google Cloud project, enabled APIs, OAuth client or service account, credentials file |
| Hosting | Remote URL — nothing to run | Runs on your machine (Python or Node) |
| Sites | Every site in the workspace, by domain | One property per config, usually |
| Clients | Claude, ChatGPT, Claude Code, Codex, and VS Code (sign-in); Cursor and Windsurf (API key) | Local clients; web apps need your own hosting |
| Beyond Google data | AI citation checks, fix plans, WordPress edits — 72 tools | Analytics or Search Console only |
| Price | Google reads free; $5 free credit for the paid tools | Free, self-hosted |
Questions worth asking.
Straight answers on the Google Analytics and Search Console MCP tools.
Yes, several. Google publishes an open-source GA4 MCP server you run locally with Google Cloud credentials, and there are community servers on GitHub. AuditAE is a hosted option: you connect Google once in the dashboard and point Claude, ChatGPT or Cursor at one URL, with no Google Cloud project to set up.
Google doesn't publish one; the options are community servers you host yourself, which need a Google Cloud project and credentials. AuditAE's query_search_console runs the Search Console search analytics query for any site in your workspace over the Google connection you already made in the dashboard.
Search Console clicks, impressions, CTR and average position by query, page, country, device, date or search appearance, and any GA4 report: dimensions and metrics you name, with filters and sorting. The connection uses Google's read-only Analytics and Search Console scopes, so the tools can't change your Google settings.
The two Google tools are free. An AuditAE account starts with $5 of credit and no card; that credit is only spent by paid tools such as AI citation checks (5–12¢ per engine) or fix plans (50¢), and each tool states its price before you call it.
The GA4 property and Search Console site you pick for each site in its Settings. One Google sign-in covers the workspace; an agency can connect every client's properties and query them all by domain.
The tools fetch live from Google on each call. Your Google tokens are stored encrypted, and you can disconnect Google in the dashboard at any time.
Ask your data. Skip the setup.
Connect Google once, add one URL to your client, and query GA4 and Search Console for free. $5 credit for everything else, no card.
Comparing options? See the best MCP servers for SEO.