Google Search Console, Bing and GA4 in OpenClaw

OpenClaw connects to remote MCP servers over Streamable HTTP and runs the MCP OAuth sign-in from its CLI, catching the callback on 127.0.0.1. GSC Magic accepts that sign-in.

Last updated: 2026-10-30

In short

Run openclaw mcp add gsc-magic --url https://mcp.gscmagic.com/mcp --transport streamable-http, set auth: "oauth" on the server, run openclaw mcp login gsc-magic on a machine with a browser, and your OpenClaw agents can use Search Console, Bing and GA4 tools.

Set up in 4 steps

  1. Create a GSC Magic account, connect Google and import your sites.
  2. Add the server with the first command below.
  3. In your OpenClaw config set auth: "oauth" on mcp.servers.gsc-magic, then run openclaw mcp login gsc-magic on a machine with a browser and allow access on the GSC Magic page.
  4. Run openclaw mcp doctor gsc-magic --probe to check the tools.
Run in a terminal 
openclaw mcp add gsc-magic --url https://mcp.gscmagic.com/mcp --transport streamable-http
openclaw mcp login gsc-magic
Start free

Good to know

  • Keep tokens out of config literals; OpenClaw has secret references for sensitive headers.
  • Sign-in uses OAuth: the client opens a GSC Magic page where you sign in and approve once. No API key or token to paste.
  • On Free your agent can only read. On Pro and Agency write tools are available, and the owner can switch write mode off in Settings in one click.

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

Sign in from Settings → MCP fails with a redirect error.

Browser sign-in through the Gateway's public HTTPS address returns there, which GSC Magic does not accept. Run openclaw mcp login gsc-magic from the terminal instead, or use a token.

The Gateway runs on a server without a browser.

Create an access token in the dashboard, remove auth: "oauth" from mcp.servers.gsc-magic and add headers: { Authorization: "Bearer gsm_…" }. OpenClaw ignores headers while auth is "oauth".

The startup log says authentication refused (401).

Sign in again with openclaw mcp login gsc-magic, or replace the token if you use a header.

Questions about OpenClaw

Can I limit which GSC Magic tools OpenClaw exposes?

Yes. Add --include with tool names or patterns, for example --include 'report_*,gsc_query_analytics', or set toolFilter in the config.

Other clients

Claude · ChatGPT · Claude Code · Cursor · Windsurf · VS Code · Any MCP client · Gemini CLI · Zed · Cline · Continue · n8n · LibreChat · goose · Warp · Raycast · Hermes Agent · Grok