How to use Google Forms with VS Code
You want Google Forms inside VS 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 VS 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.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
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.
-
Copy your gateway URL
Every client below needs it.
Connect the gateway to VS Code
-
Add the server
VS Code 1.107.0 or higher. Command Palette → MCP: Add Server… → choose HTTP, paste your gateway URL, and name it something like mcp-arcade.
-
Start it and sign in to Arcade
Click Start next to the server in mcp.json or under Extensions → MCP Servers - Installed, then approve the Arcade sign-in and consent screens.
-
Try it out
Open the chat pane, switch to Agent mode, 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
VS 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.