Plivo for AI agents
Plivo provides programmable voice, messaging, and phone number APIs for building communications into applications. Developers use it to send SMS and manage calls at scale. 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 Plivo.
Check message delivery status
Look up a sent message's status read-only to confirm it reached the recipient.
Check account usage summary
Pull usage summary data to track messaging and call volume against a monthly limit.
List owned phone numbers read-only
Check which numbers are provisioned on the account before assigning one to a new campaign.
6 Plivo actions, graded by risk.
Every Plivo action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- plivo.list_callsList Calls
- plivo.get_messageGet Message
- plivo.list_messagesList Messages
- plivo.get_usage_summaryGet Usage Summary
- plivo.list_owned_numbersList Owned Numbers
- plivo.get_account_detailsGet Account Details
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.
Plivo in three steps.
- 01Your users connect PlivoThey add their Plivo 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 Plivo through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('plivo', { 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 Plivo connects.
Users add their Plivo 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 Plivo 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 Plivo from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Plivo and Arc0, answered.
Can I use Plivo with Claude, ChatGPT or Cursor?
Yes. Connect Plivo 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 Plivo actions you allow.
How do users connect Plivo?
Users add their Plivo 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 Plivo actions can my agent take?
6 in total: 6 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Plivo?
Yes. Allow read actions and deny writes in the Plivo policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Plivo too?
Yes. The same Plivo connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Plivo into your agent.
Your users connect Plivo once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan