zep-memory

Store and retrieve persistent knowledge graph memories via Graphiti MCP server.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ships/eden --skill zep-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zep-memory
Source: https://github.com/ships/eden/tree/main/assets/claude/skills/zep-memory
Command: npx skills add https://github.com/ships/eden --skill zep-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Zep-memory helps AI agents retain important information across sessions by storing and retrieving it from a persistent knowledge graph, so future suggestions and actions respect prior context and discovered preferences.

Core Features & Use Cases

  • Search-first retrieval for alignment: Finds relevant prior Preferences and Procedures before acting, reducing inconsistency.
  • Immediate capture of reusable knowledge: Stores new requirements, facts, and step-by-step workflows as soon as they are discovered.
  • Explicit group_id scoping for isolation: Prevents knowledge pollution by requiring intentional group_id management (per-user, per-project, per-worktree, etc.).
  • Entity-focused, anti-bloat retrieval: Encourages entity_types filtering and targeted fact queries to avoid overly broad results.

Quick Start

Use zep-memory to store and later retrieve the user’s project-specific deploy procedure by searching for existing procedures first, then adding the new workflow as a Procedure under a group_id scoped to that project.

Frequently Asked Questions about zep-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist agent memory across different conversation sessions?

You can persist agent memory across sessions by using a knowledge graph to store and retrieve preferences, requirements, and procedures, ensuring future actions respect prior context. This approach prevents inconsistency by retaining discovered facts beyond single conversation boundaries.

What is the best way to prevent context leakage when storing agent knowledge?

To prevent context leakage when storing agent knowledge, you must apply explicit group_id scoping to isolate data per user, project, or worktree. Additionally, using targeted entity_types filtering during retrieval prevents knowledge pollution from overly broad search results.

How do I save reusable procedures and requirements to a knowledge graph?

You can save reusable procedures and requirements by using the add_memory operation with appropriate source types like text, json, or message. This immediately captures new workflows and facts into the persistent graph as soon as they are discovered during interactions.

Can I retrieve specific entity facts from agent memory without returning irrelevant data?

Yes, you can retrieve specific entity facts without returning irrelevant data by applying explicit entity_types filtering during your search operations. This entity-focused, anti-bloat retrieval mechanism encourages targeted fact queries to avoid overly broad results.

Does agent memory work with the Graphiti MCP server for cross-session retention?

Yes, agent memory works with the Graphiti MCP server to provide persistent knowledge graph storage and retrieval. This integration enables cross-session retention of preferences and reusable procedures across different conversation boundaries and project contexts.