Epiphany
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Epiphanyrecall what I said about the new feature"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Epiphany
One private, local memory your AI tools share.
Every AI you use forgets you the moment the chat ends. You re-explain the same context over and over, and when a session dies, the reasoning behind it is gone for good. Epiphany fixes that. It's a single memory that lives on your machine, that Claude, Grok, Gemini, and more all read from and write to, so what you tell one, the others already know.
Local-first. Your brain is a file on your disk. Nothing leaves the machine. No account, no cloud, no company owns your memory.
Cross-model. One shared memory across Claude (Desktop + Code), Grok, Gemini, Cursor, Antigravity, Warp, and Hermes. Tell Grok something, ask Claude about it.
Real memory, not bullet points. Thoughts carry their reasoning and connect into a graph, so recall returns why something is true and what it followed from, not a lone fact. Ask a follow-up and it holds the thread.
Never lose a session. A background watcher reads the transcripts your tools already write to disk and files every session into the brain in near-real-time, even ones that crashed before anything was saved.
How it works
Epiphany is a local MCP server plus a tiny CLI.
It runs a small server on your machine that exposes two tools to any AI client:
recallandremember.epiphany connect <tool>wires that server into each AI tool, in the tool's own config format, and installs a standing rule so the agent reaches for your memory on its own.Memories are embedded on-device (a local model, nothing sent anywhere) and stored in SQLite. Agents wire explicit reasoning connections between thoughts (
because,builds_on,part_of, ...), and recall walks that graph to reconstruct the whole thought-string.A background watcher sees your tools' session logs the moment they change and sweeps them into the brain, so nothing is ever lost.
The intelligence stays in the models you already use. The brain itself is a fast, private librarian: it holds, connects, and recalls. It never phones home.
Related MCP server: mindmap-mcp-server
Quickstart
Requires Node 18+.
git clone https://github.com/GATSV-tech/epiphany.git
cd epiphany
npm install
npm run build
npm link # puts the `epiphany` command on your PATHWire it into the tools you use, then fully restart each one:
epiphany connect claude-code
epiphany connect grok
epiphany connect gemini
epiphany list # see all supported toolsTurn on the background "never lose a session" sweep:
epiphany scheduleThat's it. Now talk to any connected AI. It will recall what you've told the others and save what's worth keeping, on its own.
Run epiphany with no arguments any time to open the dashboard and look inside your brain.
Supported tools
Tool | Connector | Standing rule |
Claude Code (every terminal) | auto | auto |
Grok CLI | auto | auto |
Gemini CLI | auto | auto |
Antigravity (Google IDE) | auto | shared with Gemini |
Claude Desktop | auto | guided (account setting) |
Cursor | auto | guided (app setting) |
Warp (terminal, Agent Mode) | auto | guided (app setting) |
Hermes (Nous Research agent) | auto | guided (instructions) |
Commands
epiphany connect <tool> wire Epiphany into an AI tool (connector + rule)
epiphany rule <tool> update just the standing rule for a tool
epiphany list show supported tools
epiphany dash open the interactive dashboard (browse, search, curate)
epiphany status show brain size, connected tools, and auto-capture state
epiphany ingest sweep session logs into the brain now (one-shot)
epiphany watch run the near-real-time watcher in the foreground
epiphany schedule install the background watcher (captures sessions as they happen)Your brain lives at ~/.epiphany/brain.db. It's yours. Back it up, inspect it, delete it, it's just SQLite.
Roadmap
Epiphany's core, local cross-model memory with reasoning graphs and automatic capture, works today. Next:
More session sources for the ingestor (Claude Code, Cursor transcripts).
Reconciliation. When a fact changes, the brain flags the conflict and you confirm the update, so memory self-corrects instead of piling up contradictions.
Cloud bridge. An optional relay so cloud-only surfaces (ChatGPT on the web, wearables) can reach your local brain.
Desktop app. A download-and-run shell for people who don't live in a terminal.
One-line install via npm.
Contributions and ideas welcome.
License
MIT.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityAmaintenanceA local MCP server that gives AI assistants a long-term memory by capturing sessions verbatim and surfacing relevant context automatically.Last updated15475MIT
- AlicenseAqualityBmaintenanceA local-first MCP server for shared memory across AI tools, enabling context capture and resume across sessions.Last updated261302Apache 2.0
- Alicense-qualityDmaintenanceA portable MCP server providing a shared intelligent memory system for any MCP-compatible AI tool, enabling storage, retrieval, extraction, and governance of memories across sessions.Last updated44MIT
- Alicense-qualityCmaintenanceA local-first memory server for AI tools that provides cross-tool, consent-gated, and auditable memory management via MCP.Last updatedAGPL 3.0
Related MCP Connectors
Person-owned, portable AI memory as a remote MCP server, readable and writable by any MCP client.
Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.
Cloud-hosted MCP server for durable AI memory
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GATSV-tech/epiphany'
If you have feedback or need assistance with the MCP directory API, please join our Discord server