Quo for AI agents
Quo, formerly OpenPhone, is a business phone platform for managing calls, messages, and contacts across a team. Sales and support teams use it as a shared business phone line. 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 Quo.
Send a text message
Send a message to a contact from a shared business number and log the conversation.
Check call recordings read-only
List call recordings for a number to review a past customer conversation.
Delete a contact with approval
Remove a contact from the directory only after confirming it is a duplicate.
36 Quo actions, graded by risk.
Every Quo action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
20Look things up. Allowed by default.
- quo.get_callGet Call
- quo.get_taskGet Task
- quo.get_userGet User
- quo.list_callsList Calls
- quo.list_tasksList Tasks
- quo.list_usersList Users
- quo.get_contactGet Contact
- quo.get_messageGet Message
- quo.get_webhookGet Webhook
- quo.list_contactsList Contacts
- quo.list_messagesList Messages
- quo.list_webhooksList Webhooks
- quo.get_phone_numberGet Phone Number
- quo.get_call_voicemailGet Call Voicemail
- quo.list_conversationsList Conversations
- quo.list_phone_numbersList Phone Numbers
write
13Create and change things. Allow, or ask the user first.
- quo.create_taskCreate Task
- quo.update_taskUpdate Task
- quo.send_messageSend Message
- quo.create_contactCreate Contact
- quo.create_webhookCreate Webhook
- quo.update_contactUpdate Contact
- quo.update_webhookUpdate Webhook
- quo.send_message_and_mark_conversation_doneSend Message and Mark Conversation Done
- quo.set_task_assigneeSet Task Assignee
- quo.set_task_due_dateSet Task Due Date
- quo.set_task_completionSet Task Completion
- quo.set_conversation_statusSet Conversation Status
- quo.set_task_conversation_linkSet Task Conversation Link
destructive
3Delete, cancel or archive. Ask first, or deny outright.
- quo.delete_taskDelete Task
- quo.delete_contactDelete Contact
- quo.delete_webhookDelete Webhook
Quo in three steps.
- 01Your users connect QuoThey add their Quo api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Task” can wait for the user, and “delete Task” can be denied outright.
- 03Any agent can actYour agent calls Quo through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('quo', { read: 'allow', write: 'ask', // create_task destructive: 'deny', // delete_task }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Quo connects.
Users add their Quo 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 Quo 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 Quo from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Quo and Arc0, answered.
Can I use Quo with Claude, ChatGPT or Cursor?
Yes. Connect Quo 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 Quo actions you allow.
How do users connect Quo?
Users add their Quo 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 Quo actions can my agent take?
36 in total: 20 read, 13 write and 3 destructive, such as “create Task”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Quo?
Yes. Actions like “delete Task” 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 Quo too?
Yes. The same Quo connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Quo into your agent.
Your users connect Quo once, under your brand. Your agent gets 36 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan