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 +188 -183
- package/README.ru.md +251 -0
- package/dist/client.js +61 -5
- package/dist/config.js +41 -12
- package/dist/index.js +62 -13
- package/dist/telemetry.js +3 -3
- package/dist/tools/auth.js +113 -0
- package/package.json +2 -1
- package/test/dist-smoke.test.js +83 -1
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
|
[](https://www.npmjs.com/package/mcp-google-search-console)
|
|
4
|
-
[](https://github.com/A1-x-Tech/mcp-google-search-console/actions/workflows/ci.yml)
|
|
5
6
|
[](https://glama.ai/mcp/servers/A1-x-Tech/mcp-google-search-console)
|
|
7
|
+
[](https://github.com/A1-x-Tech/mcp-google-search-console/actions/workflows/ci.yml)
|
|
6
8
|
[](./LICENSE)
|
|
7
9
|
|
|
8
|
-
MCP
|
|
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
|
-
|
|
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
|
-
|
|
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
|
-
|
|
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
|
-
|
|
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
|
-
|
|
31
|
-
the last 28 days, with clicks and CTR."*
|
|
28
|
+
## See it work in a minute
|
|
32
29
|
|
|
33
|
-
|
|
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
|
-
|
|
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
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
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
|
-
##
|
|
54
|
+
## Quick start
|
|
56
55
|
|
|
57
|
-
|
|
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
|
-
|
|
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
|
-
|
|
62
|
+
<details open><summary><strong>Codex</strong></summary>
|
|
65
63
|
|
|
66
|
-
|
|
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
|
-
|
|
72
|
-
the
|
|
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
|
-
|
|
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
|
-
|
|
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
|
-
|
|
82
|
+
</details>
|
|
87
83
|
|
|
88
|
-
|
|
84
|
+
<details><summary><strong>Claude Code</strong></summary>
|
|
89
85
|
|
|
90
|
-
<
|
|
91
|
-
<summary><b>Claude Code</b></summary>
|
|
86
|
+
<br>
|
|
92
87
|
|
|
93
88
|
```bash
|
|
94
|
-
claude mcp add
|
|
95
|
-
-
|
|
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
|
-
|
|
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
|
-
|
|
117
|
+
<details><summary><strong>Cursor</strong></summary>
|
|
118
|
+
|
|
119
|
+
<br>
|
|
128
120
|
|
|
129
|
-
`~/.cursor/mcp.json`
|
|
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
|
-
|
|
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
|
-
##
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
|
|
197
|
-
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
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
|
-
|
|
222
|
-
|
|
223
|
-
|
|
|
224
|
-
|
|
225
|
-
| `
|
|
226
|
-
| `
|
|
227
|
-
| `
|
|
228
|
-
| `
|
|
229
|
-
| `
|
|
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
|
-
|
|
225
|
+
## Data, limits and background work
|
|
232
226
|
|
|
233
|
-
|
|
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
|
-
|
|
236
|
-
|
|
237
|
-
- [
|
|
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
|
-
|
|
242
|
-
|
|
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
|
-
|
|
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
|
-
|
|
249
|
+
<p align="center">
|
|
250
|
+
You made it to the end!
|
|
251
|
+
</p>
|