Google Search Console MCP: search analytics, URL inspection, site management.
{
"mcpServers": {
"io-github-mharnett-google-gsc": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Google Search Console MCP: search analytics, URL inspection, site management.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Production ready MCP server with real-time search, extract, map & crawl.
Web and local search using Brave Search API
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
🚀 OneSearch MCP Server: Web Search & Scraper & Extract, Support agent-browser, SearXNG, Tavily, DuckDuckGo, Bing, etc.
MCP Security Weekly
Get CVE alerts and security updates for io.github.mharnett/google-gsc and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for Google Search Console -- search analytics, URL inspection, and site management via Claude.
npm install mcp-gsc
git clone https://github.com/drak-marketing/mcp-gsc.git
cd mcp-gsc
npm install
npm run build
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-gsc"]
}
}
}
| 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