Espocrm for AI agents
EspoCRM is an open-source CRM that businesses self-host to manage accounts, contacts, leads, and sales pipelines, used by teams that want control over their own CRM 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 Espocrm.
Check the logged-in CRM user
Get the current app user's identity to confirm which account is acting before a sync runs.
Read CRM entity metadata
Get the instance's metadata to confirm which record types and fields are configured before mapping data.
Read-only setup checks
Keep metadata and user lookups read-only, since they only describe the CRM's configuration.
2 Espocrm actions, graded by risk.
Every Espocrm 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.
- espocrm.get_app_userGet App User
- espocrm.get_metadataGet Metadata
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.
Espocrm in three steps.
- 01Your users connect EspocrmThey add their Espocrm 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 Espocrm through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('espocrm', { 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 Espocrm connects.
Users add their Espocrm 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 Espocrm 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 Espocrm from any agent.
Espocrm and Arc0, answered.
Can I use Espocrm with Claude, ChatGPT or Cursor?
Yes. Connect Espocrm 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 Espocrm actions you allow.
How do users connect Espocrm?
Users add their Espocrm 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 Espocrm 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 Espocrm?
Yes. Allow read actions and deny writes in the Espocrm policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Espocrm too?
Yes. The same Espocrm connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Espocrm into your agent.
Your users connect Espocrm 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