Helloleads for AI agents
HelloLeads is a simple lead management tool for small businesses to capture, track, and follow up on sales leads. Revenue teams rely on it to track customer relationships instead of scattering notes across tools. 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 Helloleads.
Create a new lead
Add a new lead's contact details and source to the pipeline right after it comes in.
List leads in a list
List all leads in a named list to prepare a follow-up call sheet for the sales team.
Check lead source performance
Review which lead list is generating the most entries this week, read-only.
3 Helloleads actions, graded by risk.
Every Helloleads 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.
- helloleads.list_leadsList Leads
- helloleads.list_listsList Lead Lists
write
1Create and change things. Allow, or ask the user first.
- helloleads.create_leadCreate Lead
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Helloleads in three steps.
- 01Your users connect HelloleadsThey add their Helloleads api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Lead” can wait for the user to approve.
- 03Any agent can actYour agent calls Helloleads through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('helloleads', { read: 'allow', write: 'ask', // create_lead destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Helloleads connects.
Users add their Helloleads 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 Helloleads 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 Helloleads from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Helloleads and Arc0, answered.
Can I use Helloleads with Claude, ChatGPT or Cursor?
Yes. Connect Helloleads 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 Helloleads actions you allow.
How do users connect Helloleads?
Users add their Helloleads 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 Helloleads actions can my agent take?
3 in total: 2 read, 1 write and 0 destructive, such as “create Lead”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Helloleads?
Yes. Allow read actions and deny writes in the Helloleads policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Helloleads too?
Yes. The same Helloleads connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Helloleads into your agent.
Your users connect Helloleads 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