Close for AI agents
Close is a sales CRM built around calling and email automation, helping small sales teams manage leads and pipeline without heavy setup. 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 Close.
Create a new lead
Create a new lead record from an inbound inquiry, ready for a rep to work.
Look up an opportunity
Look up an opportunity's stage and value before a rep's next call.
Confirm before deleting a call log
Confirm before deleting a logged call, since it removes that record from the lead's history.
14 Close actions, graded by risk.
Every Close action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- close.get_noteGet Notes
- close.get_contactGet Contact
- close.get_opportunityGet Opportunity
- close.list_activitiesList Activities
- close.list_opportunitiesList Opportunities
- close.list_custom_object_typesList Custom Object Types
- close.list_custom_activity_typesList Custom Activity Types
write
6Create and change things. Allow, or ask the user first.
- close.create_smsCreate SMS Message
- close.create_callCreate Call
- close.create_leadCreate Lead
- close.create_taskCreate Task
- close.create_emailCreate Email
- close.who_am_iWho Am I
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- close.delete_callDelete Call
Close in three steps.
- 01Your users connect CloseThey add their Close api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create SMS Message” can wait for the user, and “delete Call” can be denied outright.
- 03Any agent can actYour agent calls Close through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('close', { read: 'allow', write: 'ask', // create_sms destructive: 'deny', // delete_call }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Close connects.
Users add their Close 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 Close 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 Close from any agent.
Close and Arc0, answered.
Can I use Close with Claude, ChatGPT or Cursor?
Yes. Connect Close 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 Close actions you allow.
How do users connect Close?
Users add their Close 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 Close actions can my agent take?
14 in total: 7 read, 6 write and 1 destructive, such as “create SMS Message”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Close?
Yes. Actions like “delete Call” 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 Close too?
Yes. The same Close connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Close into your agent.
Your users connect Close once, under your brand. Your agent gets 14 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan