Flexisign for AI agents
FlexiSign is a privacy-focused e-signature tool that simplifies signing, sending, and managing documents, used by teams that want a lightweight alternative to bigger signature platforms. 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 Flexisign.
Browse available templates
List templates to find the right one before starting a new signature request.
Confirm the right template is used
Have an agent confirm the correct template is selected before a document goes out for signing.
Read-only template listing
Keep template browsing read-only, since it only surfaces options without sending a document.
1 Flexisign actions, graded by risk.
Every Flexisign 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.
- flexisign.list_templatesList Templates
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.
Flexisign in three steps.
- 01Your users connect FlexisignThey add their Flexisign 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 Flexisign through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('flexisign', { 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 Flexisign connects.
Users add their Flexisign 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 Flexisign 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 Flexisign from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Flexisign and Arc0, answered.
Can I use Flexisign with Claude, ChatGPT or Cursor?
Yes. Connect Flexisign 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 Flexisign actions you allow.
How do users connect Flexisign?
Users add their Flexisign 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 Flexisign 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 Flexisign?
Yes. Allow read actions and deny writes in the Flexisign policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Flexisign too?
Yes. The same Flexisign connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Flexisign into your agent.
Your users connect Flexisign 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