NeetoForm for AI agents
NeetoForm is an online form builder for collecting submissions and managing the team members who can view and act on responses. 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 NeetoForm.
Check a form's submissions
List submissions to a form to review new responses since the last check, a read-only lookup.
List team members with access
List the team members who can access a workspace's forms and submitted responses, a read-only check.
Approve before removing a team member
Require approval before removing a team member, since it revokes their access to submitted data.
6 NeetoForm actions, graded by risk.
Every NeetoForm action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- neetoform.list_formsList Forms
- neetoform.list_team_membersList Team Members
- neetoform.list_form_submissionsList Form Submissions
write
2Create and change things. Allow, or ask the user first.
- neetoform.update_team_memberUpdate Team Member
- neetoform.invite_team_membersInvite Team Members
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- neetoform.remove_team_memberRemove Team Member
NeetoForm in three steps.
- 01Your users connect NeetoFormThey add their NeetoForm api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “update Team Member” can wait for the user, and “remove Team Member” can be denied outright.
- 03Any agent can actYour agent calls NeetoForm through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('neetoform', { read: 'allow', write: 'ask', // update_team_member destructive: 'deny', // remove_team_member }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How NeetoForm connects.
Users add their NeetoForm 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 NeetoForm 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 NeetoForm from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
NeetoForm and Arc0, answered.
Can I use NeetoForm with Claude, ChatGPT or Cursor?
Yes. Connect NeetoForm 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 NeetoForm actions you allow.
How do users connect NeetoForm?
Users add their NeetoForm 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 NeetoForm actions can my agent take?
6 in total: 3 read, 2 write and 1 destructive, such as “update Team Member”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in NeetoForm?
Yes. Actions like “remove Team Member” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call NeetoForm too?
Yes. The same NeetoForm connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug NeetoForm into your agent.
Your users connect NeetoForm once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan