Open-source Search Console MCP servers vs GSC Magic
Running mcp-gsc or mcp-server-gsc on your laptop is free. Here is what you trade for it, and when that trade is right.
Last updated: 2026-10-18
Open-source Search Console MCP servers such as mcp-gsc and mcp-server-gsc are free but run locally, need a Google Cloud project and credentials on disk, and do not work in claude.ai or ChatGPT on the web. GSC Magic is hosted, signs in with Google OAuth, adds Bing, GA4 and Tag Manager, stores history beyond 16 months and ships SEO reports, from $0.
The short version
Open-source servers prove the idea: an AI assistant with Search Console access is dramatically more useful than one without. They run on your machine, which means a Google Cloud project, credentials on disk and a desktop-only client. GSC Magic takes the same idea and hosts it: Google sign-in, one URL that works in claude.ai, ChatGPT and every editor, Bing and GA4 next to Search Console, history that outlives Google's 16-month window, and reports that return answers instead of rows.
Side by side
| Aspect | Local open-source MCP | GSC Magic |
|---|---|---|
| Where it runs | Your computer (Python or Node process over stdio) | Hosted; a URL you paste |
| Works in claude.ai, ChatGPT web, Claude mobile | No: local servers only work in desktop apps that spawn processes | Yes: remote MCP over Streamable HTTP with OAuth |
| Setup | Google Cloud project, enable APIs, OAuth client or service account JSON, add the account to each property, install runtime | Sign in with Google, import sites |
| Credentials | Service-account key or OAuth client secret on disk | OAuth tokens encrypted on our side; nothing on your disk |
| Data sources | Search Console; a few add GA4 | Search Console, Bing Webmaster Tools, IndexNow, Core Web Vitals, GA4, Tag Manager |
| Tools | Typically 10–25 | 77, including 8 SEO reports |
| History beyond 16 months | No | Yes on Pro and Agency, backfilled and kept |
| Alerts, digest, client reports | No | Yes on paid plans |
| Team and client scoping | No; one account per install | Roles and client groups on Agency |
| Write protection | Depends on the project; often full API access | Read-only by default; write mode is opt-in per workspace |
| Maintenance | You update it, you debug token expiry | We do |
| Price | Free, plus setup and upkeep time | Free plan; Pro $19/month |
Based on the public READMEs of the most-used open-source projects in October 2026. Projects change; check their repositories for current details.
What setup looks like
Open source
- Create a Google Cloud project and enable the Search Console API.
- Create OAuth credentials or a service account; download the JSON key.
- Add the service account as a user on every Search Console property.
- Install Python or Node, clone or install the package, point an environment variable at the key.
- Register the command in Claude Desktop, Cursor or Claude Code. Repeat on every machine.
GSC Magic
- Sign in with Google at app.gscmagic.com and pick the sites to import.
- Paste
https://mcp.gscmagic.com/mcpinto your client, or click Add to Claude.
What the agent gets back
Most local servers wrap the API one-to-one: the agent asks for rows and gets rows, up to the model's context limit. GSC Magic adds a report layer. report_traffic_drops compares two periods and returns the movers; report_cannibalization finds queries split across pages; report_quick_wins ranks positions 4–20 by potential clicks. The model reasons about a few hundred tokens instead of paging through thousands, which makes answers faster, cheaper and less prone to invention. See the full tool list.
For a vendor-by-vendor roundup, including hosted services such as GSC Wizard and AskGSC, read Best Google Search Console MCP servers in 2026.
Questions
Which open-source Search Console MCP servers exist?
The most cited at the time of writing are AminForou/mcp-gsc (Python, about 20 tools, OAuth or service account), ahonn/mcp-server-gsc (TypeScript, service account) and a long tail of smaller projects, some adding GA4 or Bing. Google publishes an official Google Analytics MCP server, but no official Search Console one.
Is a local server more private?
The data path is shorter, but a service-account key on disk is a bigger risk than a revocable OAuth token stored encrypted. Both send query results to the AI provider you use. GSC Magic adds read-only enforcement, per-request permission checks and an activity log.
Can I run GSC Magic locally too?
Yes. The same server runs locally over stdio with your own Google credentials for people who prefer that. The hosted service is the default because it needs no Google Cloud project and works in claude.ai and ChatGPT.
When is open source the right choice?
If you are one developer, you already have a Google Cloud project, you only use a desktop MCP client and you enjoy maintaining it. For anyone else, or anyone on the web apps, hosted wins on time alone.
Also read: GSC Magic vs SEO suite MCPs (Ahrefs, Semrush, SE Ranking).