# 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. Source: https://elaichi.ai/connectors/googleforms/ ## Facts | | | | --- | --- | | Application | Google Forms | | Category | Survey | | AI tools | 5 | | Authentication | Connects over OAuth | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Google Forms is connected - 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. ## Connect Google Forms in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Google Forms. 2. Optionally set Share with, then press Connect. 3. Approve it in Google Forms. Google Forms's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Google Forms tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Google Forms to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Google Forms to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Google Forms tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Google Forms through Elaichi ### Summarize event feedback the morning after Marketing. 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. ### Read the pulse survey without the export HR. 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. ### Spot repeat complaints in satisfaction forms Support. 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. ### Check who has filled in the intake form Operations. 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. ### Pull registration answers before the venue call Events. 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. ### Find the strongest quotes in user research Product. 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. ## 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 my team share one Google Forms connection? Yes. One person connects Google Forms in Elaichi and shares the connection with a team, and nobody else on the team ever handles a Google credential. Each person still signs in to Elaichi as themselves, so every read of a Google Forms response is logged under the name of the person who asked for it. ### 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. ## All 5 Google Forms tools Every tool below is callable through https://api.elaichi.ai/mcp once Google Forms is connected, subject to the toolbox it is in and the restrictions on the caller. - **Get single Google Forms form by ID** (Get). Get a single Google Form by id. Returns the full form object including its structure, title, and items. Required: id. - **List all Google Forms forms** (List). List all Google Forms accessible in Google Drive. Returns an array of file objects representing forms, including id, name, and mimeType. - **List all Google Forms responses** (List). List all responses submitted to a specific Google Form. Returns an array of form response objects. Required: form_id. - **Get single Google Forms response by ID** (Get). Get a single response submitted to a Google Form by its id. Returns the full response object. Required: form_id and id. - **List all Google Forms user info** (List). Retrieves basic profile information about the authenticated user in Google Calendar. The response includes essential details such as the user's unique identifier (sub), full name (name), first name (given_name), last name (family_name), profile picture URL (picture), and email address (email).