How to integrate Whautomate MCP with Codex

Framework Integration Gradient
Whautomate Logo
Codex Logo
divider

Introduction

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

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

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 870+ 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 Whautomate MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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

The Whautomate MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Whautomate account. It provides structured and secure access to customer engagement resources, so your agent can manage contacts, schedule broadcasts, retrieve chat histories, and organize messaging segments automatically on your behalf.

  • Contact management and automation: Quickly add new contacts or retrieve lists of WhatsApp contacts to streamline customer engagement and outreach.
  • Broadcast scheduling and tracking: Instruct your agent to fetch, inspect, or get details on message broadcasts—including status tracking and filtering by date or type.
  • Chat history and message retrieval: Have your agent pull detailed chat messages for individual contacts, so you can review conversations, follow up intelligently, or analyze engagement history.
  • Segment and service organization: Effortlessly manage audience segments and services—fetching, deleting, or organizing them to keep your communication campaigns targeted and up-to-date.
  • Webhook and integration oversight: Retrieve all registered webhooks to monitor and audit external integrations, ensuring your automations stay connected and reliable.

Supported Tools & Triggers

Tools
Add ContactTool to add a new contact.
Delete SegmentTool to delete a specific segment.
Delete Service CategoryTool to delete a service category.
Get All WebhooksTool to retrieve all registered webhooks.
Get Broadcast By IDTool to retrieve a specific broadcast's details.
Get BroadcastsTool to retrieve a list of broadcasts.
Get ContactsTool to retrieve a list of contacts.
Get Messages of ContactTool to retrieve chat messages for a specific contact.
Get SegmentsTool to retrieve a list of segments.
Get Service By IdTool to retrieve details of a specific service by its unique id.
Get Service CategoriesTool to retrieve a list of service categories.
Get ServicesTool to retrieve a list of services with optional filters.
Get Staff Availability BlocksTool to retrieve a staff member's blocked time schedule over a date range.
Get Staff By IDTool to retrieve detailed information about a specific staff member.
Get StaffsTool to retrieve a list of staff members.
Update ServiceTool to update an existing whatsapp service.

Conclusion

You've successfully integrated Whautomate with Codex using Composio's Rube MCP server. Now you can interact with Whautomate 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 Whautomate operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

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

How to build Whautomate MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Whautomate MCP?

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

Can I use Tool Router MCP with Codex?

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 Whautomate tools.

Can I manage the permissions and scopes for Whautomate while using Tool Router?

Yes, absolutely. You can configure which Whautomate 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.

How safe is my data with Composio Tool Router?

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 Whautomate data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.