getzep/zep is a repository of examples, framework integrations, ingestion tools, and evaluation utilities for building agent memory with Zep Cloud, a managed service for storing and retrieving information used by AI agents. It is for developers integrating Zep Cloud into agent applications and workflows. The catalogue skills and MCP entry are add-ons for working with that ecosystem.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/getzep/zepWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/getzep/zep/claude-desktop-zep)<a href="https://agentmods.dev/mcp/getzep/zep/claude-desktop-zep"><img src="https://agentmods.dev/badge/mcp/getzep/zep/claude-desktop-zep/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/getzep/zep/claude-desktop-zep"><img src="https://agentmods.dev/badge/mcp/getzep/zep/claude-desktop-zep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zep scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"zep": {
"command": "/path/to/zep-mcp-server",
"env": {
"ZEP_API_KEY": "your-zep-api-key-here"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 8 lines scan A 425983633a7a
zep is an MCP server published in the GitHub repository getzep/zep (4,899 stars, last pushed 6d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
telemem
Long-term & multimodal memory for AI agents — character isolation, video pipeline, MCP server, mem0-compatible. Runs locally from the telemem Python package. Needs 3 environment variables to run.
technocore-chat
MCP server for technocore-chat: shared rooms, durable notes and rendezvous for agents, over plain HTTP. Runs locally from the technocore-mcp Python package. Needs 2 environment variables to run.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
agent-magnet
Self-learning memory infrastructure for AI products. Runs locally from the agent-magnet Python package. Needs 6 environment variables to run.
kiagent
Your mail, chats and documents indexed into a local SQLite corpus, served to AI clients over MCP. Remote server at {subdomain}.localkiagent.com.