Survey
Google Forms MCP connector
Connecting Google Forms to Elaichi lets Claude, ChatGPT, Cursor and the Elaichi Agent read your forms and their responses, so anyone on your team can ask what people answered and get a plain answer.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
5 tools
How to connect
How to connect Google Forms to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Google Forms once
-
Open Connections, choose Add connection, and pick Google Forms.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Google Forms. Google Forms's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Google Forms to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Google Forms to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Google Forms to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Google Forms to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Google Forms through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Summarize event feedback the morning after
Ask for the themes in last night's post-event survey responses and get a short readout before the debrief starts. No spreadsheet export, no scrolling through hundreds of rows.
-
HR
Read the pulse survey without the export
Ask which questions scored lowest in this quarter's engagement form and which comments mention workload. The answer comes from the live responses, not a copy someone pasted last week.
-
Support
Spot repeat complaints in satisfaction forms
Ask which products or issues come up most often in the customer satisfaction form this month, and compare it to last month. Catch a pattern before it turns into a ticket backlog.
-
Operations
Check who has filled in the intake form
Ask how many responses the new vendor intake form has, and which submissions arrived since Monday. Chase the gaps instead of counting them by hand.
-
Events
Pull registration answers before the venue call
Ask how many attendees requested dietary accommodations or accessibility support across the registration form, so the numbers you give the venue are the real ones.
-
Product
Find the strongest quotes in user research
Ask for the responses to the beta feedback form that mention a specific feature, and have the agent pull out the clearest quotes for the roadmap review.
Try asking
- “Summarize this week's responses to the onboarding feedback form.”
- “Which forms collected the most responses this month?”
- “List every question on the customer satisfaction form.”
AI tools
Google Forms tools for your AI agents
5 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Forms, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Google Forms gets you
6 screens from the product, each doing one job for your Google Forms account.
The agent
Ask about Google Forms responses in plain language.
Answers come from live forms and responses, not a stale export.
- forms
- responses
- questions
- respondents
Ask Elaichi to work across your apps.
Summarize this week's responses to the onboarding feedback form.
Which forms collected the most responses this month?
List every question on the customer satisfaction form.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor read your forms.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
5 Google Forms tools, zero custom code.
Forms, responses and user info, each with listed methods ready to call.
- Get single Google Forms form by ID
- List all Google Forms forms
- List all Google Forms responses
- Get single Google Forms response by ID
ElaichiToolsToolboxes
Every team gets its own Google Forms toolbox.
Research, support and people teams each work in a scope you define.
- Research
- Support
- People
- Marketing
ElaichiToolboxesShared connections
Share a Google Forms account, never the password.
See who connected each account and how many teams and members use it.
- Research
- Support
- People Ops
- Marketing EMEA
ElaichiConnectionsAudit log
Every response read is written down.
When, who, what happened, type and resource, in an append only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns responses into an approved digest.
Six steps fetch responses, group them, draft a digest, wait for approval, post back.
Google Forms digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch forms
Google Forms
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Google Forms
Queued
Collections and dashboards
Google Forms numbers arrive before anyone asks.
Four metrics, 14 days of responses created and a team breakdown, refreshed on schedule.
Google Forms health
Refreshed 4 minutes ago · every 15 minutes · from the forms collection
Forms
1,284 ↓ 12%
Responses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Forms created
Last 14 days
By team
Share of activity
Research 34%
Support 27%
People Ops 21%
Marketing EMEA 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Google Forms to Claude?
Connect Google Forms in Elaichi first: click connect, sign in with your Google account when the Google sign-in screen appears, and approve access. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. From that point Claude can read your Google Forms forms and responses as you.
Does Google Forms work with ChatGPT and Cursor as well as Claude?
Yes. Once Google Forms is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Google Forms once and every client you use picks it up.
What can an AI agent actually do with my Google Forms data?
With Google Forms connected, an agent can list your forms, open a specific form to see its questions, pull the responses people have submitted, and look at a single response in detail. In practice that means you can ask things like how many people answered the onboarding survey this week, what the most common complaint in the feedback form is, or what one particular respondent said. This connector reads Google Forms; it does not create forms or edit answers.
Does connecting Google Forms give the AI every form in my Google account?
No. When you connect Google Forms, the agent sees only the forms and responses your own Google account can already open, following Google's own sharing rules. Elaichi can narrow that further, for example by restricting which actions a team may use, but it can never widen access beyond what you personally have in Google Forms.
Can I stop an agent from deleting or changing things in Google Forms?
The Google Forms connector in Elaichi is read-only: it lists forms, opens forms, and reads responses, so there is nothing it can delete or change in Google Forms. Beyond that, Elaichi restrictions work per action, and a blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it. You can, for example, let a team see which forms exist without letting them open individual responses.
What happens to a Google Forms connection when someone leaves?
When a person is offboarded in Elaichi, their access to Google Forms through Elaichi ends at once, in every client they had connected. If they had shared a Google Forms connection with a team, that connection keeps working for everyone else. Disconnecting Google Forms once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Google Forms in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.