> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs-beta.getzep.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs-beta.getzep.com/_mcp/server.

# Zep for Agent Frameworks

> Use Zep with supported agent frameworks for conversation persistence, Context Graph search, and provider-aware context placement.

Zep integrations for agent frameworks support agent memory, Context Graph search, and context placement. Memory-specific integrations persist conversation turns and retrieve data from a user's [Context Graph](/graph-overview). Search tools can also retrieve shared or domain context with `graph_id`.

Use model-callable search tools or place retrieved context in your provider's untrusted-data channel.

> **Keep retrieved context out of privileged instructions**
>
> Zep context can include content that your users, documents, or tools supplied. A system or developer message gives that content higher instruction priority than ordinary input. Some convenience integrations use system-message injection. Use direct SDK retrieval or an actual retrieval tool call unless all stored content is application-authored and trusted. Follow [Memory security best practices](/memory-security) for provider-specific placement.

> **Build an agent with Zep tools**
>
> To build an agent that plans its retrieval and uses several Zep tools, read [Build an Agent with Zep](/build-an-agent-with-zep). The guide shows how to add domain knowledge, design tools, and evaluate the agent.

You keep the framework's orchestration, tools, and runtime. Zep stores and retrieves agent memory across sessions.

If your framework is not listed, use a [Zep SDK](/sdk-reference) directly. The [quick start guide](/quick-start-guide) shows the user, thread, ingestion, and retrieval flow.

## Provisioning behavior

Provisioning differs by integration:

* LangGraph and Google ADK require you to create the Zep user and thread before the first turn.
* Other package integrations can create users and threads on first use. Check the integration guide before you enable this behavior.
* Eve and ElevenLabs use SDK patterns instead of a Zep integration package.

## Supported frameworks

* [**AG2**](/ag2-memory): Zep search tools, plus a trusted-content-only automatic memory loop.
* [**AutoGen**](/autogen-memory): Tools for search and data ingestion, plus trusted-content-only memory classes on AutoGen's Memory interface.
* [**CrewAI**](/crewai-memory): Storage adapters and tools so CrewAI agents carry context across executions and share a knowledge base.
* [**ElevenLabs**](/elevenlabs): SDK pattern for a custom LLM proxy. The proxy places context in user-level input.
* [**Eve**](/eve): Hooks persist turns. Authored tools retrieve context with `graph.search`.
* [**Google ADK**](/google-adk-memory): Message persistence and model-callable search tools, plus trusted-content-only instruction injection.
* [**LangGraph**](/langgraph-memory): Node helpers and a graph-search tool, plus a trusted-content-only pre-model hook.
* [**LiveKit**](/livekit-memory): Turn persistence and graph search, plus trusted-content-only instruction injection.
* [**Mastra**](/mastra-memory): Processors and tools that add long-term memory to Mastra agents.
* [**Microsoft Agent Framework**](/microsoft-agent-framework-memory): Turn persistence and a graph-search tool, plus a trusted-content-only context provider.
* [**NVIDIA NeMo Agent Toolkit**](/nvidia-nemo): Trusted-content-only automatic memory for NVIDIA NeMo Agent Toolkit agents.
* [**Pydantic AI**](/pydantic-ai-memory): Turn persistence and a model-callable graph-search tool, plus trusted-content-only prompt injection.
* [**Strands**](/strands-memory): A Strands `MemoryStore` with batched extraction and graph search, plus trusted-content-only context injection.
* [**Vercel AI SDK**](/vercel-ai-memory): Middleware, helpers, and tools for long-term memory in Vercel AI SDK (v6) applications.