MCP Servers
acamolese/google-search-console-mcp
MCP (Model Context Protocol) server for Google Search Console.
Our verdict
We have not reviewed acamolese/google-search-console-mcp yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About acamolese/google-search-console-mcp
An MCP server that connects AI coding assistants like Claude and Cursor to Google Search Console data. It allows read-only queries of GSC performance metrics and generates HTML SEO audit reports through OAuth-based authentication.
Best for
Developers and SEOs who want to query Google Search Console data directly from AI coding assistants.
Use cases
- Pull search performance data into an AI assistant for analysis
- Generate branded HTML SEO audit reports from GSC data
- Integrate GSC queries into automated SEO workflows
Notes
3 stars on GitHub. Last updated 2026-04-23. Licensed MIT.
Pros
- Works with multiple MCP-compatible clients
- OAuth-based authentication for secure access
- MIT licensed for open use and modification
Cons
- Read-only access limits data manipulation
- Requires MCP client setup and OAuth configuration
- Small community with only 3 stars on GitHub
Key facts
What we have checked
- Days since the last commit
- 12
- GitHub forks
- 4
- GitHub stars
- 9
- Open issues
- 1
- Releases in the last 90 days
- 2
Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
uvx mcp-google-search-console authTools exposed
gsc_sitesgsc_site_detailsgsc_querygsc_performance_overviewgsc_compare_periodsgsc_quick_winsgsc_ctr_gapsgsc_cannibalizationgsc_traffic_dropsgsc_content_decaygsc_alertsgsc_portfoliogsc_indexing_issuesgsc_inspect_urlgsc_sitemapsgsc_doctorgsc_auditGSC_AUTH_MODEGSC_REPORT_LANGUAGEGSC_DATA_STATE
Clients the listing names (not checked here)
Claude Desktop, Claude Code, Cursor
Install
Add acamolese/google-search-console-mcp to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --transport stdio google-search-console-mcp -- uvx mcp-google-search-console@3.0.1Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"google-search-console-mcp": {
"command": "uvx",
"args": [
"mcp-google-search-console@3.0.1"
]
}
}
}Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"google-search-console-mcp": {
"command": "uvx",
"args": [
"mcp-google-search-console@3.0.1"
]
}
}
}VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"servers": {
"google-search-console-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-google-search-console@3.0.1"
]
}
}
}Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.google-search-console-mcp]
command = "uvx"
args = ["mcp-google-search-console@3.0.1"]- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What acamolese/google-search-console-mcp connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 3.0.1Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 3.0.1Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 3.0.1Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 3.0.1Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 3.0.1Config checked | Codex docs |
Health and security
Is acamolese/google-search-console-mcp looked after, and what do its setup files show
Health score
52 out of 100
| Part | Points | What we saw |
|---|---|---|
| Recent activity | 30 of 30 | Last push 12 days ago |
| Releases | 11.3 of 15 | 2 releases in 90 days |
| Issue replies | Not counted | The latest check has no issue response reading (fewer than 3 measured issues, or issues switched off) |
| Maintainer | 0 of 15 | Owned by a single user |
| Official source | 0 of 20 | Community server |
Sources
Where this comes from
- GitHubRegistry
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.