Google Forms MCP connector

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.

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.

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.

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.

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.

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.

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.

Yes. Google Forms is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Yes. Both let Claude, ChatGPT or Cursor use Google Forms. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Forms call.

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Forms: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.