MCP connectorsGoogle Forms

Google Forms MCP: connect Google Forms to Claude and ChatGPT

Ask Claude or ChatGPT what customers wrote in the post-event survey, how many people signed up for Thursday’s training or which answers in the supplier questionnaire mention delivery times. The AI finds the form in Google Forms, reads the responses and gives you the link.

With Deployed OS everyone connects their own Google account. The AI reads only the forms that person can already open, and the one thing it writes is a new form in their own Drive, unpublished, when they ask for it.

3 read actions · 1 write action · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Google Forms in Claude and ChatGPT

Marketing

Event feedback without the spreadsheet

Summarise 200 answers from the post-webinar survey by theme and pull out the quotes worth sharing, with each answer under its question.
HR

Pulse surveys and sign-ups in plain words

What the team answered in the quarterly pulse survey, or who signed up for the kick-off and who needs a special diet. Only for the people who can open that form.
Customer success

Read the intake form before the call

A new customer has filled in the onboarding form. Get their answers summarised, with the link, before the kick-off meeting.
Operations

Draft the next form in one sentence

Describe the survey you need and the AI creates it with the questions you confirmed, unpublished in your own Drive. You check it and publish it yourself.
Examples

Ask it like this

  • “Summarise the responses to our Customer event survey from the last 30 days. What did people like least?”

  • “How many have signed up for the kick-off in Gothenburg, and who needs a special diet?”

  • “Find the answers in the Supplier questionnaire that mention delivery times.”

  • “What does the Onboarding form ask, and which questions are required?”

  • “Create a form called Workshop feedback with a 1 to 5 rating, a multiple choice question about the pace and a free-text question for comments.”

  • “Which forms with 2026 in the name can I open, and who owns them?”

The connector

What the Google Forms MCP connector does today

  • Readsforms_search_forms

    Find the Google Forms you can open by words in their names, with name, owner, last change and link for each.

  • Readsforms_get_form

    Read one form you can open: its title, description and questions with their types and options, the link to answer it and its linked response sheet.

  • Readsforms_list_responses

    List the responses to a form you can open, newest first as Google sends them, each answer under its question, page by page, or only those after a given date and time.

  • Writesforms_create_form

    Create a form in your own Drive with a title, an optional description and optional questions, once you have confirmed the questions. It is not published and is shared with nobody, and the company guardrails apply.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Reads, plus new forms
The connector finds forms by name and reads their questions and responses. With Edit access it can create a new form in your own Drive. It cannot change, publish, share or delete an existing form or response.
Each person’s own rights
Everyone connects their own Google account, so the AI finds the forms that person can open and nothing else. A survey shared only with HR stays with HR.
New forms only with Edit access
Admins choose which groups get Google Forms, and only groups with Edit access can create forms. A new form is unpublished and shared with nobody until its owner publishes it in Google Forms.
Every call logged
Who asked, which form was read, when. Deployed OS shows reads and writes per connector and per person, and the log can be exported.
Setup

Set up the Google Forms connector in three steps

01
An admin creates a project in your company’s Google Cloud, sets up an internal OAuth app and turns on the Forms API, with read access to forms and responses and the right to create forms. The same Google app serves Drive, Gmail, Calendar and the other Google connectors, and your company owns it.
02
The admin adds the app’s Client ID and Client secret to Deployed OS and chooses which groups get Google Forms, and which of them may create forms.
03
Each person connects their own Google work account. From then on they just ask, in Claude, ChatGPT or Copilot.
Questions

Google Forms MCP: common questions

Google’s own remote MCP servers, in developer preview, cover Gmail, Drive, Docs, Sheets, Slides, Calendar and Chat. Deployed OS gives your whole company one connector for Google Forms next to your other tools, with each person’s own login, access per group and a log of every call.

No. It reads forms and responses, and with Edit access it can create a new form in your own Drive once you have confirmed the questions. That form is unpublished and shared with nobody, so nobody can answer it until you publish it in Google Forms. Nothing existing is changed, published, shared or deleted. If you want it to do more, we can extend it for you.

Your admin sets up Google in Deployed OS once. You add your company’s Deployed OS connection in Claude, connect your own Google account and start asking. The same connection works in ChatGPT and Copilot.

Only if they can in Google Forms. The AI uses each person’s own Google account, so a form shared with one team stays with that team. A respondent’s email address only comes with a response when Google includes it.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Forms and responses are fetched from Google when someone asks for them.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.

Poyan Karimi
You’ll hear from Poyan Karimi
Co-founder · Deployed AI