Leverly for AI agents
Leverly is a lead response automation tool that connects sales reps to inbound leads quickly through automated call workflows and scheduled reattempts. 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 Leverly.
Log a new outbound call
Create a call record when a rep reaches out to a newly assigned lead.
Check pending call reattempts
List reattempts still scheduled for a lead to see if follow-up is on track.
Approve before stopping reattempts
Require approval before stopping reattempts on a lead, since it ends automated follow-up.
3 Leverly actions, graded by risk.
Every Leverly 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.
- leverly.list_reattemptsList Reattempts
write
2Create and change things. Allow, or ask the user first.
- leverly.create_callCreate Call
- leverly.stop_reattemptsStop Leverly Reattempts
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Leverly in three steps.
- 01Your users connect LeverlyThey add their Leverly api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Call” can wait for the user to approve.
- 03Any agent can actYour agent calls Leverly through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('leverly', { read: 'allow', write: 'ask', // create_call destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Leverly connects.
Users add their Leverly 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 Leverly 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 Leverly from any agent.
Leverly and Arc0, answered.
Can I use Leverly with Claude, ChatGPT or Cursor?
Yes. Connect Leverly 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 Leverly actions you allow.
How do users connect Leverly?
Users add their Leverly 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 Leverly actions can my agent take?
3 in total: 1 read, 2 write and 0 destructive, such as “create Call”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Leverly?
Yes. Allow read actions and deny writes in the Leverly policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Leverly too?
Yes. The same Leverly connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Leverly into your agent.
Your users connect Leverly once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan