How to integrate Zep MCP with Google ADK

GET STARTED FOR FREE
Framework Integration Gradient
Zep Logo
Google ADK Logo
divider

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.

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.

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.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

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

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.

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

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

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

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

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

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

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.

How to build Zep MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Zep MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Zep MCP with Claude Agent SDK

LangChain

LangChain

Use Zep MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Zep MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Zep MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Zep MCP with LlamaIndex

CrewAI

CrewAI

Use Zep MCP with CrewAI

Claude Code

Claude Code

Use Zep MCP with Claude Code

Codex

Codex

Use Zep MCP with Codex

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

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.

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.

Book a call↗Get started for free