Plivo
Plivo provides programmable voice, messaging, phone number, SIP, verification, and communications APIs.
Verdict
Common use cases
- Investigate SMS delivery failures in real time
- Audit monthly voice and messaging spend
- Confirm phone number inventory before campaigns
- Trace call routing for support escalations
- Export message logs for compliance reviews
Integration
- Vendor
- Plivo
- Category
- communication
- Auth
- API_KEY
- Tools
- 6
- Composio slug
plivo
Tools
- Get Account Details
Return billing, credit, timezone, and account-type details for the connected Plivo account. Use this to inspect account status and configuration before querying communication resources.
- Get Message
Retrieve one existing Plivo message by its message UUID, including delivery, routing, timing, error, and billing details when available.
- Get Usage Summary
Return one page of Plivo spend and usage grouped by hour, day, month, or year for a required date range, with optional usage filters.
- List Calls
Return one page of Plivo call history, optionally filtered by time, direction, status, participants, hangup details, parent call, or subaccount. This does not initiate or modify calls.
- List Messages
Return one page of inbound and outbound Plivo message history, optionally filtered by time, direction, state, sender, recipient, type, or subaccount. This reads existing message records and does not send a message.
- List Owned Numbers
Return one page of phone numbers currently owned by the connected Plivo account, optionally filtered by prefix, type, service, alias, or subaccount.
Setup
Setup guide
- 1Open any Switchy Project, click the MCP panel, and search for Plivo. Click Connect and you'll see a prompt for your Plivo Auth ID and Auth Token. Log into your Plivo console, navigate to Account Settings, and copy both credentials from the API Credentials section. Paste them into Switchy and click Authorize. Switchy confirms the connection by fetching your account details. To test, open a chat in the Project and type '@Plivo list the last five outbound messages'. The MCP returns a table of recent SMS records with timestamps and delivery states. If you see an auth error, double-check that the token matches the Auth ID and that your Plivo account is active.
What teammates see: by default, memories from Plivo are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Delivery Status
@Plivo get message details for UUID a1b2c3d4-5678-90ef-ghij-klmnopqrstuv and show me the delivery state, error code if any, and final carrier response.
Review Recent Calls
@Plivo list the last 20 inbound calls, include caller number, duration, hangup cause, and timestamp, then summarize any calls that ended in error.
Audit This Month's Spend
@Plivo get usage summary for the current month grouped by day, then calculate total spend and highlight any days with unusually high costs.
Inventory Active Numbers
@Plivo list all owned phone numbers, show the number, type, and alias for each, then count how many are toll-free versus local.
Trace Outbound Messages
@Plivo list outbound messages sent to +14155551234 in the last seven days, include message body, state, and any error details.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@plivo show me all inbound messages from the last 24 hours that failed delivery
Found 3 failed inbound messages in the last 24 hours: 1. From +14155551234 at 2:47 PM – Status: failed, Error: Invalid destination number 2. From +16505559876 at 11:22 AM – Status: failed, Error: Carrier rejection 3. From +12125558901 at 9:03 AM – Status: failed, Error: Number not in service All messages were attempting delivery to your number +18885552000. Total cost incurred: $0.03. This is an illustrative example showing how Plivo surfaces delivery failures with carrier-level error codes.
This example demonstrates Plivo's message-history filtering by time window and delivery state. Requires read scope on messaging resources. The MCP returns one page at a time (default 20 records), so high-volume accounts may need follow-up prompts to paginate through results. Error codes vary by carrier and are passed through from upstream providers.
@plivo what phone numbers do we own that support MMS, and what's our current account credit balance?
Your account has 4 MMS-capable numbers: • +18885551000 (US, California) • +18885552000 (US, New York) • +14155553000 (US, California) • +16175554000 (US, Massachusetts) Current account balance: $127.45 USD. Account type: Postpaid with auto-recharge enabled at $50 threshold. Timezone: America/Los_Angeles. This example combines number inventory with account-status checks to give a snapshot of messaging capacity and billing health.
This example pairs two read-only tools—List Owned Numbers filtered by MMS service capability, and Get Account Details for billing state. Useful for capacity planning before launching campaigns. The MCP does not modify account settings or purchase new numbers; those actions require the Plivo web console or a separate provisioning workflow.
@plivo pull last month's outbound call usage broken down by day and calculate our average daily spend
Retrieved 30 days of outbound call usage for March 2024: Total calls: 1,847 Total cost: $412.60 Average daily spend: $13.75 Peak day: March 15 with $31.20 (142 calls) Lowest day: March 3 with $4.10 (19 calls) Most calls went to US destinations (1,604 calls, $287.50), followed by Canada (183 calls, $89.40) and UK (60 calls, $35.70). This illustrative example shows how the AI can aggregate Plivo's usage API response and derive spending trends across a billing period.
This example showcases the Get Usage Summary tool with day-level granularity, then uses the AI to calculate derived metrics Plivo doesn't compute natively. The usage API returns raw spend and volume data; the math and trend analysis happen in the AI layer. Requires a valid date range—Plivo enforces maximum query windows (typically 6 months) and may rate-limit frequent usage polling.
Use-case deep-dives
When Plivo makes sense for customer-support SMS workflows
A 6-person support team sends 200-400 SMS follow-ups per week through Plivo and wants to audit delivery failures during standup. The List Messages and Get Message tools let you filter by date range, status, and recipient to surface undelivered texts without leaving the workspace. This works well when your team already uses Plivo for outbound messaging and needs read-only visibility into delivery logs. The auth is a single API key, so setup takes under two minutes. If you're not already on Plivo or you need to send messages from the workspace itself, this MCP won't help—it reads history but doesn't initiate new SMS. For teams that run Plivo in production and want fast triage of delivery issues, this is the right call.
Use Plivo MCP when finance needs usage breakdowns
A 3-person finance team reconciles telecom spend every month and needs to pull Plivo usage by day or week to match invoices. The Get Usage Summary tool returns spend grouped by hour, day, month, or year for any date range, so you can answer "what did we spend on calls in Q1" without opening the Plivo dashboard. This is faster than exporting CSVs when you're doing ad-hoc queries or comparing multiple months. The tool returns one page at a time, so if you have thousands of line items per month, you'll hit pagination limits and need to script around it. If your monthly usage fits in a few hundred rows and you want to skip the Plivo UI for routine checks, this MCP saves 10 minutes per reconciliation cycle.
When List Owned Numbers beats the Plivo console for ops
A 4-person ops team manages 80 phone numbers across three Plivo subaccounts and needs to verify which numbers are active before a campaign launch. The List Owned Numbers tool filters by prefix, type, service, alias, or subaccount, so you can answer "show me all toll-free numbers in the East subaccount" in one query instead of clicking through the Plivo UI. This is the right move when you're doing frequent inventory checks or debugging routing issues and want to stay in the workspace. The tool pages results, so if you own 500+ numbers, you'll need multiple queries to see the full list. For teams that treat phone-number inventory as a daily ops question rather than a once-a-quarter audit, this MCP cuts lookup time in half.
Frequently asked
What does the Plivo MCP let me do in Switchy?
It gives your AI agents read-only access to your Plivo account: checking message and call history, retrieving delivery status, inspecting owned phone numbers, and pulling usage reports. Agents can answer questions like "Did that SMS deliver?" or "How many calls did we make last week?" without leaving the conversation. It does not send messages or place calls.
Do I need admin access to connect Plivo?
You need an Auth ID and Auth Token from your Plivo console, which any account member with API access can generate. Switchy does not require Plivo admin privileges, but whoever connects it should understand which subaccounts and phone numbers the token exposes, since agents will see all resources the token permits.
Can the Plivo MCP send SMS or make outbound calls?
No. This integration is read-only: it retrieves message history, call logs, account details, and usage summaries. If you need agents to send messages or initiate calls, you will need to build a custom tool that hits Plivo's Send Message or Create Call endpoints directly, outside this MCP.
Why use this instead of querying Plivo's API myself?
The MCP handles authentication, pagination, and error translation so your agents can ask natural-language questions without you writing fetch loops or parsing JSON. If you already have a Plivo integration in your app, this MCP is redundant. If you want agents to answer support or ops questions on the fly, it saves you the glue code.
Who on the team should connect the Plivo account?
Whoever owns your Plivo billing or ops dashboard. The token grants read access to all call and message history the account can see, so treat it like you would any production API credential. Once connected, any Switchy workspace member can ask agents to query Plivo data in shared threads.