Claude Code

How to use Google Forms with Claude Code

You want Google Forms inside Claude Code so it can summarize survey results, build a recurring intake form, monitor new form responses, and audit and update a form — without you copy-pasting between tabs. Here is the whole setup, once.

Create your Google Forms gateway

The gateway is the thing Claude Code connects to, and it is where you decide which Google Forms tools an agent may use. You create it once and every client reuses it.

  1. Create an Arcade account

    Sign up and open the dashboard. The free tier is enough to follow this through.

  2. Create an MCP Gateway and select your Google Forms tools

    In the dashboard, create a gateway and pick the Google Forms tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.

  3. Copy your gateway URL

    Every client below needs it.

    https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>

Connect the gateway to Claude Code

  1. Add the gateway as a remote HTTP MCP server

    claude mcp add --transport http arcade "<YOUR_ARCADE_GATEWAY_URL>"

  2. Verify it was added

    claude mcp get arcade
    claude mcp list

  3. Sign in to Arcade

    Start Claude Code, run /mcp, pick arcade and choose Authenticate. Approve the Arcade sign-in that opens in your browser.

  4. Try it out

    Open Claude Code in your project and ask it to use one of your Google Forms tools. The first time it calls a Google Forms tool, Arcade replies with an authorization link. Open it, sign in to Google Forms and approve access, then ask again. You do this once per account.

Get started with these Google Forms prompts

Claude Code can now act on your Google Forms account. Copy a prompt and paste it in.

summarize survey results

Find the most recent customer feedback form, summarize its questions and response counts, and report the main patterns in the text answers. Include the form name, response count, and any questions with unusually low participation.

build a recurring intake form

Create a Google Form for collecting weekly project updates with fields for project name, owner, status, blockers, and next steps. Return the form URL and IDs, and leave it unpublished until I approve the questions.

monitor new form responses

Find the team incident-report form and set up notifications for new responses. Tell me which form you watched, where notifications are sent, and when the watch needs to be renewed.

audit and update a form

Find the onboarding survey in my shared forms, show me its current questions and settings, then propose changes to collect email addresses and add a question about the first-week experience. Do not apply any changes until I approve them.

Limit agents to reading forms and responses, or require approval before they change settings, publish a form, accept responses, or move one to trash. Pair it with Contextual Access policies so agents can inspect responses without being allowed to publish, change settings, or trash a form.

Ready to actually ship your agent?

Free to start. Ready for enterprise when you are.