mcp-google-forms 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 +217 -145
- package/README.ru.md +293 -0
- package/dist/client.js +62 -14
- package/dist/config.js +41 -12
- package/dist/index.js +64 -13
- package/dist/telemetry.js +3 -3
- package/dist/tools/auth.js +39 -0
- package/dist/tools/forms.js +5 -6
- package/dist/tools/items.js +1 -1
- package/package.json +2 -1
- package/test/dist-smoke.test.js +83 -1
package/README.md
CHANGED
|
@@ -1,142 +1,160 @@
|
|
|
1
|
-
# Google Forms MCP
|
|
1
|
+
# <img src="./assets/a1-logo.svg" alt="A1" width="40"> Google Forms MCP
|
|
2
|
+
|
|
3
|
+
**English** | [Русский](./README.ru.md)
|
|
2
4
|
|
|
3
5
|
[](https://www.npmjs.com/package/mcp-google-forms)
|
|
4
|
-
[](https://github.com/A1-x-Tech/mcp-google-forms/actions/workflows/ci.yml)
|
|
5
6
|
[](https://glama.ai/mcp/servers/A1-x-Tech/mcp-google-forms)
|
|
7
|
+
[](https://github.com/A1-x-Tech/mcp-google-forms/actions/workflows/ci.yml)
|
|
6
8
|
[](./LICENSE)
|
|
7
9
|
|
|
8
|
-
MCP
|
|
9
|
-
responses and set up push notifications for new submissions — from Claude, Cursor, Codex and
|
|
10
|
-
other AI clients, in natural language.
|
|
10
|
+
**A1 Google Forms MCP** lets an AI app build and manage Google Forms in plain language. Create a survey, choose its questions, publish it when ready, read answers and use notifications for new submissions.
|
|
11
11
|
|
|
12
|
-
|
|
13
|
-
"show me yesterday's responses", or "close the form for responses" — it drives the Forms API
|
|
14
|
-
for you, from a blank form to response analysis.
|
|
12
|
+
It uses the Google Forms API with your Google account. It distinguishes a draft form from a published form and makes the limits of the Forms API explicit instead of implying that every form task is possible.
|
|
15
13
|
|
|
16
|
-
|
|
14
|
+
- **19 tools.** Inspect form structure and responses, create and edit forms and questions, manage publishing, and configure Pub/Sub watches.
|
|
15
|
+
- **Connects from the conversation.** Say "connect Google Forms": 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
|
+
- **Publish deliberately.** Forms made through the API start unpublished, so they cannot collect responses until you publish them.
|
|
17
|
+
- **Responses stay intact.** The API can read responses but cannot create or edit them; the server has no tool that submits answers.
|
|
18
|
+
- **Minimal Google scopes.** It uses `forms.body` and `forms.responses.readonly`, without broad Drive access.
|
|
17
19
|
|
|
18
|
-
|
|
19
|
-
2. Add the server — for example, in Claude Code ([other clients](#installation)):
|
|
20
|
+
Start with a read-only question:
|
|
20
21
|
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
22
|
+
> Show me yesterday’s responses to the customer feedback form and summarize the free-text answers.
|
|
23
|
+
|
|
24
|
+
[Connect the server](#quick-start) · [Explore use cases](#what-you-can-ask-it-to-do) · [Open technical documentation](#technical-documentation)
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## See it work in a minute
|
|
29
|
+
|
|
30
|
+
> **You:** Show me the questions and response settings of the customer feedback form.
|
|
31
|
+
>
|
|
32
|
+
> **Assistant:** Shows the form, its items, whether it is published and whether it accepts responses. Nothing changes.
|
|
33
|
+
>
|
|
34
|
+
> **You:** Prepare a required 1–5 rating question called “How was your experience?” after the first question.
|
|
35
|
+
>
|
|
36
|
+
> **Assistant:** Shows the target form, position and proposed question, then asks for confirmation before adding it.
|
|
37
|
+
>
|
|
38
|
+
> **You:** Confirm.
|
|
39
|
+
>
|
|
40
|
+
> **Assistant:** Adds the question to the form. It does not publish or close the form unless you ask separately.
|
|
28
41
|
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
| `raw_request` | Escape hatch: any Forms API v1 path (e.g. a custom `batchUpdate` with grids). |
|
|
49
|
-
|
|
50
|
-
Plus resilience built in: automatic OAuth token refresh (including on 401), retries with
|
|
51
|
-
backoff on 429 (and on 5xx/network errors for reads only — writes are never replayed), a
|
|
52
|
-
request timeout, and an SSRF guard so the token can't leak to a foreign host.
|
|
53
|
-
|
|
54
|
-
## Example prompts
|
|
55
|
-
|
|
56
|
-
- "Create an RSVP form for the offsite, ask for name, meal preference (veg/meat/fish) and
|
|
57
|
-
arrival date, then publish it and give me the link."
|
|
58
|
-
- "Turn the 'Onboarding quiz' form into a quiz and make every question required."
|
|
59
|
-
- "How many responses came in since Monday? Summarize the free-text feedback."
|
|
60
|
-
- "Stop accepting responses on the feedback form."
|
|
61
|
-
|
|
62
|
-
## Limitations (the API's, not the server's)
|
|
63
|
-
|
|
64
|
-
- **Responses are read-only.** The Forms API cannot submit or edit responses — there is no
|
|
65
|
-
such endpoint, so this server has no submit tool either.
|
|
66
|
-
- **API-created forms start unpublished** and don't accept responses until published — use
|
|
67
|
-
`publish: true` on `create_form` or `set_publish_settings`. Legacy forms (from before the
|
|
68
|
-
publish model) don't support `set_publish_settings` at all.
|
|
69
|
-
- **File-upload questions can't be created** via the API (existing ones are readable).
|
|
70
|
-
- **Quotas are per minute** (reads 975/project, `list_responses` 450, writes 375); the server
|
|
71
|
-
backs off on 429 automatically.
|
|
72
|
-
|
|
73
|
-
## Installation
|
|
74
|
-
|
|
75
|
-
Requires Node.js 20+ (runs via `npx`, no separate install).
|
|
42
|
+
## Contents
|
|
43
|
+
|
|
44
|
+
- [Quick start](#quick-start)
|
|
45
|
+
- [What you can ask it to do](#what-you-can-ask-it-to-do)
|
|
46
|
+
- [How a form changes](#how-a-form-changes)
|
|
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)
|
|
53
|
+
|
|
54
|
+
## Quick start
|
|
55
|
+
|
|
56
|
+
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
|
|
57
|
+
|
|
58
|
+
1. Add the server to your AI app.
|
|
59
|
+
2. Say "connect Google Forms": the assistant walks you through [creating the OAuth client and approving access](#getting-access) without editing config files.
|
|
60
|
+
3. Ask the read-only question above.
|
|
76
61
|
|
|
77
62
|
<details open>
|
|
78
|
-
<summary><
|
|
63
|
+
<summary><strong>Codex</strong></summary>
|
|
64
|
+
|
|
65
|
+
<br>
|
|
66
|
+
|
|
67
|
+
**In the app:** open **Settings → MCP servers**, select **Add server**, choose **STDIO**, enter the command `npx -y mcp-google-forms@latest` and environment variables `GOOGLE_FORMS_CLIENT_ID`, `GOOGLE_FORMS_CLIENT_SECRET`, `GOOGLE_FORMS_REFRESH_TOKEN`, then select **Save** and **Restart**.
|
|
68
|
+
|
|
69
|
+
**From the command line:**
|
|
70
|
+
|
|
71
|
+
```bash
|
|
72
|
+
codex mcp add google-forms \
|
|
73
|
+
-- npx -y mcp-google-forms@latest
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
```bash
|
|
77
|
+
codex mcp list
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
[Codex MCP documentation](https://learn.chatgpt.com/docs/extend/mcp?surface=cli)
|
|
81
|
+
|
|
82
|
+
</details>
|
|
83
|
+
|
|
84
|
+
<details>
|
|
85
|
+
<summary><strong>Claude Code</strong></summary>
|
|
86
|
+
|
|
87
|
+
<br>
|
|
79
88
|
|
|
80
89
|
```bash
|
|
81
|
-
claude mcp add
|
|
82
|
-
-
|
|
83
|
-
-e GOOGLE_FORMS_CLIENT_SECRET=your_client_secret \
|
|
84
|
-
-e GOOGLE_FORMS_REFRESH_TOKEN=your_refresh_token \
|
|
90
|
+
claude mcp add \
|
|
91
|
+
--transport stdio --scope user google-forms \
|
|
85
92
|
-- npx -y mcp-google-forms@latest
|
|
86
93
|
```
|
|
87
94
|
|
|
95
|
+
```bash
|
|
96
|
+
claude mcp list
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
[Claude Code MCP documentation](https://code.claude.com/docs/en/mcp)
|
|
100
|
+
|
|
88
101
|
</details>
|
|
89
102
|
|
|
90
103
|
<details>
|
|
91
|
-
<summary><
|
|
104
|
+
<summary><strong>Claude Desktop</strong></summary>
|
|
105
|
+
|
|
106
|
+
<br>
|
|
107
|
+
|
|
108
|
+
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.
|
|
92
109
|
|
|
93
|
-
`
|
|
110
|
+
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:
|
|
94
111
|
|
|
95
112
|
```json
|
|
96
113
|
{
|
|
97
114
|
"mcpServers": {
|
|
98
115
|
"google-forms": {
|
|
99
116
|
"command": "npx",
|
|
100
|
-
"args": ["-y", "mcp-google-forms@latest"]
|
|
101
|
-
"env": {
|
|
102
|
-
"GOOGLE_FORMS_CLIENT_ID": "your_client_id",
|
|
103
|
-
"GOOGLE_FORMS_CLIENT_SECRET": "your_client_secret",
|
|
104
|
-
"GOOGLE_FORMS_REFRESH_TOKEN": "your_refresh_token"
|
|
105
|
-
}
|
|
117
|
+
"args": ["-y", "mcp-google-forms@latest"]
|
|
106
118
|
}
|
|
107
119
|
}
|
|
108
120
|
}
|
|
109
121
|
```
|
|
110
122
|
|
|
123
|
+
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.
|
|
124
|
+
|
|
125
|
+
[Claude Desktop MCP documentation](https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop)
|
|
126
|
+
|
|
111
127
|
</details>
|
|
112
128
|
|
|
113
129
|
<details>
|
|
114
|
-
<summary><
|
|
130
|
+
<summary><strong>Cursor</strong></summary>
|
|
131
|
+
|
|
132
|
+
<br>
|
|
115
133
|
|
|
116
|
-
`~/.cursor/mcp.json`
|
|
134
|
+
Add this to `~/.cursor/mcp.json` on macOS/Linux or `%USERPROFILE%\.cursor\mcp.json` on Windows:
|
|
117
135
|
|
|
118
136
|
```json
|
|
119
137
|
{
|
|
120
138
|
"mcpServers": {
|
|
121
139
|
"google-forms": {
|
|
140
|
+
"type": "stdio",
|
|
122
141
|
"command": "npx",
|
|
123
|
-
"args": ["-y", "mcp-google-forms@latest"]
|
|
124
|
-
"env": {
|
|
125
|
-
"GOOGLE_FORMS_CLIENT_ID": "your_client_id",
|
|
126
|
-
"GOOGLE_FORMS_CLIENT_SECRET": "your_client_secret",
|
|
127
|
-
"GOOGLE_FORMS_REFRESH_TOKEN": "your_refresh_token"
|
|
128
|
-
}
|
|
142
|
+
"args": ["-y", "mcp-google-forms@latest"]
|
|
129
143
|
}
|
|
130
144
|
}
|
|
131
145
|
}
|
|
132
146
|
```
|
|
133
147
|
|
|
148
|
+
[Cursor MCP documentation](https://cursor.com/docs/mcp)
|
|
149
|
+
|
|
134
150
|
</details>
|
|
135
151
|
|
|
136
152
|
<details>
|
|
137
|
-
<summary><
|
|
153
|
+
<summary><strong>VS Code</strong></summary>
|
|
138
154
|
|
|
139
|
-
|
|
155
|
+
<br>
|
|
156
|
+
|
|
157
|
+
Run **MCP: Open User Configuration** and add:
|
|
140
158
|
|
|
141
159
|
```json
|
|
142
160
|
{
|
|
@@ -144,78 +162,132 @@ claude mcp add google-forms \
|
|
|
144
162
|
"google-forms": {
|
|
145
163
|
"type": "stdio",
|
|
146
164
|
"command": "npx",
|
|
147
|
-
"args": ["-y", "mcp-google-forms@latest"]
|
|
148
|
-
"env": {
|
|
149
|
-
"GOOGLE_FORMS_CLIENT_ID": "your_client_id",
|
|
150
|
-
"GOOGLE_FORMS_CLIENT_SECRET": "your_client_secret",
|
|
151
|
-
"GOOGLE_FORMS_REFRESH_TOKEN": "your_refresh_token"
|
|
152
|
-
}
|
|
165
|
+
"args": ["-y", "mcp-google-forms@latest"]
|
|
153
166
|
}
|
|
154
167
|
}
|
|
155
168
|
}
|
|
156
169
|
```
|
|
157
170
|
|
|
171
|
+
Check it with **MCP: List Servers**.
|
|
172
|
+
|
|
173
|
+
[VS Code MCP documentation](https://code.visualstudio.com/docs/agent-customization/mcp-servers)
|
|
174
|
+
|
|
158
175
|
</details>
|
|
159
176
|
|
|
160
|
-
##
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
|
|
177
|
+
## What you can ask it to do
|
|
178
|
+
|
|
179
|
+
### Inspect a survey and its answers
|
|
180
|
+
|
|
181
|
+
- Show this form’s questions, response settings and responder link.
|
|
182
|
+
- How many answers arrived since Monday? Summarize the free-text feedback.
|
|
183
|
+
- Show one response by ID.
|
|
184
|
+
|
|
185
|
+
### Build and improve a form
|
|
186
|
+
|
|
187
|
+
- Create an RSVP form with name, meal preference and arrival date.
|
|
188
|
+
- Add a required rating, dropdown, date, time, choice or text question.
|
|
189
|
+
- Reorder a question or update a title, description, quiz mode or email collection.
|
|
190
|
+
|
|
191
|
+
### Publish and connect notifications
|
|
192
|
+
|
|
193
|
+
- Publish a prepared form and show its responder URL.
|
|
194
|
+
- Stop accepting new responses without deleting the form.
|
|
195
|
+
- Create, renew or remove a Cloud Pub/Sub watch for new submissions.
|
|
196
|
+
|
|
197
|
+
## How a form changes
|
|
198
|
+
|
|
199
|
+
1. `create_form` creates a **form**, which starts unpublished by default.
|
|
200
|
+
2. Questions are **items**, identified by their position in the form.
|
|
201
|
+
3. Publishing makes a form available to respondents; closing response collection leaves it published but stops new submissions.
|
|
202
|
+
4. Responses are a separate read-only record. The API cannot submit, edit or delete a respondent’s answer.
|
|
203
|
+
|
|
204
|
+
File-upload questions cannot be created through the Forms API, although existing file-upload items can be read. Legacy forms created before Google’s publish model may not support publishing settings.
|
|
205
|
+
|
|
206
|
+
## What can change
|
|
207
|
+
|
|
208
|
+
| Operation | What happens | Confirmation boundary |
|
|
209
|
+
|---|---|---|
|
|
210
|
+
| Read a form and its responses | Reads form structure and submissions | No change |
|
|
211
|
+
| Create a form | Adds an unpublished form | Changes Google Forms |
|
|
212
|
+
| Add or move a question | Changes form items | Changes a form |
|
|
213
|
+
| Update form info, settings or an item | Changes title, settings or a selected question | Changes a form |
|
|
214
|
+
| Publish, unpublish, open or close responses | Changes who can use the form | Changes a form’s public availability |
|
|
215
|
+
| Delete an item | Removes a selected question | Destructive |
|
|
216
|
+
| Manage a Pub/Sub watch | Creates, renews or deletes notification delivery | Potentially destructive |
|
|
217
|
+
| Raw API request | Can call API methods without a dedicated tool | Potentially destructive |
|
|
218
|
+
|
|
219
|
+
The AI client controls confirmation prompts. The server marks reads, writes and destructive tools so the client can distinguish an inspection from a live change.
|
|
220
|
+
|
|
221
|
+
## Getting access
|
|
222
|
+
|
|
223
|
+
Google Forms requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.
|
|
224
|
+
|
|
225
|
+
### Connect from the chat (recommended)
|
|
226
|
+
|
|
227
|
+
Say "connect Google Forms" and the assistant runs the flow with you:
|
|
228
|
+
|
|
229
|
+
1. `setup_instructions` prints the checklist: create or select a Google Cloud project, enable **Google Forms API**, configure the consent screen and create a **Desktop app** OAuth client.
|
|
230
|
+
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.
|
|
231
|
+
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.
|
|
232
|
+
4. `finish_login` exchanges the code and saves the tokens to `~/.config/mcp-google-forms/credentials.json` (mode 0600).
|
|
233
|
+
|
|
234
|
+
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.
|
|
235
|
+
|
|
236
|
+
### Environment variables (CI, unattended installs)
|
|
237
|
+
|
|
238
|
+
1. Create or select a Google Cloud project and enable **Google Forms API**.
|
|
239
|
+
2. Configure the OAuth consent screen and create a **Desktop app** OAuth client.
|
|
240
|
+
3. Authorize the Google account that owns or can edit the forms. The [OAuth 2.0 Playground](https://developers.google.com/oauthplayground) can obtain the refresh token when **Use your own OAuth credentials** is enabled.
|
|
241
|
+
4. Request both scopes:
|
|
242
|
+
|
|
243
|
+
```text
|
|
244
|
+
https://www.googleapis.com/auth/forms.body
|
|
245
|
+
https://www.googleapis.com/auth/forms.responses.readonly
|
|
246
|
+
```
|
|
247
|
+
|
|
248
|
+
Testing-mode OAuth refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal app in a Workspace domain, when you need long-lived access. Treat the client secret and refresh token as passwords.
|
|
193
249
|
|
|
194
250
|
## Configuration
|
|
195
251
|
|
|
196
|
-
|
|
197
|
-
|---|---|---|---|
|
|
198
|
-
| `GOOGLE_FORMS_CLIENT_ID` | yes* | — | OAuth2 client id (refresh flow). |
|
|
199
|
-
| `GOOGLE_FORMS_CLIENT_SECRET` | yes* | — | OAuth2 client secret (refresh flow). |
|
|
200
|
-
| `GOOGLE_FORMS_REFRESH_TOKEN` | yes* | — | OAuth2 refresh token (refresh flow). |
|
|
201
|
-
| `GOOGLE_FORMS_ACCESS_TOKEN` | yes* | — | Alternative: a static access token (~1 h lifetime), mostly for testing. |
|
|
202
|
-
| `GOOGLE_FORMS_API_BASE` | no | `https://forms.googleapis.com` | API root override. |
|
|
203
|
-
| `GOOGLE_FORMS_TIMEOUT_MS` | no | `60000` | Per-request timeout, ms. |
|
|
204
|
-
| `GOOGLE_FORMS_MAX_RETRIES` | no | `3` | Retries on transient errors. |
|
|
252
|
+
Every variable is optional — with none of them the server connects [from the chat](#connect-from-the-chat-recommended).
|
|
205
253
|
|
|
206
|
-
|
|
254
|
+
| Variable | Required | Description |
|
|
255
|
+
|---|---|---|
|
|
256
|
+
| `GOOGLE_FORMS_CLIENT_ID` | No* | OAuth client ID. |
|
|
257
|
+
| `GOOGLE_FORMS_CLIENT_SECRET` | No* | OAuth client secret. |
|
|
258
|
+
| `GOOGLE_FORMS_REFRESH_TOKEN` | No* | OAuth refresh token. |
|
|
259
|
+
| `GOOGLE_FORMS_ACCESS_TOKEN` | No* | Short-lived alternative to the OAuth trio. |
|
|
260
|
+
| `GOOGLE_FORMS_OAUTH_PORT` | No | Fixed loopback port for the in-chat login; useful over SSH port forwarding. |
|
|
261
|
+
| `GOOGLE_FORMS_API_BASE` | No | Google Forms API base URL override. |
|
|
262
|
+
| `GOOGLE_FORMS_TIMEOUT_MS` | No | Per-request timeout; default `60000` ms. |
|
|
263
|
+
| `GOOGLE_FORMS_MAX_RETRIES` | No | Temporary-error retries; default `3`. |
|
|
207
264
|
|
|
208
|
-
|
|
265
|
+
\* Provide either the OAuth trio or an access token.
|
|
209
266
|
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
-
|
|
267
|
+
## Data, limits and background work
|
|
268
|
+
|
|
269
|
+
- **Requests go to Google Forms.** The local server refreshes Google OAuth tokens and calls the Forms API. Its anonymous telemetry contains an installation ID, package version, AI client and platform versions, and tool names — never OAuth tokens, form data, tool arguments or prompts. Set `ASKADS_TELEMETRY=0` to opt out.
|
|
270
|
+
- **Google applies per-minute quotas.** The documented limits are 975 reads per project, 450 `list_responses` calls and 375 writes. On `429`, the server uses backoff; reads also retry after network and `5xx` errors, while writes are not replayed after an uncertain failure.
|
|
271
|
+
- **There is no background polling.** The server runs only when called. Pub/Sub watches can notify your own infrastructure about new responses; if your AI app supports scheduled tasks, it can also check responses periodically.
|
|
272
|
+
|
|
273
|
+
## Technical documentation
|
|
274
|
+
|
|
275
|
+
- [MCP capability catalog](./docs/capabilities/index.md) — task-oriented pages for every tool.
|
|
276
|
+
- [All tools and inputs](./docs/TOOLS.md)
|
|
277
|
+
- [Development documentation](./docs/DEVELOPMENT.md)
|
|
278
|
+
- [Publishing documentation](./docs/PUBLISHING.md)
|
|
279
|
+
- [Google Forms API reference](https://developers.google.com/forms/api)
|
|
213
280
|
|
|
214
281
|
## Support
|
|
215
282
|
|
|
216
|
-
|
|
217
|
-
|
|
283
|
+
Found a bug or need a scenario? [Create an issue](https://github.com/A1-x-Tech/mcp-google-forms/issues) or write in [Telegram](https://t.me/a1_mcp).
|
|
284
|
+
|
|
285
|
+
<br>
|
|
218
286
|
|
|
219
|
-
|
|
287
|
+
<p align="center">
|
|
288
|
+
<img src="https://github.com/ztemerbekov/a1-yandex-kit-skills/raw/main/assets/images/mona-hifive-yandex-kit-warm.gif" alt="Две Моны дают пять" width="256">
|
|
289
|
+
</p>
|
|
220
290
|
|
|
221
|
-
|
|
291
|
+
<p align="center">
|
|
292
|
+
You made it to the end!
|
|
293
|
+
</p>
|