# Google Forms MCP connector

Connecting Google Forms to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot 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 |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## 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.

## Google Forms MCP connector for 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.

## Google Forms MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Google Forms MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.

## Google Forms MCP connector for 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.

## Google Forms MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## 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

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Google Forms tool needs "Use your connected apps". 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. Think hard before granting Use your connected apps, which can also delete in 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.

## Elaichi vs Zapier MCP vs Composio for Google Forms

All three can connect Google Forms to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Google Forms tools | Allow or restrict single Google Forms tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Google Forms call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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, Microsoft Copilot, 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 role 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 restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says. 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, Microsoft Copilot and every other client at the same time.

### Does the Google Forms MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Google Forms?

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.

### How is Elaichi different from Composio for Google Forms?

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.

## 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).
