Getform for AI agents
Getform is a form backend that collects submissions from any HTML form without a server. Developers use it to handle contact and signup forms on static sites. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Getform.
Pull a form submission
Fetch a specific contact-form submission's fields to route it into a support ticket or CRM record.
Submit a form on a user's behalf
Post a completed form payload to a Getform endpoint when a user asks an agent to finish a signup.
Review a submission before acting
Read a new submission's contents first so a destructive follow-up action is not taken on bad data.
2 Getform actions, graded by risk.
Every Getform action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- getform.get_form_submit_formSubmit Form
- getform.get_form_get_submissionGet Form Submission
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Getform in three steps.
- 01Your users connect GetformThey add their Getform api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Getform through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('getform', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Getform connects.
Users add their Getform api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Getform connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Getform from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Getform and Arc0, answered.
Can I use Getform with Claude, ChatGPT or Cursor?
Yes. Connect Getform to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Getform actions you allow.
How do users connect Getform?
Users add their Getform api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Getform actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Getform?
Yes. Allow read actions and deny writes in the Getform policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Getform too?
Yes. The same Getform connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Getform into your agent.
Your users connect Getform once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan