How to integrate Kadoa MCP with Codex

Kadoa logo
Codex logo
divider

Introduction

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

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

The Kadoa MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kadoa account. It provides structured and secure access to your data extraction workflows, so your agent can launch crawls, monitor sessions, retrieve extracted data, and manage workflow configurations automatically on your behalf.

  • Automated workflow monitoring and management: Ask your agent to fetch workflow configurations, enable data validation, or get the latest results from any extraction workflow you have set up.
  • Crawling session control: Have your agent check the status of crawl sessions, list all crawled pages, and pull the raw content (HTML or Markdown) from any page processed by a workflow.
  • Notification channel setup and retrieval: Direct your agent to create notification channels, list available notification event types, and fetch specific channel configurations for streamlined alerting.
  • Location and environment awareness: Let your agent retrieve all supported locations to ensure workflows run in the right environment before launching new extraction jobs.
  • Seamless data access: Instruct your agent to quickly get the most recent data output from any workflow, keeping your automations and dashboards always up to date.

Supported Tools & Triggers

Tools
Create Notification ChannelTool to create a notification channel for alerts delivery.
Enable Data ValidationTool to enable data validation on a specified workflow.
Fetch workflow configurationTool to fetch an advanced workflow’s configuration details.
Get all locationsTool to retrieve a list of all available locations.
Get Crawled Page ContentTool to retrieve content of a crawled page.
Get Crawled PagesTool to list pages crawled during a session.
Get Crawl StatusTool to fetch current status of a crawling session.
Get Notification Event TypesTool to retrieve supported notification event types.
Get Latest Workflow DataTool to retrieve the most recent data produced by a workflow.
Get Notification ChannelTool to retrieve details of a specific notification channel.
Get Notification SettingTool to retrieve a specific notification setting by its identifier.
Get validation configurationTool to retrieve the configuration settings for data validation.
Get Workflow Run HistoryTool to fetch workflow run history.
Get WorkflowsTool to retrieve all workflows.
Get Workflow Validation ResultsTool to retrieve the latest validation results for a workflow job.
List Validation RulesTool to list all data validation rules with optional pagination and filtering.
Create Advanced WorkflowTool to create an advanced workflow.
Start Crawl SessionTool to start a web crawling session.
Create Notification SettingTool to create a notification setting linking channels to events.
Post Notification TestTool to send a test notification event.
Subscribe to Webhook EventsTool to subscribe to specified webhook events.
Create WorkflowTool to create a new workflow in kadoa.
Configure Workflow MonitoringTool to configure monitoring for a workflow to detect data changes by updating workflow metadata.
Post Workflow Validation RuleTool to generate and add a new validation rule to a workflow.
Update Notification ChannelTool to update an existing notification channel.
Run Ad-hoc ExtractionTool to synchronously extract data from a URL using a given template.
Unsubscribe from Webhook EventsTool to unsubscribe from webhook event notifications by deleting a notification setting.

Conclusion

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

How to build Kadoa MCP Agent with another framework

FAQ

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

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

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

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

How to integrate Kadoa MCP with Codex