Elefante
Give Claude Code or Cursor a Git-backed, human-editable memory store that survives sessions and repos instead of opaque chat history.
Overview
Elefante is an MCP server for the Build phase that stores agent memory in an open, Git-native, human-editable protocol.
What is this MCP server?
- Open, Git-native memory protocol designed for MCP agents
- Portable, versioned storage you can diff, branch, and edit like code
- stdio npm package (elefante-mcp 0.1.9) for local MCP clients
- Human-readable artifacts instead of proprietary session blobs
- Fits solo builders who want memory to travel with the repository
- Server schema MCP registry version 0.1.9
- 1 npm stdio package identifier: elefante-mcp
- Transport type: stdio
Community signal: 15 GitHub stars.
What problem does it solve?
Agent sessions forget context unless you paste the same background every time or hide state in formats you cannot audit in Git.
Who is it for?
Indie builders running long-horizon agent projects who want portable, diffable memory tied to Git.
Skip if: Teams that only need ephemeral chat context or a hosted vector DB with no Git workflow.
What do I get? / Deliverables
After registration, your agent can persist and reload versioned memory files that live in your repo workflow instead of a black-box store.
- Registered stdio MCP server for agent memory read/write
- Portable, versioned memory artifacts aligned with the open Elefante protocol
Recommended MCP Servers
Journey fit
Agent memory is wired during build when you connect MCP tooling; it stays relevant in operate when you refine what the agent remembers across iterations. Elefante is an MCP memory protocol—canonical shelf is agent-tooling because you register it beside other agent integrations, not as a one-off research fetch.
How it compares
Git-native MCP memory protocol, not a generic notes skill or hosted-only RAG service.
Common Questions / FAQ
Who is Elefante for?
Solo and indie builders using MCP-compatible agents who want durable, editable project memory under version control.
When should I use Elefante?
When you are wiring agent tooling in Build (or refining memory in Operate) and need context to survive across sessions and machines.
How do I add Elefante to my agent?
Install the npm package elefante-mcp (stdio transport) and register the MCP server in your client’s config (e.g. Claude Code or Cursor MCP settings).