mcp-gsc
Google Search Console Insights with Claude AI for SEOs
No outside reports on file
The main danger is that sensitive website performance and competitive data from Google Search Console could leak through AI conversations or be misused if credentials are compromised.
Based on public adoption and transparency signals as of Oct 21, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachLocal or standard API callsLOW
- CredentialsRequires API key or tokenREVIEW
- Package sourceGitHub (AminForou/mcp-gsc)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
No npm or PyPI package is listed. Install from source: github.com/AminForou/mcp-gsc ↗
Everything known
We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.
0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30
Popularity grade: C (from public signals such as stars and downloads, not a code review). Graded 2026-10-21.
Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.
About MCP Gsc
This is a connector that lets Claude AI read data from Google Search Console, a tool that shows how your website appears in Google search results. It helps SEOs (search engine optimization experts) analyze keyword performance, click-through rates, and search visibility by connecting Claude directly to your Google Search Console account.
Who it’s for
SEO professionals and website owners who want to use Claude AI to analyze and interpret their Search Console data. It's for people who manage websites and want AI-powered insights about their search performance.
Alternatives
- Google Search Console API (used directly with custom scripts for more control)
- Screaming Frog SEO Spider (desktop tool for site analysis without AI)
- Semrush or Ahrefs (professional SEO platforms with built-in AI-like features)
- Manual Search Console analysis (reading Google's native dashboard and reports)
Setup
Check these steps against the project’s own instructions before running anything.
Follow the project's README for installation and configuration instructions, as setup may require authenticating with your Google account and configuring Claude Desktop or your AI platform.
Why this grade
Signal-based grade (3/7 points): well starred on GitHub, public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- GitHub stars
- 2.1k
- Listing last refreshed
- 2026-10-29
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Risks to watch for
- Google account access: The connector needs permission to read your Google Search Console account, which contains data about your website's search performance and visitor behavior
- Website data exposure: If the AI shares your Search Console data in conversations, your keyword strategies, traffic patterns, and site weaknesses could be revealed
- Malicious prompts: An attacker could craft questions designed to trick the AI into leaking sensitive search data or competitor insights
- Token/quota abuse: Misconfigured use could consume your Google API quota quickly or generate unexpected costs
- Credential handling: If authentication tokens are stored insecurely, attackers might access your Search Console account
How to lower the risk
Least-privilege permissions
- Use a Google service account with read-only Search Console access
- Never grant this tool write or delete permissions
Network isolation
- Run the connector on a trusted machine or network only
- Avoid using it on shared or public computers
Monitoring
- Regularly check your Google Cloud audit logs for unusual API access
- Review which data Claude is actually requesting from Search Console
Red flags to watch for
- Unexpected API usage spikes or cost increases
- Claude returning data you didn't ask it to retrieve
- Error messages indicating authentication failures or access denials
Questions
How do I install MCP Gsc?
MCP Gsc does not publish a standalone npm or PyPI package. Clone or follow the setup instructions in its source repository at github.com/AminForou/mcp-gsc.
Are there security reports about MCP Gsc?
No reports found for this package in our research (last checked 2026-10-30). MCP Gsc currently holds Grade C (Moderate risk signals) based on public adoption and transparency signals. Key risk areas to watch include google account access, website data exposure, malicious prompts.
Is MCP Gsc actively maintained?
MCP Gsc has 2.1k GitHub stars. Our directory data was last refreshed on 2026-10-29. Check recent commit activity, release tags, and open issues at github.com/AminForou/mcp-gsc before pinning it in production.
What are alternatives to MCP Gsc?
Notable alternatives to MCP Gsc include Google Search Console API, Screaming Frog SEO Spider, Semrush or Ahrefs, Manual Search Console analysis. You can also compare MCP Gsc side by side with other MCP servers in the Related tools section on this page.
Key facts
- Type
- App connector
- Publisher
- AminForou
- Source code
- github.com/AminForou/mcp-gsc
- Est. context load
- ~1k tokens / turn (~6 tool schemas, 0.5% of 200k context)
- Popularity
- 2.1k GitHub stars
- Last updated
- 2026-10-29
- Last graded
- 2026-10-21
Community
Discussions for MCP Gsc
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude