Google Search Console, Bing and GA4 for any MCP client

GSC Magic speaks standard Model Context Protocol over Streamable HTTP. Any client that supports remote servers can connect: Hermes Agent, OpenClaw, Grok, Zed, agent frameworks and your own code.

Last updated: 2026-10-18

In short

GSC Magic is a standard remote MCP server at https://mcp.gscmagic.com/mcp (Streamable HTTP) with OAuth 2.1 dynamic client registration and bearer tokens, so any Model Context Protocol client, agent framework or script can connect and call its 77 Search Console, Bing, GA4 and reporting tools.

Set up in 3 steps

  1. Endpoint: https://mcp.gscmagic.com/mcp (POST for JSON-RPC, Streamable HTTP transport).
  2. Authentication: OAuth 2.1 with dynamic client registration (discovery at /.well-known/oauth-protected-resource), or a bearer access token created in the dashboard.
  3. Call tools/list to see what your plan and permissions allow, then tools/call.
curl with an access token
curl -X POST https://mcp.gscmagic.com/mcp \
  -H "Authorization: Bearer gsm_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Good to know

  • Every tool declares readOnlyHint, destructiveHint and openWorldHint, so clients can show what is safe.
  • Tool schemas avoid unions, $ref and additionalProperties so they load in every client, including the strictest ones.
  • Results are compact JSON with explicit truncation flags; large exports are never written to disk in the hosted service.

What to ask once connected

  • "List my Search Console properties and the one with the most clicks last 28 days."
  • "Which queries sit in positions 4–10 with the most impressions? Suggest title changes."
  • "Compare clicks this month with last month by page and tell me what moved."
  • "Which URLs in my sitemap are not indexed, and what does the inspection say?"
  • "How many sessions came from ChatGPT, Perplexity and Claude last month, and to which pages?"

More in 25 SEO prompts for AI agents; the full tool list is on the tools page.

Troubleshooting

POST /mcp returns 401 before I can register.

That is expected: the 401 carries a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource/mcp. Follow it to discover the authorization server, register with /register, then authorize with PKCE. Or skip OAuth and send a dashboard access token as Bearer.

The client cannot register: redirect_uri rejected.

Dynamic registration accepts loopback addresses and the known callback origins of Claude and ChatGPT. For other hosted clients use an access token, or contact support to allow-list the origin.

tools/list returns fewer tools than the catalogue.

The list is computed per account: plan, Google scopes granted, Bing and IndexNow keys, write mode and client group all filter it. A free account with only Google connected sees the Search Console, report, GA4 and Tag Manager tools.

SSE or streaming errors.

Send Accept: application/json, text/event-stream and keep the Mcp-Session-Id header if your client uses sessions. The server is stateless, so reconnecting is always safe.

Questions about Any MCP client

Is there a local (stdio) version?

Yes. The same server runs locally with your own Google credentials for people who prefer that; the hosted service is the recommended path because it needs no Google Cloud project.

What are the rate limits?

Plan limits apply per account (Free: 200 calls a month, 10 a day). The endpoint also has a generous per-IP limit sized for the shared addresses of Claude and ChatGPT.

Other clients

Claude · ChatGPT · Claude Code · Cursor · Windsurf · VS Code