Google Search Console MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, available at https://cotlet.dev/app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Google Search Console through Cotlet.dev. Call google_search_console_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_search_console_guideB | How to work in Google Search Console (request indexing and remove URLs): its screens and the sign-in link. Call this first. |
| google_search_console_statusB | Check that your Cotlet.dev account and Google Search Console are ready: account, credits and Google Search Console connection. |
| google_search_console_openB | Open a Google Search Console page in your signed-in Cloud Browser (default https://search.google.com) to work with request indexing and remove URLs. |
| google_search_console_readA | Read the current Google Search Console page: its text and numbered buttons, links and fields. |
| google_search_console_clickB | Click a numbered element on the current Google Search Console page. |
| google_search_console_typeB | Type text into a numbered field on the current Google Search Console page. |
| google_search_console_closeA | Close the Google Search Console browser session when the work is done, so credits stop running. |
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 7 tools
Each tool maps to a distinct browser-automation action (open/close session, read page, click element, type text), so misselection risk is low. The only mild overlap is between the guide and status tools, since both are pre-flight helpers, but their descriptions clearly separate instructions from account/connection checks.
All seven tools share the uniform google_search_console_<action> snake_case pattern, with short, predictable action suffixes (guide, status, open, close, read, click, type). No mixed conventions or styles appear anywhere in the set.
Seven tools is well within a tight, purposeful scope for a browser-driven GSC client. Every tool earns its place: session lifecycle (open/close), perception (read), interaction (click/type), and onboarding (guide/status), with no redundancy.
The core loop of open session, read page, click/type, and close is fully covered, plus guide and status for setup. Minor gaps exist: no explicit key-press/submit, scroll, wait-for-load, or direct URL navigation tool, which agents can mostly work around via clicks.