How to integrate Honeyhive MCP with Codex

GET STARTED FOR FREE
Honeyhive logo
Codex logo
divider

Introduction

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

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

The Honeyhive MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Honeyhive account. It provides structured and secure access to your AI observability platform, so your agent can perform actions like managing datasets, logging model and tool events, evaluating runs, and configuring project settings on your behalf.

  • Dataset management and organization: Create, retrieve, and delete datasets for your AI projects, helping you maintain organized and up-to-date evaluation data.
  • Efficient event logging: Log batches of model or external tool events, enabling comprehensive tracking and analysis of AI system interactions in real-time.
  • Data curation and cleanup: Add new datapoints to datasets or remove specific datapoints, ensuring your evaluation data remains accurate and relevant.
  • Streamlined evaluation workflows: Mark evaluation runs as completed and fetch project configuration details, making it easy to track progress and update run statuses automatically.

Supported Tools & Triggers

Tools
Add datapoints to datasetTool to add datapoints to a dataset.
Create Batch Model EventsTool to create multiple model events in a single request.
Create Batch Tool EventsTool to log a batch of external API calls as tool events.
Create DatasetTool to create a dataset.
Create ToolTool to create a new tool.
Delete DatapointTool to delete a specific datapoint by its ID.
Delete DatasetTool to delete a dataset by ID.
End Evaluation RunTool to mark an evaluation run as completed.
Get ConfigurationsTool to retrieve a list of configurations.
Get DatasetsTool to retrieve a list of datasets.
Get MetricsTool to retrieve all metrics.
Get ProjectsTool to retrieve projects.
List ToolsTool to list all available Honeyhive tools.
Retrieve DatapointTool to retrieve a specific datapoint by its ID.
Retrieve DatapointsTool to retrieve a list of datapoints.
Retrieve EventsTool to retrieve events by filters.
Retrieve Experiment ResultTool to retrieve the result of a specific experiment run.
Start Evaluation RunTool to initiate an evaluation run using external datasets.
Start SessionTool to start a new session.
Update DatapointTool to update a specific datapoint.
Update DatasetTool to update an existing dataset.
Update EventTool to update an event.
Update MetricTool to update an existing metric.
Update ProjectTool to update a project's name or description.

Conclusion

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

How to build Honeyhive MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Honeyhive MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Honeyhive MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Honeyhive MCP with Claude Code

OpenClaw logo

OpenClaw

Use Honeyhive MCP with OpenClaw

CLI logo

CLI

Use Honeyhive MCP with CLI

Google ADK logo

Google ADK

Use Honeyhive MCP with Google ADK

LangChain logo

LangChain

Use Honeyhive MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Honeyhive MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Honeyhive MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Honeyhive MCP with LlamaIndex

CrewAI logo

CrewAI

Use Honeyhive MCP with CrewAI

FAQ

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

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

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

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