Google Forms MCP vs dForms: There Is No Official Server, So What Should Your Agent Use? (2026)
Google Forms MCP vs dForms: Google ships no official Forms server. What community servers need, what they do, and what your agent gets.
Josue HernandezAI Specialist
If you searched for a Google Forms MCP, you probably want one thing: ask Claude for a form and get a real Google Form back. The catch is that Google does not publish one. Google ships official MCP servers for Gmail, Drive, Docs, Sheets and more, but Forms is not on the list. So every Google Forms MCP you will find today is a community project or a third party connector.
This guide explains what that means in practice. First, what Google does publish. Then, how the community servers work and what they need from you. Finally, how they compare with the dForms MCP, a form builder made for agents. Every claim about Google comes from its own pages, linked, and checked on November 18, 2026.
Is there an official Google Forms MCP?
No, not as of November 18, 2026. Google's guide to configure the Google Workspace MCP servers lists one server per product. The list covers Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, the People API, Classroom and Universal Search. Google Forms does not appear.
Those official servers are also a developer preview. According to the same guide, you need to join the Google Workspace Developer Preview Program. You also need a Google Cloud project and an OAuth client marked for use by an AI agent.
So if you want your agent to build Google Forms today, you have three roads:
- A community Google Forms server that you run yourself.
- A hosted connector from a third party that lists Google Forms.
- The Google Forms API directly, from your own code.
How community Google Forms servers work
Several open source servers wrap the Google Forms API. They all follow the same pattern: you create the Google credentials, and the server uses them to call the API on your behalf.
What setup looks like
Take matteoantoci/google-forms-mcp on GitHub as an example. Its README lists four steps:
- Create a project in the Google Cloud Console and enable the Google Forms API.
- Create an OAuth 2.0 client ID of type Desktop app.
- Run its script to get a refresh token with your client ID and secret.
- Add the client ID, secret and refresh token to the Claude desktop config, then restart Claude.
That is a reasonable path for a developer. For a recruiter or a sales lead, however, a Google Cloud project and a refresh token are a real barrier. Also, the refresh token in your config file can act on your Google account, so it needs the same care as a password.
What the tools can do
That same server exposes five tools: create a form, add a text question, add a multiple choice question, get a form, and get its responses. Other community servers expose more, so read each README before you pick one.
In other words, a typical Google Forms MCP gives your agent the basics: create a form, add questions, read the answers. Anything beyond the tool list, such as quiz points or section jumps, depends on whether that server wraps the part of the API you need.
What about hosted connectors?
Some automation platforms list Google Forms among their MCP apps. For example, the Zapier page for Google Forms shows two triggers, new form response and new or updated form response. Those are useful to react to answers, but they are not tools to build a form.
Google Forms MCP vs dForms MCP side by side
dForms is the form builder for AI agents: the one your agent actually wants to use. Its connector lives at https://mcp.dforms.ai/mcp, and the tools are documented in the dForms connector docs. Here is the comparison, with the Google column based on the pages linked above.
| What your agent needs | Community Google Forms MCP | dForms MCP |
|---|---|---|
| Who publishes it | A community maintainer, not Google | dForms, the product team |
| Connect from Claude | Local server, Google Cloud project, OAuth client, refresh token | Custom connector URL, sign in with your account |
| Create a form | Yes, through the tool list | From a plain description, as a draft |
| Publish and undo a publish | Depends on the server | Publish, and go back to the version that was live before |
| Score each answer | Depends on the server | Points per answer option, score on every response |
| Read responses | Yes, raw responses | List, filter by score, read one, CSV |
| Send leads on | Not in most tool lists | Webhooks, HubSpot, calendar step |
| Price | Google Forms is free | Free, responses not counted or billed |
| Run it yourself | The server runs on your machine | MIT license, self-host the whole product |
The short version: a Google Forms MCP is the right tool when the form must live in Google Forms. However, dForms is built around the full loop your agent needs for intake, from the form to the scored lead.
Build a scored form with the dForms MCP in Claude
Connecting takes about a minute, with no Google Cloud project and no keys to store.
- Open dForms on the web once, at app.dforms.ai, with the account you will connect.
- In Claude, click + in the chat box, then Connectors, Add connector, Add custom connector.
- Name it
dForms, pastehttps://mcp.dforms.ai/mcpand click Add. - Enter your email and the 6 digit code dForms sends you.
Then paste this prompt and change the details:
Create a form in dForms called "Event registration and lead score".
Questions: name, work email, company, role (founder / marketing / sales / other),
company size (1 to 10 / 11 to 50 / 51 to 200 / 200+),
and what brings them (looking for a tool / just learning / partner).
Points: company size 51 to 200 = 10, 11 to 50 = 6, others = 2.
Looking for a tool = 10, partner = 5, just learning = 0.
Show the booking step only when the total is 70% or more.
Send every response to HubSpot. Leave it as a draft and give me the preview link.
Your agent builds the questions, the points and the logic, then returns the draft link. When you say "publish it", the connector asks for your yes first, because publish, revert and delete are marked as destructive. After that, each response arrives with its score. Ask "list today's responses at 70% or more, sorted by score" and your agent reads them back.
Running a script or a server side agent instead? Use an API key from the Developers page. Keys allow 120 calls a minute, with no per key scopes and no approval step, so an agent with a key can publish directly. If you want to review first, ask it to keep forms in draft.
Related guides
- Every connector step, for Claude Code, Cursor and ChatGPT too: create a form with Claude
- How the points work: build a form with scoring
- Other MCP servers compared: Typeform MCP vs dForms and Tally MCP vs dForms
- What Claude can do with forms in general: Claude forms
- Leaving Google Forms altogether: Google Forms alternative
When Google Forms is the better choice
A Google Forms MCP is the better pick in a few clear cases, and it is worth being honest about them.
- Your organization runs on Google Workspace and wants every form inside it, next to Sheets and Drive.
- You are making school quizzes. Google Forms has quizzes with an answer key and points per question, documented in Google's help on creating and grading quizzes.
- You are a developer who is happy to own a Google Cloud project, an OAuth client and a refresh token, and to pick a maintained server.
- You only need a few simple forms, with no scoring, routing or follow up.
On the other hand, pick dForms if your agent is the main user and the job is lead or candidate intake. You connect with a URL instead of a Google Cloud project. Your agent scores every answer, and hot leads go straight to HubSpot, a webhook or a calendar step. And because Google may still ship an official Forms server, check Google's guide again before you commit to a community server for the long term.
If you want to try the agent side first, start at dForms and ask your agent for one form.
Frequently asked questions
Does Google have an official Forms MCP server?
No. As of November 18, 2026, Google's Workspace MCP guide lists official servers for Gmail, Drive, Docs, Sheets and six more products. Google Forms is not one of them. Every Google Forms MCP today comes from the community or a third party.
How do I connect a Google Forms server to Claude?
With a community server, you usually create a Google Cloud project and enable the Forms API. Then you create an OAuth client, generate a refresh token and add them to Claude's config. Each server's README has its exact steps.
Is a community Forms server safe to use?
It can be, but it runs with your Google credentials. Read the code or pick a widely used server, keep the refresh token private, and limit the account it can reach.
Can my agent score Google Forms answers?
Google Forms quizzes support points per question. Whether your agent can set them depends on the tools your Google Forms MCP exposes. In dForms, points per answer option are part of the connector, so every response arrives with its score.
Is dForms free?
Yes. dForms is free, responses are not counted or billed, and it is open source under the MIT license, so you can self-host it.
Do Typeform, Tally or Jotform have MCP servers?
Yes. Typeform, Tally and Jotform ship MCP servers. dForms differs in what your agent can finish: scoring per answer, routing to a calendar or CRM, revert after publish and free unlimited responses.