Google Forms integration for AI agents.
Google Forms integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Forms tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Google Forms actions, managed and audited.
Your user connects Google Forms once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Google Forms access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Google Forms tools.
10 tools are generated from the published Google Forms catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 10 tools. All published catalog entries are included in this page's server-rendered HTML.
- Forms Forms BatchUpdate
- Change the form with a batch of updates.
- forms
- Forms Forms Create
- Create a new form using the title given in the provided form message in the request. *Important:* Only the form.info.title and form.info.document_title fields are copied to the new form. All other fields including the form description, items and settings are disallowed. To create a new form and add items, you must first call forms.create to create an empty form with a title and (optional) document title, and then call forms.update to add the items.
- forms
- Forms Forms Get
- Get a form.
- forms
- Forms Forms Responses Get
- Get one response from the form.
- forms
- Forms Forms Responses List
- List a form's responses.
- forms
- Forms Forms SetPublishSettings
- Updates the publish settings of a form. Legacy forms aren't supported because they don't have the `publish_settings` field.
- forms
- Forms Forms Watches Create
- Create a new watch. If a watch ID is provided, it must be unused. For each invoking project, the per form limit is one watch per Watch.EventType. A watch expires seven days after it is created (see Watch.expire_time).
- forms
- Forms Forms Watches Delete
- Delete a watch.
- forms
- Forms Forms Watches List
- Return a list of the watches owned by the invoking project. The maximum number of watches is two: For each invoker, the limit is one for each event type per form.
- forms
- Forms Forms Watches Renew
- Renew an existing watch for seven days. The state of the watch after renewal is `ACTIVE`, and the `expire_time` is seven days from the renewal. Renewing a watch in an error state (e.g. `SUSPENDED`) succeeds if the error is no longer present, but fail otherwise. After a watch has expired, RenewWatch returns `NOT_FOUND`.
- forms
Google Forms integration, answered
- How do AI agents use Google Forms through Open Connector?
- Your user connects Google Forms once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Forms tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Google Forms MCP server?
- Yes. Open Connector can serve Google Forms as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Forms actions with credentials injected server-side.
- Where do Google Forms credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Google Forms — keep the keys.
Open source, self-hostable, with Google Forms credentials that never leave your infrastructure. Run it from source today.