Formilla for AI agents
Formilla powers live chat and marketing automation, syncing customer contact records for support and outreach teams who want chat and email working from the same data. 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 Formilla.
Update a customer's contact record
Upsert a contact's details once new information comes in from a chat conversation.
Sync a new lead from chat
Upsert a contact created from a live chat session so the record exists for follow-up.
Log contact changes for review
Record every contact upsert in the audit log so support can trace where a field value came from.
1 Formilla actions, graded by risk.
Every Formilla action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
1Create and change things. Allow, or ask the user first.
- formilla.upsert_contactUpsert Contact
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Formilla in three steps.
- 01Your users connect FormillaThey add their Formilla api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “upsert Contact” can wait for the user to approve.
- 03Any agent can actYour agent calls Formilla through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('formilla', { read: 'allow', write: 'ask', // upsert_contact destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Formilla connects.
Users add their Formilla 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 Formilla 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 Formilla from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Formilla and Arc0, answered.
Can I use Formilla with Claude, ChatGPT or Cursor?
Yes. Connect Formilla 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 Formilla actions you allow.
How do users connect Formilla?
Users add their Formilla 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 Formilla actions can my agent take?
1 in total: 0 read, 1 write and 0 destructive, such as “upsert Contact”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Formilla?
Yes. Allow read actions and deny writes in the Formilla policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Formilla too?
Yes. The same Formilla connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Formilla into your agent.
Your users connect Formilla 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