How to integrate Plivo MCP with Codex

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Plivo MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Plivo logoPlivo
Api Key

Plivo is a cloud communications platform for programmable SMS, voice, SIP, phone numbers, and verification APIs. It helps teams add reliable global messaging and calling without building telecom infrastructure.

6 Tools

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Plivo MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Plivo with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Plivo MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Plivo MCP server, and what's possible with it?

The Plivo MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Plivo account. It provides structured and secure access to your account information, communication history, usage, and owned phone numbers, so your agent can review account details, inspect calls and messages, analyze spending, and check your phone number inventory on your behalf.

  • Account details and billing status: Have your agent retrieve your account type, available credit, billing information, and timezone when you need a quick account overview.
  • Call history review: Let the agent list calls and narrow the results by time, direction, status, participants, or hangup details.
  • Message tracking: Direct your agent to review inbound and outbound messages or inspect one message for delivery, routing, timing, error, and billing details.
  • Usage and spend analysis: Instruct your agent to summarize Plivo spending and usage by hour, day, month, or year across a chosen date range.
  • Owned number inventory: Have your agent list your Plivo phone numbers and filter them by prefix, number type, service, or alias.

Conclusion

You've successfully integrated Plivo with Codex using Composio's MCP server. Now you can interact with Plivo directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Plivo operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Plivo operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities
TOOLS

Supported Tools

Every Plivo action and event your agent gets out of the box.

Get Account Details

Return billing, credit, timezone, and account-type details for the connected Plivo account.

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.

List Messages

Return one page of inbound and outbound Plivo message history, optionally filtered by time, direction, state, sender, recipient, type, or subaccount.

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.

FAQ

Frequently asked questions

With a standalone Plivo MCP server, the agents and LLMs can only access a fixed set of Plivo tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Plivo and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Plivo tools.

Yes, absolutely. You can configure which Plivo scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Plivo data and credentials are handled as safely as possible.

Start with Plivo.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Plivo tool your agent needs.Free to start.

Start building