mcp-google-search-console 1.0.0 → 1.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,246 +1,251 @@
1
- # Google Search Console MCP
1
+ # <img src="./assets/a1-logo.svg" alt="A1" width="40"> Google Search Console MCP
2
+
3
+ **English** | [Русский](./README.ru.md)
2
4
 
3
5
  [![npm](https://img.shields.io/npm/v/mcp-google-search-console)](https://www.npmjs.com/package/mcp-google-search-console)
4
- [![CI](https://github.com/A1-x-Tech/mcp-google-search-console/actions/workflows/ci.yml/badge.svg)](https://github.com/A1-x-Tech/mcp-google-search-console/actions/workflows/ci.yml)
5
6
  [![Glama](https://glama.ai/mcp/servers/A1-x-Tech/mcp-google-search-console/badges/score.svg)](https://glama.ai/mcp/servers/A1-x-Tech/mcp-google-search-console)
7
+ [![CI](https://github.com/A1-x-Tech/mcp-google-search-console/actions/workflows/ci.yml/badge.svg)](https://github.com/A1-x-Tech/mcp-google-search-console/actions/workflows/ci.yml)
6
8
  [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)
7
9
 
8
- MCP server for the **Google Search Console API**: search performance analytics
9
- (clicks, impressions, CTR, position), sitemap management, URL index inspection
10
- and property management — from Claude, Cursor, Codex and other AI clients, in
11
- natural language.
10
+ **A1 Google Search Console MCP** connects an AI app to Google Search Console. Investigate search performance, check whether a URL is indexed, inspect sitemaps and deliberately submit or remove a sitemap when needed.
12
11
 
13
- Ask your assistant "which queries brought the most clicks last month?", "is this
14
- page indexed?", or "resubmit the sitemap" — it drives the Search Console API for
15
- you, from a quick indexing check to a full performance analysis.
12
+ It works with the properties your Google account can access. The important detail is that it uses the exact Search Console property value — a domain property and a URL-prefix property are different objects.
16
13
 
17
- ## Quick start
14
+ - **18 tools.** Seven tools read properties, search data, sitemaps and index status; two add a property or submit a sitemap; three can remove data or call an arbitrary API method.
15
+ - **Connects from the conversation.** Say "connect Google Search Console": the server walks you through the OAuth client, catches Google's redirect on `127.0.0.1` with PKCE and keeps the tokens itself — no config files, no restart.
16
+ - **Exact property IDs.** `https://example.com/`, `https://www.example.com/` and `sc-domain:example.com` are distinct. `list_sites` shows the value to use.
17
+ - **Search data with context.** Query clicks, impressions, CTR and position by date, page, query, country, device or search appearance.
18
+ - **Indexing, not publishing.** URL inspection explains Google’s current status; it does not force a page into the index.
19
+
20
+ Start with a read-only question:
21
+
22
+ > Show the top 20 search queries for my property over the last 28 days, with clicks and CTR.
18
23
 
19
- 1. [Get OAuth credentials](#getting-credentials) for the Search Console API.
20
- 2. Add the server — for example, in Claude Code ([other clients](#installation)):
24
+ [Connect the server](#quick-start) · [Explore use cases](#what-you-can-ask-it-to-do) · [Open technical documentation](#technical-documentation)
21
25
 
22
- ```bash
23
- claude mcp add google-search-console \
24
- -e GOOGLE_SEARCH_CONSOLE_CLIENT_ID=your_client_id \
25
- -e GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET=your_client_secret \
26
- -e GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN=your_refresh_token \
27
- -- npx -y mcp-google-search-console@latest
28
- ```
26
+ ---
29
27
 
30
- 3. Ask the assistant: *"Show me the top 20 search queries for example.com over
31
- the last 28 days, with clicks and CTR."*
28
+ ## See it work in a minute
32
29
 
33
- ## Tools
30
+ > **You:** Is `https://example.com/pricing` indexed? If not, why?
31
+ >
32
+ > **Assistant:** Inspects the URL and shows the index verdict, coverage, crawl information and canonical URLs. Nothing changes.
33
+ >
34
+ > **You:** Check my submitted sitemaps and prepare a resubmission for the one with errors.
35
+ >
36
+ > **Assistant:** Shows the sitemap, its warnings and errors, then asks for confirmation before submitting it again.
37
+ >
38
+ > **You:** Confirm.
39
+ >
40
+ > **Assistant:** Resubmits the selected sitemap. It does not change page content or guarantee indexing.
34
41
 
35
- | Tool | Description |
36
- |---|---|
37
- | `list_sites` | All Search Console properties the account can access, with permission levels. |
38
- | `get_site` | One property's entry (siteUrl + permissionLevel). |
39
- | `add_site` | Add a property (stays unverified until verified in Search Console). |
40
- | `delete_site` | Unlink a property from the account (no data is deleted). |
41
- | `search_analytics` | Performance query: clicks/impressions/CTR/position by date, query, page, country, device, search appearance or hour; filters, search type, pagination, fresh-data mode. |
42
- | `get_top_queries` | Shortcut for the most common ask: top queries by clicks, optionally filtered by page substring, country or device. |
43
- | `list_sitemaps` | Submitted sitemaps (or children of a sitemap index), with errors/warnings. |
44
- | `get_sitemap` | One sitemap's status and per-content-type counts. |
45
- | `submit_sitemap` | Submit or resubmit a sitemap. |
46
- | `delete_sitemap` | Remove a sitemap from Search Console. |
47
- | `inspect_url` | Google-index status of a URL: verdict, coverage, crawl info, canonicals, rich results. |
48
- | `raw_request` | Escape hatch: any Search Console API path (webmasters/v3 or v1). |
42
+ ## Contents
49
43
 
50
- Plus resilience built in: automatic OAuth token refresh (including on 401),
51
- retries with backoff on 429 (and on 5xx/network errors for reads only —
52
- mutations are never replayed), a request timeout, and an SSRF guard so the
53
- token can't leak to a foreign host.
44
+ - [Quick start](#quick-start)
45
+ - [What you can ask it to do](#what-you-can-ask-it-to-do)
46
+ - [How Search Console properties work](#how-search-console-properties-work)
47
+ - [What can change](#what-can-change)
48
+ - [Getting access](#getting-access)
49
+ - [Configuration](#configuration)
50
+ - [Data, limits and background work](#data-limits-and-background-work)
51
+ - [Technical documentation](#technical-documentation)
52
+ - [Support](#support)
54
53
 
55
- ## Example prompts
54
+ ## Quick start
56
55
 
57
- - "Which pages lost the most clicks this month compared to the previous one?"
58
- - "Is https://example.com/pricing indexed? If not, why?"
59
- - "List queries containing 'mcp' where we rank below position 10."
60
- - "Do any of our sitemaps have errors? Resubmit the ones that do."
56
+ You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
61
57
 
62
- ## Two property formats (the #1 pitfall)
58
+ 1. Add the server to your AI app.
59
+ 2. Say "connect Google Search Console": the assistant walks you through [creating the OAuth client and approving access](#getting-access) without editing config files.
60
+ 3. Start with the read-only question above.
63
61
 
64
- The `site_url` must match the property **exactly** as registered in Search Console:
62
+ <details open><summary><strong>Codex</strong></summary>
65
63
 
66
- - **URL-prefix property** — full URL with scheme and trailing slash:
67
- `https://example.com/`. Note `http://example.com/`, `https://example.com/`
68
- and `https://www.example.com/` are three **different** properties.
69
- - **Domain property** — `sc-domain:example.com` (no scheme, no slash).
64
+ <br>
70
65
 
71
- A near-match returns 403/404. `list_sites` shows the exact registered values —
72
- the assistant will usually call it first.
66
+ <<<<<<< Updated upstream
67
+ **In the app:** open **Settings → MCP servers**, select **Add server**, choose **STDIO**, enter the command `npx -y mcp-google-search-console@latest` and environment variables `GOOGLE_SEARCH_CONSOLE_CLIENT_ID`, `GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET`, `GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN`, then select **Save** and **Restart**.
68
+ ||||||| Stash base
69
+ **In the app:** open **Settings → Plugins → MCP servers**, choose **Add server**, then add `npx -y mcp-google-search-console@latest` with `GOOGLE_SEARCH_CONSOLE_CLIENT_ID`, `GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET` and `GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN`.
70
+ =======
71
+ **In the app:** open **Settings → Plugins → MCP servers**, choose **Add server**, then add `npx -y mcp-google-search-console@latest`.
72
+ >>>>>>> Stashed changes
73
73
 
74
- ## Limitations (the API's, not the server's)
74
+ ```bash
75
+ codex mcp add google-search-console \
76
+ -- npx -y mcp-google-search-console@latest
77
+ codex mcp list
78
+ ```
75
79
 
76
- - **Dates are in Pacific Time** and `end_date` is inclusive; final analytics
77
- data lags ~2–3 days (pass `data_state: "all"` for fresh, still-changing rows).
78
- - **Filters are AND-only** — no OR across filters; regex operators use RE2 syntax.
79
- - **URL inspection quota is small**: 2,000 inspections per property per day
80
- (600/minute) — don't batch-inspect entire sites.
81
- - **Search analytics**: max 25,000 rows per request (paginate with `start_row`);
82
- anonymized long-tail queries are never returned.
83
- - **Verification is out of scope**: `add_site` registers a property, but
84
- verification happens in the Search Console UI or the Site Verification API.
80
+ [Codex MCP documentation](https://learn.chatgpt.com/docs/extend/mcp?surface=cli)
85
81
 
86
- ## Installation
82
+ </details>
87
83
 
88
- Requires Node.js 20+ (runs via `npx`, no separate install).
84
+ <details><summary><strong>Claude Code</strong></summary>
89
85
 
90
- <details open>
91
- <summary><b>Claude Code</b></summary>
86
+ <br>
92
87
 
93
88
  ```bash
94
- claude mcp add google-search-console \
95
- -e GOOGLE_SEARCH_CONSOLE_CLIENT_ID=your_client_id \
96
- -e GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET=your_client_secret \
97
- -e GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN=your_refresh_token \
89
+ claude mcp add \
90
+ --transport stdio --scope user google-search-console \
98
91
  -- npx -y mcp-google-search-console@latest
92
+ claude mcp list
99
93
  ```
100
94
 
95
+ [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp)
96
+
101
97
  </details>
102
98
 
103
- <details>
104
- <summary><b>Claude Desktop</b></summary>
99
+ <details><summary><strong>Claude Desktop</strong></summary>
105
100
 
106
- `claude_desktop_config.json` — macOS `~/Library/Application Support/Claude/`, Windows `%APPDATA%\Claude\`
101
+ <br>
102
+
103
+ The current official path is **Settings → Extensions**. For a custom desktop extension, open **Advanced settings → Extension Developer → Install Extension…**, select a `.mcpb` file and follow the prompts.
104
+
105
+ This repository currently publishes an npm stdio package and does not contain a `.mcpb` bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
107
106
 
108
107
  ```json
109
- {
110
- "mcpServers": {
111
- "google-search-console": {
112
- "command": "npx",
113
- "args": ["-y", "mcp-google-search-console@latest"],
114
- "env": {
115
- "GOOGLE_SEARCH_CONSOLE_CLIENT_ID": "your_client_id",
116
- "GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET": "your_client_secret",
117
- "GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN": "your_refresh_token"
118
- }
119
- }
120
- }
121
- }
108
+ {"mcpServers":{"google-search-console":{"command":"npx","args":["-y","mcp-google-search-console@latest"]}}}
122
109
  ```
123
110
 
111
+ In those builds, save it to `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS or `%APPDATA%\Claude\claude_desktop_config.json` on Windows.
112
+
113
+ [Claude Desktop MCP documentation](https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop)
114
+
124
115
  </details>
125
116
 
126
- <details>
127
- <summary><b>Cursor</b></summary>
117
+ <details><summary><strong>Cursor</strong></summary>
118
+
119
+ <br>
128
120
 
129
- `~/.cursor/mcp.json` (or `.cursor/mcp.json` in the project)
121
+ Add to `~/.cursor/mcp.json` on macOS/Linux or `%USERPROFILE%\.cursor\mcp.json` on Windows:
130
122
 
131
123
  ```json
132
- {
133
- "mcpServers": {
134
- "google-search-console": {
135
- "command": "npx",
136
- "args": ["-y", "mcp-google-search-console@latest"],
137
- "env": {
138
- "GOOGLE_SEARCH_CONSOLE_CLIENT_ID": "your_client_id",
139
- "GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET": "your_client_secret",
140
- "GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN": "your_refresh_token"
141
- }
142
- }
143
- }
144
- }
124
+ {"mcpServers":{"google-search-console":{"type":"stdio","command":"npx","args":["-y","mcp-google-search-console@latest"]}}}
145
125
  ```
146
126
 
127
+ [Cursor MCP documentation](https://cursor.com/docs/mcp)
128
+
147
129
  </details>
148
130
 
149
- <details>
150
- <summary><b>VS Code</b></summary>
131
+ <details><summary><strong>VS Code</strong></summary>
151
132
 
152
- `.vscode/mcp.json` — note the `servers` key (not `mcpServers`)
133
+ <br>
134
+
135
+ Run **MCP: Open User Configuration** and add:
153
136
 
154
137
  ```json
155
- {
156
- "servers": {
157
- "google-search-console": {
158
- "type": "stdio",
159
- "command": "npx",
160
- "args": ["-y", "mcp-google-search-console@latest"],
161
- "env": {
162
- "GOOGLE_SEARCH_CONSOLE_CLIENT_ID": "your_client_id",
163
- "GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET": "your_client_secret",
164
- "GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN": "your_refresh_token"
165
- }
166
- }
167
- }
168
- }
138
+ {"servers":{"google-search-console":{"type":"stdio","command":"npx","args":["-y","mcp-google-search-console@latest"]}}}
169
139
  ```
170
140
 
141
+ Check it with **MCP: List Servers**. [VS Code MCP documentation](https://code.visualstudio.com/docs/agent-customization/mcp-servers)
142
+
171
143
  </details>
172
144
 
173
- ## Getting credentials
174
-
175
- The Search Console API has no API-key access — every call needs OAuth 2.0 (the
176
- data belongs to your account). One-time setup, ~10 minutes:
177
-
178
- 1. **Create a Google Cloud project** (or reuse one) at
179
- [console.cloud.google.com](https://console.cloud.google.com/), then enable
180
- the **Google Search Console API**: *APIs & Services → Library → Google
181
- Search Console API → Enable*.
182
- 2. **Configure the OAuth consent screen** (*APIs & Services → OAuth consent
183
- screen*): choose *External*, fill in the app name and your email, and add
184
- your Google account under **Test users** (in Testing mode only listed users
185
- can authorize — no app verification needed).
186
- 3. **Create an OAuth client** (*APIs & Services → Credentials → Create
187
- credentials → OAuth client ID*), application type **Desktop app**. Save the
188
- **client ID** and **client secret**.
189
- 4. **Mint a refresh token.** The easiest way is the
190
- [OAuth 2.0 Playground](https://developers.google.com/oauthplayground):
191
- - Click the gear icon → check **Use your own OAuth credentials** → paste
192
- your client ID and secret (add
193
- `https://developers.google.com/oauthplayground` as an authorized redirect
194
- URI to the OAuth client first).
195
- - In *Step 1*, enter the scope `https://www.googleapis.com/auth/webmasters`
196
- and click **Authorize APIs**, signing in with the test-user account that
197
- owns your Search Console properties.
198
- - In *Step 2*, click **Exchange authorization code for tokens** and copy the
199
- **refresh token**.
200
- 5. Put the three values into `GOOGLE_SEARCH_CONSOLE_CLIENT_ID`,
201
- `GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET` and
202
- `GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN`. The server exchanges the refresh
203
- token for short-lived access tokens automatically.
204
-
205
- Scope notes: `https://www.googleapis.com/auth/webmasters` covers everything
206
- including sitemap submission and property management. If you only need reads
207
- (analytics, inspection, listings), the narrower
208
- `https://www.googleapis.com/auth/webmasters.readonly` works — but `add_site`,
209
- `delete_site`, `submit_sitemap` and `delete_sitemap` will then return 403.
210
- While the consent screen stays in Testing mode, refresh tokens expire after
211
- 7 days — publish the app (or keep it Internal in a Workspace domain) for
212
- long-lived tokens.
213
-
214
- ⚠️ The credentials are stored **in plain text** in your client's config — treat
215
- them like a password. The refresh token grants access to your Search Console
216
- data until revoked at
217
- [myaccount.google.com/permissions](https://myaccount.google.com/permissions).
145
+ ## What you can ask it to do
146
+
147
+ ### Find search opportunities
148
+
149
+ - Which queries and pages brought the most clicks this month?
150
+ - Which pages lost clicks compared with the previous period?
151
+ - Show queries containing `mcp` where average position is below 10.
152
+
153
+ ### Check index status and sitemaps
154
+
155
+ - Is this URL indexed? Show coverage, crawl and canonical information.
156
+ - Which submitted sitemaps have errors or warnings?
157
+ - Resubmit this sitemap after showing its current status.
158
+
159
+ ### Manage properties carefully
160
+
161
+ - List the Search Console properties I can access.
162
+ - Add this exact property value; I will verify ownership separately.
163
+ - Remove this property from my account after confirmation.
164
+
165
+ ## How Search Console properties work
166
+
167
+ A URL-prefix property must include its protocol and trailing slash, for example `https://example.com/`. A domain property is written as `sc-domain:example.com`. A near-match causes 403 or 404, so use the exact value returned by `list_sites`.
168
+
169
+ `add_site` only registers a property. Verification remains in the Search Console UI or Site Verification API. Search data uses Pacific Time; `end_date` is inclusive and final analytics data typically lags by two to three days. `data_state: "all"` can include fresher, still-changing rows.
170
+
171
+ ## What can change
172
+
173
+ | Operation | What happens | Confirmation boundary |
174
+ |---|---|---|
175
+ | List properties, analytics, sitemaps and URL status | Reads Search Console data | No change |
176
+ | Add a property | Adds a property entry; does not verify it | Changes account access |
177
+ | Submit or resubmit a sitemap | Requests processing of a sitemap | Changes Search Console state |
178
+ | Delete a property | Unlinks the property from the account; Google data is not deleted | Destructive |
179
+ | Delete a sitemap | Removes a submitted sitemap | Destructive |
180
+ | Raw API request | May call a write or delete endpoint | Potentially destructive |
181
+
182
+ The AI client controls confirmation prompts. The server marks reads, writes and destructive calls so the client can distinguish an inspection from a real change.
183
+
184
+ ## Getting access
185
+
186
+ Google Search Console requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.
187
+
188
+ ### Connect from the chat (recommended)
189
+
190
+ Say "connect Google Search Console" and the assistant runs the flow with you:
191
+
192
+ 1. `setup_instructions` prints the checklist: create or select a Google Cloud project, enable **Google Search Console API**, configure the consent screen and create a **Desktop app** OAuth client.
193
+ 2. Download that client's JSON ("Download JSON") and give the assistant its **path** — `set_client` stores it owner-only. The secret never goes through the conversation.
194
+ 3. `start_login` returns a Google consent link. Open it **on this machine** and approve; the code comes back to a one-shot listener on `127.0.0.1` (PKCE), never through the chat.
195
+ 4. `finish_login` exchanges the code and saves the tokens to `~/.config/mcp-google-search-console/credentials.json` (mode 0600) and verifies them with a real Google Search Console API call — so an API that is still switched off is caught right there.
196
+
197
+ The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. `auth_status` shows what is connected, `logout` revokes and deletes it.
198
+
199
+ ### Environment variables (CI, unattended installs)
200
+
201
+ 1. Create or select a Google Cloud project and enable **Google Search Console API**.
202
+ 2. Configure the OAuth consent screen and create a **Desktop app** OAuth client.
203
+ 3. Use the [OAuth 2.0 Playground](https://developers.google.com/oauthplayground) with **Use your own OAuth credentials** to authorize the Google account that can access the properties and obtain a refresh token.
204
+ 4. Use `https://www.googleapis.com/auth/webmasters` to include sitemaps and property changes. Use `https://www.googleapis.com/auth/webmasters.readonly` only if you intentionally need read-only access.
205
+
206
+ Testing-mode refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal Workspace app, for long-lived access. Treat the client secret and refresh token as passwords.
218
207
 
219
208
  ## Configuration
220
209
 
221
- | Variable | Required | Default | Description |
222
- |---|---|---|---|
223
- | `GOOGLE_SEARCH_CONSOLE_CLIENT_ID` | yes* | — | OAuth2 client id (refresh flow). |
224
- | `GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET` | yes* | — | OAuth2 client secret (refresh flow). |
225
- | `GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN` | yes* | — | OAuth2 refresh token (refresh flow). |
226
- | `GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN` | yes* | — | Alternative: a static access token (~1 h lifetime), mostly for testing. |
227
- | `GOOGLE_SEARCH_CONSOLE_API_BASE` | no | `https://searchconsole.googleapis.com` | API root override. |
228
- | `GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS` | no | `60000` | Per-request timeout, ms. |
229
- | `GOOGLE_SEARCH_CONSOLE_MAX_RETRIES` | no | `3` | Retries on transient errors. |
210
+ Every variable is optional — with none of them the server connects [from the chat](#connect-from-the-chat-recommended).
211
+
212
+ | Variable | Required | Description |
213
+ |---|---|---|
214
+ | `GOOGLE_SEARCH_CONSOLE_CLIENT_ID` | No* | OAuth client ID. |
215
+ | `GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET` | No* | OAuth client secret. |
216
+ | `GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN` | No* | OAuth refresh token. |
217
+ | `GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN` | No* | Short-lived alternative to the OAuth trio. |
218
+ | `GOOGLE_SEARCH_CONSOLE_OAUTH_PORT` | No | Fixed loopback port for the in-chat login; useful over SSH port forwarding. |
219
+ | `GOOGLE_SEARCH_CONSOLE_API_BASE` | No | API base URL override. |
220
+ | `GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS` | No | Per-request timeout; default `60000` ms. |
221
+ | `GOOGLE_SEARCH_CONSOLE_MAX_RETRIES` | No | Temporary-error retries; default `3`. |
222
+
223
+ \* Provide either the OAuth trio or an access token.
230
224
 
231
- \* Either the three refresh-flow variables together, **or** `GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN`.
225
+ ## Data, limits and background work
232
226
 
233
- ## Documentation
227
+ - **Privacy.** The local server calls Google and sends anonymous telemetry with an installation ID, versions and tool names — never OAuth tokens, property data, tool arguments or prompts. Set `ASKADS_TELEMETRY=0` to opt out.
228
+ - **API limits.** URL inspection allows 2,000 inspections per property per day and 600 per minute. Analytics returns at most 25,000 rows per request; long-tail anonymized queries are never returned. Use pagination and do not inspect whole sites URL by URL.
229
+ - **No background monitoring.** The server works only while called. If your AI app supports scheduled tasks, it can periodically check a sitemap or an important URL.
234
230
 
235
- - [All tools](https://github.com/A1-x-Tech/mcp-google-search-console/blob/main/docs/TOOLS.md) — full reference with parameters and notes.
236
- - [Development](https://github.com/A1-x-Tech/mcp-google-search-console/blob/main/docs/DEVELOPMENT.md) — build, tests, smoke check, telemetry.
237
- - [Publishing](https://github.com/A1-x-Tech/mcp-google-search-console/blob/main/docs/PUBLISHING.md) — releasing and MCP-catalog listing.
231
+ ## Technical documentation
232
+
233
+ - [MCP capability catalog](./docs/capabilities/index.md) — task-oriented pages for every tool.
234
+ - [All tools and inputs](./docs/TOOLS.md)
235
+ - [Development documentation](./docs/DEVELOPMENT.md)
236
+ - [Publishing documentation](./docs/PUBLISHING.md)
237
+ - [Google Search Console API](https://developers.google.com/webmaster-tools)
238
238
 
239
239
  ## Support
240
240
 
241
- Questions, ideas, issues — Telegram [@gistrec](http://t.me/gistrec) or
242
- [GitHub issues](https://github.com/A1-x-Tech/mcp-google-search-console/issues).
241
+ Found a bug or need a scenario? [Create an issue](https://github.com/A1-x-Tech/mcp-google-search-console/issues) or write in [Telegram](https://t.me/a1_mcp).
242
+
243
+ <br>
243
244
 
244
- ## License
245
+ <p align="center">
246
+ <img src="https://github.com/ztemerbekov/a1-yandex-kit-skills/raw/main/assets/images/mona-hifive-yandex-kit-warm.gif" alt="Две Моны дают пять" width="256">
247
+ </p>
245
248
 
246
- MIT — see [LICENSE](./LICENSE).
249
+ <p align="center">
250
+ You made it to the end!
251
+ </p>