How to integrate Zep MCP with Google ADK

This guide walks you through connecting Zep to Google ADK 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 Google ADK 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.

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

This guide walks you through connecting Zep to Google ADK 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 Google ADK 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

TL;DR

Here's what you'll learn:
  • Get a Zep account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Zep
  • Build an agent that connects to Zep through MCP
  • Interact with Zep using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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:

  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 step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Zep via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["zep"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Zep operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Zep and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["zep"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Zep operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Zep with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Zep using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Zep tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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. Google ADK 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