How to integrate Sendspark MCP with Codex

Sendspark logo
Codex logo
divider

Introduction

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

Also integrate Sendspark 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 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 Sendspark 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 connect.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 Sendspark MCP server, and what's possible with it?

The Sendspark MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Sendspark account. It provides structured and secure access to your video campaigns and prospect data, so your agent can create campaigns, manage prospects, audit webhooks, and fetch campaign analytics on your behalf.

  • Dynamic campaign creation and management: Instantly launch new dynamic video campaigns or fetch details of existing campaigns in your workspace without manual setup.
  • Prospect automation at scale: Add individual or multiple prospects to video campaigns, retrieve their details by email, and streamline personalized outreach in seconds.
  • Webhook auditing and management: List all configured webhooks or remove outdated ones to keep your integrations secure and up-to-date.
  • Campaign analytics and tracking: Retrieve data and performance metrics for your campaigns and prospects to monitor engagement and optimize results.
  • API health monitoring: Check Sendspark API health status before making calls, ensuring your automations always run smoothly.

Supported Tools & Triggers

Tools
Add Multiple Prospects to Dynamic CampaignTool to add multiple prospects to a dynamic campaign in bulk.
Add Prospect to Dynamic Video CampaignTool to add a prospect to a dynamic video campaign.
API Health StatusTool to check the health status of the sendspark api.
Create Dynamic Video CampaignTool to create a dynamic video campaign.
Delete WebhookTool to delete a specific webhook by its id.
Get Campaign Prospect Data By EmailTool to retrieve prospect data by email within a dynamic campaign.
Get Dynamic Campaign by IDTool to retrieve details of a specific dynamic video campaign.
Get Workspace Prospect Data by EmailTool to retrieve prospect data by email in a dynamic campaign.
List Dynamic Video CampaignsTool to list all dynamic video campaigns in a workspace.
List WebhooksTool to list all configured webhooks.

Conclusion

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

How to build Sendspark MCP Agent with another framework

FAQ

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

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

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

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