Server data from the Official MCP Registry
Google Search Console MCP: search analytics, URL inspection, site management.
Google Search Console MCP: search analytics, URL inspection, site management.
Valid MCP server (4 strong, 4 medium validity signals). 2 known CVEs in dependencies (0 critical, 2 high severity) Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
8 files analyzed · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: GOOGLE_APPLICATION_CREDENTIALS
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-mharnett-google-gsc": {
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "your-google-application-credentials-here"
},
"args": [
"-y",
"mcp-google-gsc"
],
"command": "npx"
}
}
}From the project's GitHub README.
MCP server for Google Search Console -- search analytics, URL inspection, and site management via Claude.
npm install mcp-google-gsc
git clone https://github.com/mharnett/mcp-search-console.git
cd mcp-google-gsc
npm install
npm run build
Security: Never share your .mcp.json file or commit it to git -- it may contain API credentials. Add .mcp.json to your .gitignore.
Create a config.json in the project root (see config.example.json for the full structure):
{
"default_credentials": "/path/to/service-account-key.json",
"clients": {
"my-project": {
"site_url": "sc-domain:example.com",
"credentials": "/path/to/service-account-key.json"
}
}
}
Alternatively, set GOOGLE_APPLICATION_CREDENTIALS to the path of your service account key file. The config file takes precedence when present.
Add to your Claude Code .mcp.json:
{
"mcpServers": {
"gsc": {
"command": "node",
"args": ["/path/to/mcp-gsc/dist/index.js"]
}
}
}
Or if installed globally:
{
"mcpServers": {
"gsc": {
"command": "npx",
"args": ["mcp-google-gsc"]
}
}
}
Claude Desktop: Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).
| Tool | Description |
|---|---|
gsc_get_client_context | Detect the GSC property from your working directory based on config mapping |
gsc_list_sites | List all verified Search Console properties accessible to the service account |
gsc_search_analytics | Query search performance data (clicks, impressions, CTR, position) with dimension and filter support |
gsc_inspection | Inspect a URL for indexing status, mobile usability, and rich results |
Supports dimensions: query, page, device, country, date. Filter by any dimension with operators like equals, contains, notContains. Date range defaults to the last 28 days.
Returns index coverage, crawl status, mobile usability verdict, and rich result details for a specific URL within a property.
MIT -- see LICENSE.
Built by Mark Harnett / drak-marketing
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.