memmd-mcp
Provides a shared memory layer for OpenAI Codex, allowing agents to persist and retrieve structured memories (facts, context, preferences) across sessions via a single memory.md file.
Click on "Deploy 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., "@memmd-mcp remember that I'm using Python 3.12 for memmd-mcp"
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.
memmd-mcp
A shared memory layer for AI agents — one memory.md synced across Claude Desktop, Cursor, Claude Code, OpenAI Codex, and any MCP client. Auto-deduplication, contradiction resolution, and stale cleanup included.
Why memmd?
One memory, every client — Claude Desktop, Cursor, Claude Code, OpenAI Codex share the same
memory.mdZero external dependencies beyond
mcp— no embeddings, no API keys, fully offlineDeterministic, rule-based — no LLM calls for memory management
Human-readable
memory.md— inspect and edit anytime
Features
Deduplication — fingerprint + Jaccard similarity merges near-identical entries
Contradiction resolution — detects conflicting facts, keeps latest, archives old
Structured categories — Work Context · Projects · Personal Preferences · Archive
Section-aware recall — filter by category, keyword search with scoring
Stale cleanup — auto-archives old, unused entries on
summarize()Korean support — category aliases, fact patterns (
~는 ~), stopwords
Related MCP server: auxly-memory-cli
Quick Start
Install and run
uvx memmd-mcpAdd to your MCP client
{
"mcpServers": {
"memmd": {
"command": "uvx",
"args": ["memmd-mcp"],
"env": {
"MEMMD_MEMORY_PATH": "/absolute/path/to/memory.md"
}
}
}
}Config location by client:
Claude Desktop —
~/Library/Application Support/Claude/claude_desktop_config.jsonClaude Code —
.claude/settings.jsonor user settingsCursor —
~/.cursor/mcp.jsonOpenAI Codex —
~/.codex/config.toml
Tools
Tool | Description |
| Store with auto-dedupe and contradiction merge |
| Search with keyword scoring and category filters |
| Delete by ID |
| Category overview + stale entry cleanup |
How It Works
remember
Dedupes by SHA-1 fingerprint and Jaccard similarity (>0.82)
Extracts facts from
key: value,key = value,key is value,key는 valueOn conflict: latest value wins, old entry archived with history
recall
Keyword search with token-overlap scoring
Filters:
category:Projects API token,section:"Work Context" deployKorean aliases accepted (
category:프로젝트)
summarize
Per-category summary of recent entries
Archives stale entries (default: >120 days, <3 accesses, no recent recall)
memory.md Format
# memory.md
<!-- memmd:version=1 -->
## Work Context
<!-- memmd-entry {...json...} -->
Memory content
## Projects
...
## Personal Preferences
...
## Archive
...Environment Variables
Variable | Default | Description |
|
| Path to memory file |
|
| Days before stale cleanup (min: 7) |
License
MIT
Available Tools
4 toolsforgetC
Delete a memory entry by ID.
Inputs: id (required). Returns: result
recallC
Search memory entries with optional section/category filters.
Inputs: query (required). Returns: result
rememberC
Add memory content with automatic dedupe/contradiction merge.
Inputs: content (required), category. Returns: result
summarizeA
Summarize memory by category and archive stale entries.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: forget deletes by ID, recall searches with filters, remember adds with merging, and summarizes archives. No overlap or ambiguity.
All tool names are single-word, lowercase verbs following a consistent imperative pattern (forget, recall, remember, summarize).
4 tools is a well-scoped count for a memory management server, covering essential operations without bloat or deficiency.
The set covers create (remember), read (recall), delete (forget), and maintenance (summarize). An explicit update tool is missing, but remember's merge functionality partially addresses it.
Maintenance
Related MCP Connectors
One memory for your AI agents and your team: Claude, ChatGPT, Cursor and your agents share it.
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
One memory for all your AI tools: Claude, ChatGPT, Cursor and any MCP client share the same notes.
Shared AI memory. ChatGPT, Claude, Cursor and any MCP app read and write the same memory.
Related MCP Servers
- AlicenseAqualityAmaintenanceHosted memory for AI agents that learns from outcomes, with shared rooms. One key across Claude, Cursor & ChatGPT.11936 npm28MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.2MIT
- AlicenseAqualityBmaintenanceA local-first shared memory layer for MCP-aware agents like Claude, Codex, and Hermes, enabling persistent memory across chats and clients via Markdown files and SQLite FTS.62MIT
- AlicenseAqualityCmaintenanceShared, versioned memory for your agents across Claude Code, Cursor, Kiro and Grok. One MCP server, sourced answers, full history.3MIT