How to integrate Zep MCP with Codex

Framework Integration Gradient
Zep Logo
Codex Logo
divider

Introduction

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

The Zep MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Zep account. It provides structured and secure access so your agent can perform Zep operations on your behalf.

Supported Tools & Triggers

Tools
Add Fact TripleTool to add a manually specified fact triple (subject-predicate-object) to the Zep knowledge graph.
Add Session MemoryTool to add memory messages to a specified Zep session.
Add Thread MessagesTool to add chat messages to a thread in Zep and ingest them into the user knowledge graph.
Clone GraphTool to clone a user or group graph with new identifiers in Zep.
Create GraphTool to create a new graph by adding data to Zep.
Create GroupTool to create a new group in Zep for multi-user graph management.
Create SessionTool to create a new session in Zep for storing conversation memory.
Create ThreadTool to create a new thread in Zep for a specific user.
Create UserTool to create a new user in Zep with properties like user_id, email, and metadata.
Delete GraphTool to delete a graph from Zep.
Delete GroupTool to delete a group from Zep.
Delete Session MemoryTool to delete a session and its memory from Zep.
Delete ThreadTool to delete a thread and its messages from Zep.
Delete UserTool to delete a user and all associated threads and artifacts from Zep.
Get Edge by UUIDTool to retrieve a specific edge by its UUID from the Zep knowledge graph.
Get Graph by IDTool to retrieve a graph by its unique identifier from Zep.
Get Group by IDTool to retrieve a group by ID from Zep.
Get Node Entity EdgesTool to retrieve all entity edges for a specific node in the Zep knowledge graph.
Get Project InfoTool to retrieve project information based on the provided API key.
Get Session by IDTool to retrieve a session by its unique identifier from Zep.
Get Session MemoryTool to retrieve memory for a given session including relevant facts and entities.
Get Session Message by UUIDTool to retrieve a specific message by UUID from a Zep session.
Get Session MessagesTool to retrieve messages for a given session from Zep.
Get Task StatusTool to check the status of asynchronous operations in Zep.
Get Thread MessagesTool to retrieve conversation history for a specific thread from Zep.
Get Thread User ContextTool to retrieve the most relevant user context from the user graph based on thread messages.
Get User by IDTool to retrieve a user by their user ID from Zep.
Get User NodeTool to retrieve a user's graph node and summary from Zep.
Get User NodesTool to retrieve all nodes for a specific user from their graph in Zep.
Get User SessionsTool to retrieve all sessions for a user from Zep.
Get User ThreadsTool to retrieve all threads for a specific user from Zep.
Graph SearchTool to perform hybrid graph search combining semantic similarity and BM25 full-text search across the Zep knowledge graph.
List GraphsTool to retrieve all graphs from Zep with pagination support.
List Groups OrderedTool to retrieve all groups from Zep with pagination support.
List Sessions OrderedTool to retrieve all sessions from Zep with pagination and ordering support.
List ThreadsTool to retrieve all threads from Zep with pagination support.
List Users OrderedTool to retrieve all users from Zep with pagination support.
List All ThreadsTool to list all threads with pagination and ordering support.
Update GraphTool to update graph information in Zep including name and description.
Update GroupTool to update group information in Zep including name, description, and fact rating instructions.
Update MessageTool to update a message in a Zep thread.
Update Session MetadataTool to update session metadata in Zep.
Update UserTool to update an existing user's information in Zep including email, metadata, and ontology settings.

Conclusion

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

How to build Zep MCP Agent with another framework

FAQ

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

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

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

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