Connect Google Forms to Claude Code

Have Claude build forms and edit questions for you in Google Forms. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Google Forms to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Google Forms, you add a Google Forms MCP server: a small hosted service that exposes Google Forms's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Google Forms account. No API keys pasted into config files.

claude mcp add --transport http google-forms https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Google Forms once connected?

Full read-write Google Forms access lets Claude create a form from a brief, add and reorder questions, set answer types and validation, toggle quiz scoring, and update titles or descriptions. The form-building that used to mean clicking through every field by hand happens where the form already lives, with you approving the result.

Build a new form from a brief, with sections and question types set
Add, edit, or reorder questions and answer options on an existing form
Set required fields, validation rules, and answer choices
Configure quiz scoring, point values, and correct answers
Update the form title and description
Pull and summarize submitted responses for review

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Google Forms access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Google Forms API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Google Forms changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Google Forms connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Google Forms connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Google Forms account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Google Forms's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Google Forms?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Google Forms account it signs in with. Revoking access is one click in Google Forms.

More on the Google Forms connector

Google Forms connector for claude.ai Typeform + Claude Code Jotform + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us