How to integrate Dialmycalls MCP with Codex

GET STARTED FOR FREE
Framework Integration Gradient
Dialmycalls Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Dialmycalls 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 Dialmycalls 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 Dialmycalls MCP server, and what's possible with it?

The Dialmycalls MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dialmycalls account. It provides structured and secure access to your mass notification system, allowing your agent to manage contacts, groups, and broadcast voice or text messages—all on your behalf.

  • Contact and group management: Effortlessly add, update, or remove individual contacts and organize recipients into groups for targeted messaging.
  • Account and sub-account administration: View your main account details, manage access (sub) accounts, and streamline team communication permissions.
  • Broadcast preparation: Set up caller IDs, upload or delete recordings, and get everything ready for your next mass notification campaign.
  • Data cleanup and maintenance: Easily delete old contacts, groups, caller IDs, or recordings to keep your Dialmycalls account organized and up to date.

Supported Tools & Triggers

Tools
Add Access AccountTool to add a new access (sub) account.
Add ContactTool to add a contact to your contact list.
Add GroupTool to add a new contact group.
Delete Access AccountTool to delete an access (sub) account by id.
Delete Caller IDTool to delete a caller id.
Delete ContactTool to delete a contact by id.
Delete GroupTool to delete a contact group by id.
Delete RecordingTool to delete a recording by id.
Get Access AccountTool to retrieve an access (sub) account by id.
Get AccountTool to retrieve your main account details.
Get Caller IDTool to retrieve a caller id by id.
Get ContactTool to retrieve a contact by its unique id.
Get GroupTool to retrieve a contact group by id.
Get RecordingTool to retrieve a recording by id.
List Access AccountsTool to list all access (sub) accounts.
List Caller IDsTool to list all caller ids on the account.
List CallsTool to list all call broadcasts on the account.
List ContactsTool to list all contacts in your contact list.
List Contacts in GroupTool to list contacts by contact group id.
List Do Not ContactsTool to list all do not contact entries.
List GroupsTool to list all contact groups.
List RecordingsTool to list all recordings.
List Text BroadcastsTool to list all outgoing text broadcasts.
List Vanity NumbersTool to list all vanity numbers.
Update Access AccountTool to update an existing access (sub) account by id.
Update Caller IDTool to update an existing caller id by id.

Conclusion

You've successfully integrated Dialmycalls with Codex using Composio's Rube MCP server. Now you can interact with Dialmycalls 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 Dialmycalls 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 Dialmycalls operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Dialmycalls MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Dialmycalls MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Dialmycalls MCP with Claude Agent SDK

Google ADK

Google ADK

Use Dialmycalls MCP with Google ADK

LangChain

LangChain

Use Dialmycalls MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Dialmycalls MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Dialmycalls MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Dialmycalls MCP with LlamaIndex

CrewAI

CrewAI

Use Dialmycalls MCP with CrewAI

Claude Code

Claude Code

Use Dialmycalls MCP with Claude Code

FAQ

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

With a standalone Dialmycalls MCP server, the agents and LLMs can only access a fixed set of Dialmycalls tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Dialmycalls 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 Dialmycalls tools.

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

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

Book a call↗Get started for free