Eversign for AI agents
Eversign, now Xodo Sign, is a cloud digital signature platform for signing, sending, and managing documents online, used by teams that need a lightweight e-signature workflow. 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 Eversign.
Send a document for signature
Create a document from a template and send it to the named signers.
Check a document's audit log
Get a document's audit log to confirm who signed it and when.
Confirm before deleting a document
Require approval before deleting a document or template, since it removes the signing record.
10 Eversign actions, graded by risk.
Every Eversign action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- eversign.list_documentsList Documents
- eversign.list_templatesList Templates
- eversign.list_businessesList Businesses
- eversign.get_bulk_jobs_listGet Bulk Jobs List
- eversign.get_bulk_job_statusGet Bulk Job Status
write
4Create and change things. Allow, or ask the user first.
- eversign.create_documentCreate Document
- eversign.create_templateCreate Template
- eversign.audit_logGet Document Audit Log
- eversign.reassign_signerReassign Signer
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- eversign.delete_document_or_templateDelete Document or Template
Eversign in three steps.
- 01Your users connect EversignThey add their Eversign api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Document” can wait for the user, and “delete Document or Template” can be denied outright.
- 03Any agent can actYour agent calls Eversign through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('eversign', { read: 'allow', write: 'ask', // create_document destructive: 'deny', // delete_document_or_template }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Eversign connects.
Users add their Eversign 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 Eversign 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 Eversign from any agent.
Eversign and Arc0, answered.
Can I use Eversign with Claude, ChatGPT or Cursor?
Yes. Connect Eversign 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 Eversign actions you allow.
How do users connect Eversign?
Users add their Eversign 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 Eversign actions can my agent take?
10 in total: 5 read, 4 write and 1 destructive, such as “create Document”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Eversign?
Yes. Actions like “delete Document or Template” 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 Eversign too?
Yes. The same Eversign connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Eversign into your agent.
Your users connect Eversign once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan