How to integrate Zep MCP with Claude Agent SDK

This guide walks you through connecting Zep to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Zep agent that can store a memory about today's meeting, retrieve all memories tagged urgent, summarize knowledge about client preferences through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Zep account through Composio's Zep MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

Zep

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

Managed auth

Connect Zep without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your Claude Agent SDK agent real control over a Zep account through Composio's Zep MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Zep with

ChatGPT OpenAI Agents SDK Claude Code Claude Cowork Codex OpenCode Cursor VS Code OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your Claude/Anthropic and Composio API keys
Install the necessary dependencies
Initialize Composio and create a Tool Router session for Zep
Configure an AI agent that can use Zep as a tool
Run a live chat session where you can ask the agent to perform Zep operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

Native MCP Support: Built-in support for Model Context Protocol servers
Permission Modes: Control tool execution permissions
Streaming Responses: Real-time response streaming for interactive applications
Context Manager: Clean async context management for sessions

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

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

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before starting, make sure you have:

Composio API Key and Claude/Anthropic API Key
Primary know-how of Claude Agents SDK
A Zep account
Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key

Go to the Anthropic Console and create an API key. You'll need credits to use the models.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

@composio/core provides Composio integration for Anthropic
@anthropic-ai/claude-agent-sdk is the core agent framework
dotenv/config loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID identifies the user for session management
ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();

What's happening:

We're importing all necessary libraries including the Claude Agent SDK and Composio
The dotenv.config() function loads environment variables from your .env file
This setup prepares the foundation for connecting Claude with Zep functionality

Create a Composio instance and Tool Router session

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Zep
  const session = await composio.create(USER_ID, {
    toolkits: ['zep'],
  });
  const mcpUrl = session?.mcp.url;

What's happening:

The function checks for the required COMPOSIO_API_KEY environment variable
We're creating a Composio instance using our API key
The create method creates a Tool Router session for Zep
The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Zep tools via Composio.',
  maxTurns: 10,
};

What's happening:

We're configuring the Claude Agent options with the MCP server URL
permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
The system prompt instructs the agent that it has access to Zep
maxTurns: 10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

What's happening:

The readline interface is created to handle user input and output
The query function is used to send the user's input to the agent
The chat loop continues until the user types 'exit' or 'quit'

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

What's happening:

The chat function is the entry point for the application
The try-catch block is used to handle any errors that occur

Complete Code

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

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['zep']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Zep tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Zep through Composio's Tool Router.

Key features:

Native MCP support through Claude's agent framework
Streaming responses for real-time interaction
Permission bypass for smooth automated workflows

You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

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.

FRAMEWORKS

How to build Zep MCP Agent with another framework

ChatGPT

Use Zep MCP with ChatGPT

OpenAI Agents SDK

Use Zep MCP with OpenAI Agents SDK

Claude Code

Use Zep MCP with Claude Code

Claude Cowork

Use Zep MCP with Claude Cowork

Codex

Use Zep MCP with Codex

Cursor

Use Zep MCP with Cursor

OpenClaw

Use Zep MCP with OpenClaw

Hermes

Use Zep MCP with Hermes

CLI

Use Zep MCP with CLI

Google ADK

Use Zep MCP with Google ADK

LangChain

Use Zep MCP with LangChain

Vercel AI SDK

Use Zep MCP with Vercel AI SDK

Mastra AI

Use Zep MCP with Mastra AI

LlamaIndex

Use Zep MCP with LlamaIndex

CrewAI

Use Zep MCP with CrewAI

OpenCode

Use Zep MCP with OpenCode

VS Code

Use Zep MCP with VS Code

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Sheets

Oauth2

Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.

Composio

No Auth

Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.

Notion

Oauth2Api Key

Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.

Airtable

Oauth2Api Key

Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.

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 Agent SDK 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

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Zep MCP with Claude Agent SDK

Connect Zep without auth hassles

Introduction

Also integrate Zep with

TL;DR

What is Claude Agent SDK?

What is the Zep MCP server, and what's possible with it?

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for Claude/Anthropic and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio instance and Tool Router session

Configure Claude Agent with MCP

Create client and start chat loop

Run the application

Complete Code

Conclusion

Supported Tools

How to build Zep MCP Agent with another framework

ChatGPT

OpenAI Agents SDK

Claude Code

Claude Cowork

Codex

Cursor

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

OpenCode

VS Code

Explore Other Toolkits

Google Sheets

Composio

Notion

Airtable

Frequently asked questions

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

Can I use Tool Router MCP with Claude Agent SDK?+

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

How safe is my data with Composio Tool Router?+

Start with Zep.It takes 30 seconds.

Teams ship real agents on Composio