Google Search Console Audit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSC_CLIENT_ID | No | OAuth 2.0 Client ID for Google Search Console API | |
| GSC_CLIENT_SECRET | No | OAuth 2.0 Client Secret for Google Search Console API | |
| GSC_REFRESH_TOKEN | No | OAuth refresh token for Google Search Console API |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gsc_sitesA | List all verified sites in Google Search Console. |
| gsc_site_detailsA | Get details about a specific site in Google Search Console. Args: site_url: Site URL (e.g. "https://example.com/" or "sc-domain:example.com"). |
| gsc_queryB | Search Console performance report (top queries and pages with metrics). Args: site_url: Site URL (e.g. "https://example.com/" or "sc-domain:example.com"). date_from: Start date (YYYY-MM-DD). date_to: End date (YYYY-MM-DD). dimensions: Comma-separated dimensions (query, page, country, device, date). row_limit: Maximum rows (default 100, max 25000). |
| gsc_performance_overviewC | Summary of site performance (total clicks, impressions, avg CTR, avg position). Args: site_url: Site URL (e.g. "https://example.com/" or "sc-domain:example.com"). date_from: Start date (YYYY-MM-DD). date_to: End date (YYYY-MM-DD). |
| gsc_indexing_issuesA | Bulk indexing check for multiple pages using the URL Inspection API. Use this tool to quickly verify whether a batch of URLs is indexed by Google and
spot common issues (blocked by robots.txt, crawl errors, page-fetch failures, not
yet indexed). For each URL it returns a compact summary; to get the full
inspection payload (mobile usability, rich results, AMP) for a single page, use
Quota note: the URL Inspection API enforces ~60 requests per minute and
~2000 per day per property. Keep the Args:
site_url: Verified property URL. Domain property format "sc-domain:example.com"
or URL-prefix format "https://example.com/".
pages: List of fully qualified page URLs to check. They must belong to the
Returns:
JSON array, one entry per input URL, each with:
- url: the input URL
- verdict: one of PASS, PARTIAL, FAIL, NEUTRAL, VERDICT_UNSPECIFIED
- coverageState: human-readable coverage description
- robotsTxtState: e.g. ALLOWED / DISALLOWED
- indexingState: e.g. INDEXING_ALLOWED / BLOCKED_BY_META_TAG
- lastCrawlTime: ISO-8601 timestamp of Google's last crawl attempt
- pageFetchState: SUCCESSFUL / SOFT_404 / ACCESS_DENIED / etc.
- crawledAs: DESKTOP / MOBILE
If a single URL fails, its entry contains an |
| gsc_inspect_urlA | Full URL Inspection for a single page (index + mobile + rich results + AMP). Returns the complete Quota note: the URL Inspection API enforces ~60 requests per minute and ~2000 per day per property. Args:
site_url: Verified property URL. Domain property format "sc-domain:example.com"
or URL-prefix format "https://example.com/". Must be a property the
authenticated user can access.
page_url: Fully qualified page URL under Returns: JSON object with (at minimum) these sub-objects when available: - indexStatusResult: verdict, coverageState, lastCrawlTime, canonicals, robotsTxtState, indexingState, pageFetchState, crawledAs, referring URLs - mobileUsabilityResult: verdict, issues list - richResultsResult: verdict, detected rich-result item types and issues - ampResult: verdict, AMP URL, indexing state (only for AMP pages) - inspectionResultLink: link to the Search Console UI for the same inspection |
| gsc_sitemapsA | List all sitemaps submitted for a property, with errors/warnings and timestamps. Use this to check which sitemaps Google knows about for a property, when they were last submitted and downloaded, and whether Google recorded warnings or errors while processing them. Useful for auditing sitemap hygiene before crawl-budget work or to confirm a newly submitted sitemap was picked up. Note: this tool is read-only. Submitting or deleting sitemaps requires the
Args: site_url: Verified property URL. Domain property format "sc-domain:example.com" or URL-prefix format "https://example.com/". Returns: JSON array of sitemap entries, one per submitted sitemap, each with: - path: absolute URL of the sitemap (e.g. "https://example.com/sitemap.xml") - lastSubmitted: ISO-8601 timestamp of last (re)submission - lastDownloaded: ISO-8601 timestamp of Google's last fetch - isPending: true while Google has not finished processing the sitemap - isSitemapsIndex: true if it is a sitemap index file referencing other sitemaps - warnings: number of non-blocking issues detected by Google - errors: number of blocking errors detected by Google Returns an empty array if no sitemaps are submitted for the property. |
| gsc_auditA | Generate a complete HTML SEO audit report for a Search Console property. Runs multiple queries (overview, previous-period comparison, top queries, top pages, devices, countries, daily trend, sitemaps, indexing check), detects common issues, builds an actionable strategy and renders everything in a self-contained HTML report with Chart.js graphs. The report layout and colors can be customized via branding.json. IMPORTANT: If the user has not specified a date range, ask them before calling this tool. Do not assume defaults. Args: site_url: Site URL (e.g. "https://example.com/" or "sc-domain:example.com"). date_from: Start date (YYYY-MM-DD). date_to: End date (YYYY-MM-DD). output_dir: Directory where to save the HTML report. Defaults to ~/gsc-reports/. branding_path: Optional path to a custom branding.json overriding the default one. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/acamolese/google-search-console-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server