How to integrate Zep MCP with Claude Code

Manage your Zep directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Zep logoZep
Api Key

Zep is a foundational memory layer for AI agents and apps. It lets your AI remember, recall, and organize key information over time.

43 Tools

Introduction

Manage your Zep directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Zep with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Zep to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Zep via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Zep) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Zep account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['zep'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http zep-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Zep. This URL will be used to connect Claude Code to Zep.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Zep
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Zep MCP to Claude Code

bash
claude mcp add --transport http zep-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (zep-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Zep MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your zep-composio entry in the list
  • This confirms that Claude Code can now access Zep tools

If everything is wired up, you should see your zep-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Zep

The first time you try to use Zep tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Zep
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Zep authorization flow
  • Return to the terminal and start using Zep through Claude Code

Once authenticated, you can ask Claude Code to perform Zep operations in natural language. For example:

  • "Store a memory about today's meeting"
  • "Retrieve all memories tagged urgent"
  • "Summarize knowledge about client preferences"

Complete Code

Here's the complete code to get you started with Zep and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['zep'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http zep-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Zep with Claude Code using Composio's MCP server. Now you can interact with Zep directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Zep operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Zep operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Zep action and event your agent gets out of the box.

Add Fact Triple

Tool to add a manually specified fact triple (subject-predicate-object) to the Zep knowledge graph.

Add Session Memory

Tool to add memory messages to a specified Zep session.

Add Thread Messages

Tool to add chat messages to a thread in Zep and ingest them into the user knowledge graph.

Clone Graph

Tool to clone a user or group graph with new identifiers in Zep.

Create Graph

Tool to create a new graph by adding data to Zep.

Create Group

Tool to create a new group in Zep for multi-user graph management.

Create Session

Tool to create a new session in Zep for storing conversation memory.

Create Thread

Tool to create a new thread in Zep for a specific user.

Create User

Tool to create a new user in Zep with properties like user_id, email, and metadata.

Delete Graph

Tool to delete a graph from Zep.

Delete Group

Tool to delete a group from Zep.

Delete Session Memory

Tool to delete a session and its memory from Zep.

Delete Thread

Tool to delete a thread and its messages from Zep.

Delete User

Tool to delete a user and all associated threads and artifacts from Zep.

Get Edge by UUID

Tool to retrieve a specific edge by its UUID from the Zep knowledge graph.

Get Graph by ID

Tool to retrieve a graph by its unique identifier from Zep.

Get Group by ID

Tool to retrieve a group by ID from Zep.

Get Node Entity Edges

Tool to retrieve all entity edges for a specific node in the Zep knowledge graph.

Get Project Info

Tool to retrieve project information based on the provided API key.

Get Session by ID

Tool to retrieve a session by its unique identifier from Zep.

Get Session Memory

Tool to retrieve memory for a given session including relevant facts and entities.

Get Session Message by UUID

Tool to retrieve a specific message by UUID from a Zep session.

Get Session Messages

Tool to retrieve messages for a given session from Zep.

Get Task Status

Tool to check the status of asynchronous operations in Zep.

Get Thread Messages

Tool to retrieve conversation history for a specific thread from Zep.

Get Thread User Context

Tool to retrieve the most relevant user context from the user graph based on thread messages.

Get User by ID

Tool to retrieve a user by their user ID from Zep.

Get User Node

Tool to retrieve a user's graph node and summary from Zep.

Get User Nodes

Tool to retrieve all nodes for a specific user from their graph in Zep.

Get User Sessions

Tool to retrieve all sessions for a user from Zep.

Get User Threads

Tool to retrieve all threads for a specific user from Zep.

Graph Search

Tool to perform hybrid graph search combining semantic similarity and BM25 full-text search across the Zep knowledge graph.

List Graphs

Tool to retrieve all graphs from Zep with pagination support.

List Groups Ordered

Tool to retrieve all groups from Zep with pagination support.

List Sessions Ordered

Tool to retrieve all sessions from Zep with pagination and ordering support.

List Threads

Tool to retrieve all threads from Zep with pagination support.

List Users Ordered

Tool to retrieve all users from Zep with pagination support.

List All Threads

Tool to list all threads with pagination and ordering support.

Update Graph

Tool to update graph information in Zep including name and description.

Update Group

Tool to update group information in Zep including name, description, and fact rating instructions.

Update Message

Tool to update a message in a Zep thread.

Update Session Metadata

Tool to update session metadata in Zep.

Update User

Tool to update an existing user's information in Zep including email, metadata, and ontology settings.

FAQ

Frequently asked questions

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.

Yes, you can. Claude Code 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.

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.

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.

Start with Zep.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Zep tool your agent needs.Free to start.

Start building