How to integrate Mailersend MCP with Codex

Framework Integration Gradient
Mailersend Logo
Codex Logo
divider

Introduction

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

The Mailersend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mailersend account. It provides structured and secure access to your transactional email infrastructure, so your agent can perform actions like sending emails, managing domains, configuring webhooks, and monitoring API usage on your behalf.

  • Seamless domain management: Register new sending domains, verify their status, and retrieve detailed configuration information to ensure reliable email delivery.
  • Automated email and SMTP user setup: Quickly create SMTP users and API tokens as needed for secure and scalable application integration.
  • Webhook configuration and event tracking: Set up and delete webhooks to monitor real-time email events such as sent, delivered, or opened messages, enabling proactive workflows and notifications.
  • Recipient and quota insights: List recipients for specific domains and monitor your API usage to stay within account limits and optimize deliverability.
  • Centralized resource discovery: Retrieve general API resources and overview endpoints to streamline Mailersend integration and administration directly from your agent.

Supported Tools & Triggers

Tools
Create Sending DomainTool to add a new sending domain to mailersend.
Create SMTP UserTool to create a new smtp user.
Create API TokenTool to create a new api token.
Create WebhookTool to create a new webhook for a mailersend domain.
Delete WebhookTool to delete an existing webhook.
Get API QuotaTool to retrieve current api usage quota.
Get DomainTool to fetch information for a specific sending domain.
List Domain RecipientsTool to list recipients for a domain.
Get sending domainsTool to retrieve a list of sending domains.
Get general API resourcesTool to retrieve general api resources and information.
List Sender IdentitiesTool to list sender identities.
Get sent messagesTool to retrieve a paginated list of sent messages.
Get email recipientsTool to retrieve a list of email recipients.
Get SMS ActivityTool to retrieve sms activity logs.
Get SMS InboundsTool to retrieve inbound sms messages.
List SMS MessagesTool to list sent sms messages with optional filters.
Get SMS NumbersTool to retrieve a paginated list of sms phone numbers.
Get SMS recipientsTool to retrieve a list of sms recipients.
Get SMTP usersTool to retrieve a list of smtp users.
Get email templatesTool to retrieve a list of email templates.
Get API TokensTool to retrieve a list of api tokens.
Get usersTool to retrieve a list of users associated with your account.
List webhooksTool to retrieve a list of webhooks.

Conclusion

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

How to build Mailersend MCP Agent with another framework

FAQ

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

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

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

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