MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection
Google Search Console is an MCP integration. MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection.
The published npm package is @ni-c/google-search-console-mcp, version 0.3.0. Its declared MCP transport is stdio.
The package declares GSC_SERVICE_ACCOUNT_KEY: Service account key as JSON, or base64-encoded JSON. One of the three credential options.; GSC_SERVICE_ACCOUNT_KEY_FILE: Path to a service account key file. Alternative to GSC_SERVICE_ACCOUNT_KEY.; GSC_CLIENT_ID: OAuth2 client id. Use together with GSC_CLIENT_SECRET and GSC_REFRESH_TOKEN.; GSC_CLIENT_SECRET: OAuth2 client secret. All three OAuth2 variables are required together.; GSC_REFRESH_TOKEN: OAuth2 refresh token. All three OAuth2 variables are required together.; GOOGLE_APPLICATION_CREDENTIALS: Path to application default credentials, used when no GSC_ credential is set.; GSC_SITE_URL: Default property, e.g. sc-domain:example.com or https://example.com/ — makes site_url optional; GSC_ALLOWED_SITES: Comma-separated properties this server may touch; anything else is refused; GSC_READ_ONLY: Set to true to register only the read tools (default: false); GSC_ALLOW_TOOLS: Comma-separated tool names or list_ prefixes to register; 'essential' selects a curated preset (default: all tools); GSC_DENY_TOOLS: Comma-separated tool names or list_ prefixes to remove from whatever the allow list left.
The published oci package is ghcr.io/ni-c/google-search-console-mcp:0.3.0. Its declared MCP transport is stdio.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.3.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related search & web scraping MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| GSC_SERVICE_ACCOUNT_KEY | Service account key as JSON, or base64-encoded JSON. One of the three credential options. | Optional |
| GSC_SERVICE_ACCOUNT_KEY_FILE | Path to a service account key file. Alternative to GSC_SERVICE_ACCOUNT_KEY. | Optional |
| GSC_CLIENT_ID | OAuth2 client id. Use together with GSC_CLIENT_SECRET and GSC_REFRESH_TOKEN. | Optional |
| GSC_CLIENT_SECRET | OAuth2 client secret. All three OAuth2 variables are required together. | Optional |
| GSC_REFRESH_TOKEN | OAuth2 refresh token. All three OAuth2 variables are required together. | Optional |
| GOOGLE_APPLICATION_CREDENTIALS | Path to application default credentials, used when no GSC_ credential is set. | Optional |
| GSC_SITE_URL | Default property, e.g. sc-domain:example.com or https://example.com/ — makes site_url optional | Optional |
| GSC_ALLOWED_SITES | Comma-separated properties this server may touch; anything else is refused | Optional |
| GSC_READ_ONLY | Set to true to register only the read tools (default: false) | Optional |
| GSC_ALLOW_TOOLS | Comma-separated tool names or list_ prefixes to register; 'essential' selects a curated preset (default: all tools) | Optional |
| GSC_DENY_TOOLS | Comma-separated tool names or list_ prefixes to remove from whatever the allow list left | Optional |
Retrieve public web pages as readable Markdown with the reference Fetch MCP server, including pagination for longer responses.
Use Firecrawl MCP to retrieve website content and extract information for research through Firecrawl’s API-backed web tools.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Automates browsers and APIs, enabling Large Language Models (LLMs) to interact with web pages for tasks like screenshot capture and JavaScript
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.