Google Search Console Connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DO_NOT_TRACK | No | Set to 1 to never send usage metrics | |
| GSC_CLIENT_ID | No | Use your own OAuth client ID from the environment instead of the built-in sign-in | |
| GSC_PROJECT_DIR | No | Project folder, if your MCP client starts servers elsewhere | |
| GSC_CONNECT_HOME | No | Where credentials are stored (default ~/.gsc-connect) | |
| GSC_CONNECT_PORT | No | Preferred local port (default 4817; falls back to any free port) | |
| GSC_CLIENT_SECRET | No | Use your own OAuth client secret from the environment instead of the built-in sign-in | |
| GSC_CONNECT_TELEMETRY | No | Set to 0 to never send usage metrics | |
| GSC_CONNECT_UPDATE_CHECK | No | Set to 0 to not check npm for new versions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gsc_connectA | Open the Connect page in the user's browser: Google Cloud setup, Google sign-in, and choosing this project's property. Waits until the user finishes (up to 10 minutes). |
| gsc_open_dashboardA | Open the local Search Console dashboard (performance, queries, pages, opportunities, indexing) in the user's browser. |
| gsc_statusA | Show whether Google is connected, which account, and which property this project is linked to. |
| gsc_disconnectA | Revoke this machine's Google access token and delete it locally. |
| gsc_list_sitesA | List Search Console properties the connected account can access, with permission level. |
| gsc_link_projectA | Save which Search Console property this website project uses (writes .gsc-connect.json in the project root; contains no secrets). |
| gsc_search_analyticsA | Query Search Console performance data (clicks, impressions, CTR, position). Data is available for the last 16 months and usually lags 2–3 days. CTR is returned as a fraction. |
| gsc_performance_summaryA | Totals for a period compared with the previous period of equal length, plus top queries and pages. A good first call for 'how is the site doing?'. |
| gsc_inspect_urlA | URL Inspection: index status, coverage, last crawl, canonical and rich results for one URL in the property. |
| gsc_list_sitemapsA | Sitemaps submitted for the property, with status, errors, warnings and last download time. |
| gsc_submit_sitemapC | Submit (or resubmit) a sitemap URL for the property. |
| gsc_delete_sitemapA | Remove a sitemap from the property in Search Console (does not touch the file on the website). |
| gsc_add_siteA | Add a property to Search Console for the connected account. It stays unverified until gsc_verify_site succeeds. |
| gsc_get_verification_tokenA | Get the ownership verification token. META returns a tag for the site's (URL-prefix properties). FILE returns an HTML file name/content to serve at the site root. DNS_TXT is required for sc-domain properties. |
| gsc_verify_siteA | Ask Google to check the verification token placed by the chosen method. Run after deploying the meta tag / file or adding the DNS record. |
| gsc_export_reportA | Download Search Console reports in one step: Dates, Queries, Pages, Countries, Devices, Search appearance, Query-page pairs and Sitemaps as CSV (same columns as Search Console's Export, plus previous-period comparison), report.json, and summary.md written for you to read next. Saved to .gsc-reports/ in the project (added to .gitignore). |
| gsc_add_annotationA | Add a dated note to this project's performance chart, e.g. after deploying SEO changes ('Rewrote service page titles'). Shown in the dashboard so changes can be matched to traffic movements. |
| gsc_set_brand_termsB | Set the words that make a query 'branded' (business name, product names, common misspellings). Enables branded vs non-branded analysis in gsc_search_analytics, reports and the dashboard. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools target distinct Search Console setup, verification, reporting, or sitemap tasks, but gsc_search_analytics and gsc_performance_summary partially overlap, and gsc_connect/gsc_link_project both relate to selecting a property. Descriptions largely mitigate the confusion, so boundaries are mostly clear.
All 18 tools use a consistent gsc_ snake_case prefix with predictable verb_noun or noun forms, such as gsc_list_sites, gsc_submit_sitemap, and gsc_get_verification_token. There are no mixed conventions or vague names.
18 tools is on the high side for a connector, but the set is grouped into setup/auth, analytics, verification, sitemaps, and reporting. Each tool maps to a specific operation, making it feature-rich rather than bloated.
The surface covers connection/status, property add/list/link/verify, analytics summary and querying, URL inspection, sitemaps list/submit/delete, report export, annotations, and brand terms. The main gap is property deletion/removal, but core workflows are otherwise covered.