Zep Integrations

August 7, 2026 · View on GitHub

Dedicated integration packages for using Zep agent memory with AI frameworks. Each integration is packaged separately so you install only what you need.

Integrations are organized framework-first, then language: integrations/<framework>/<language>/.

New to Zep? Sign up at getzep.com and create an API key in the Zep dashboard; each package's SETUP.md has the details.

Available integrations

Framework	Language	Package	Location
AG2	Python	`zep-ag2`	`ag2/python/`
CrewAI	Python	`zep-crewai`	`crewai/python/`
Google ADK	Python	`zep-adk`	`adk/python/`
Google ADK	TypeScript	`@getzep/zep-adk`	`adk/typescript/`
Google ADK	Go	`github.com/getzep/zep/integrations/adk/go`	`adk/go/`
LangGraph	Python	`zep-langgraph`	`langgraph/python/`
LiveKit	Python	`zep-livekit`	`livekit/python/`
Mastra	TypeScript	`@getzep/zep-mastra`	`mastra/typescript/`
Microsoft Agent Framework	Python	`zep-ms-agent-framework`	`ms-agent-framework/python/`
Microsoft AutoGen	Python	`zep-autogen`	`autogen/python/`
Pydantic AI	Python	`zep-pydantic-ai`	`pydantic-ai/python/`
Strands Agents	Python	`zep-strands`	`strands/python/`
Vercel AI SDK	TypeScript	`@getzep/zep-vercel-ai`	`vercel-ai/typescript/`

Looking for bulk data ingestion (Slack exports, documents, email, CSV/JSON records, fact triples)? That's the standalone zep-ingest package at the repository root — not a framework integration.

See CLAUDE.md for the full per-language structure and conventions. In short, each package lives at integrations/<framework>/<language>/ and ships a README, a SETUP.md, a runnable example, tests, and a changelog.

Development

Each package is built and tested independently. For a Python package:

cd integrations/<framework>/python
uv sync --extra dev      # install (dev extras)
uv run pytest            # test
uv build                 # build

TypeScript: npm ci && npm test. Go: go test ./.... See CLAUDE.md for the full per-language commands and the CI/release setup.

Adding a new integration

Create integrations/<framework>/<language>/ following the structure in CLAUDE.md.
Implement the framework's memory/context extension point; target the latest Zep SDK.
Add tests, a runnable example, a README, and a SETUP.md.
Wire CI: add a paths-filter entry in .github/workflows/test-integrations.yml.
Open a PR.

Release

Each package releases independently via .github/workflows/release-integrations.yml. Python and TypeScript use zep-<framework>-<language>-v<version> release tags. For Go, manually dispatch the workflow from main with the framework and version; after validation it creates the module-path tag integrations/<framework>/go/vX.Y.Z and GitHub Release.

Support

Contributing

Contributions welcome — see the Contributing Guide.