memory-mcp
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., "@memory-mcpfind memories about react hooks"
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.
memory-mcp — shared-brain MCP server
A local stdio MCP server over ~/.claude/memory.
Exposes the LLM-Wiki brain (read / search / write) so a memory written in any
agent — Claude Code, Cursor, Codex — is readable and searchable in all three.
One brain, three clients, file-backed, no external service.
Tools
Tool | What it does |
| Text + frontmatter ranking over name/description/tags/body (+ bucket filter, limit). |
| One memory by name → frontmatter + body + resolved outbound |
| List memories (name, type, description), optional bucket filter. |
| Inbound + outbound wikilink neighbours for a memory. |
| Create/update a memory, regenerate |
Related MCP server: zime-memory
Architecture
Standalone TypeScript (ESM, strict +
exactOptionalPropertyTypes), run viatsx.Reads use a strict-typed parser/scanner; a corpus-parity test asserts agreement with the real brain so frontmatter never drifts.
Writes delegate index/hot/lint to the existing
~/.claude/tools/braintoolkit (subprocess,CLAUDE_DIR-scoped) — brain's exact logic, no source coupling.Search is text + frontmatter only (no embeddings in v1).
Config
CLAUDE_DIR— brain root (default~/.claude);<CLAUDE_DIR>/memoryholds the buckets.BRAIN_DIR—tools/braincheckout (default<CLAUDE_DIR>/tools/brain).
Run
node node_modules/tsx/dist/cli.mjs src/server.ts # stdio MCP server (stdout = MCP channel)
npm test # vitest
npm run typecheckRegistration in Claude Code / Cursor / Codex: see register.md.
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
- AlicenseAqualityBmaintenanceAn MCP server that reads all your Claude Code project memory files and exposes them as tools. Lets any Claude instance — in any project, or via Claude.ai — query your full project history and preferences.Last updated5171MIT
- Flicense-qualityDmaintenanceA personal memory MCP server for Claude Code that stores and retrieves memories via natural language, supporting text, images, files, and secrets with vector search.Last updated
- AlicenseAqualityCmaintenanceA local shared-memory MCP server for Claude, Codex, Hermes, and other MCP-aware agents, providing a durable memory layer with Markdown files and SQLite fact store.Last updated6MIT
- Alicense-qualityDmaintenanceA persistent memory MCP server for Claude Code that enables long-term recall across sessions via hybrid search, code intelligence, and tools for reading/writing memory.Last updated41MIT
Related MCP Connectors
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Person-owned, portable AI memory as a remote MCP server, readable and writable by any MCP client.
StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.
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/KM-it-ops/memory-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server