Boloforms for AI agents
BoloForms is an e-signature and forms platform that small businesses use to send documents for signature and track which ones are still pending. 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 Boloforms.
List pending and signed documents
Read-only pull of the documents list to check which forms are still waiting on a signature.
Track document completion status
Check the documents list on a schedule so the agent can flag ones still awaiting a signer.
Surface stalled signature requests
Review the documents list for items pending too long and flag them to the user before following up.
1 Boloforms actions, graded by risk.
Every Boloforms action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- boloforms.get_documents_listGet Documents List
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.
Boloforms in three steps.
- 01Your users connect BoloformsThey add their Boloforms 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 Boloforms through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('boloforms', { 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 Boloforms connects.
Users add their Boloforms 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 Boloforms 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 Boloforms from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Boloforms and Arc0, answered.
Can I use Boloforms with Claude, ChatGPT or Cursor?
Yes. Connect Boloforms 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 Boloforms actions you allow.
How do users connect Boloforms?
Users add their Boloforms 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 Boloforms actions can my agent take?
1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Boloforms?
Yes. Allow read actions and deny writes in the Boloforms policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Boloforms too?
Yes. The same Boloforms connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Boloforms into your agent.
Your users connect Boloforms once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan