Leadoku for AI agents
Leadoku is a lead management tool that helps sales teams track and organize prospects through their pipeline from first contact to close. 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 Leadoku.
Check for new connections
Pull newly formed connections to spot fresh leads worth a follow-up, read-only.
Review recent lead activity
Read the latest connection data to prioritize which leads a rep should contact first.
Flag a lead for outreach
Surface a new connection to a sales channel so a rep can start a conversation.
1 Leadoku actions, graded by risk.
Every Leadoku 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.
- leadoku.get_new_connectionsGet New Connections
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.
Leadoku in three steps.
- 01Your users connect LeadokuThey add their Leadoku 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 Leadoku through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('leadoku', { 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 Leadoku connects.
Users add their Leadoku 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 Leadoku 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 Leadoku from any agent.
Leadoku and Arc0, answered.
Can I use Leadoku with Claude, ChatGPT or Cursor?
Yes. Connect Leadoku 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 Leadoku actions you allow.
How do users connect Leadoku?
Users add their Leadoku 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 Leadoku 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 Leadoku?
Yes. Allow read actions and deny writes in the Leadoku policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Leadoku too?
Yes. The same Leadoku connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Leadoku into your agent.
Your users connect Leadoku 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