@renzynx/memory-mcp
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., "@@renzynx/memory-mcp save that I prefer Python over JavaScript"
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.
@renzynx/memory-mcp
A persistent memory MCP server with FTS5 fuzzy search. Compatible with Bun and Node.js.
Features
Persistent Storage: Data stored in
~/.mcp-memory/memory.dbsurvives npx/bunx cache clearsFuzzy Search: FTS5 with trigram tokenization for substring matching (
pyth→python)Token Efficient: Results in TOON format for minimal token usage
Auto Maintenance: Prunes entries older than 30 days, creates backups on startup
Cross Runtime: Works with both Bun and Node.js
Related MCP server: agent-memory
Installation
npx @renzynx/memory-mcp
# or
bunx @renzynx/memory-mcpConfiguration
OpenCode
Add to ~/.config/opencode/opencode.jsonc:
{
"mcp": {
"memory": {
"type": "local",
"command": ["bunx", "@renzynx/memory-mcp"]
}
}
}Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["@renzynx/memory-mcp"]
}
}
}Tools
save_memory
Store information with a category.
save_memory(content: string, category: string)Categories: preferences, facts, context, projects, conventions
search_memories
Fuzzy search stored memories. Returns TOON format or Ø if empty.
search_memories(query: string)list_categories
List all unique categories. Returns TOON format or Ø if empty.
list_categories()Agent Instructions
Add to your agent system prompt:
## Memory System
You have access to a persistent memory system via MCP tools. Use it proactively to remember important information across sessions.
### Tools Available
- `save_memory(content, category)` - Store information with a category
- `search_memories(query)` - Fuzzy search (supports partial matches like "pyth" → "python")
- `list_categories()` - View all memory categories
### When to Save Memories
- User preferences (coding style, tools, frameworks, communication preferences)
- Project context (architecture decisions, file structures, conventions)
- Facts about the user (name, role, team, timezone)
- Recurring tasks or workflows
- Corrections or clarifications the user provides
- Important decisions and their rationale
### Categories to Use
- `preferences` - User preferences and settings
- `facts` - Information about the user or their environment
- `projects` - Project-specific context and decisions
- `conventions` - Coding standards and patterns
- `context` - Session or task context worth preserving
### When to Search Memories
- At the start of conversations to recall user context
- Before making assumptions about preferences
- When the user references something previously discussed
- Before suggesting tools, patterns, or approaches
### Output Format
Results return in TOON format for token efficiency. "Ø" means no results found.
### Best Practices
- Save incrementally, not everything at once
- Use specific, searchable content
- Search before asking the user to repeat themselves
- Update memories when information changes (save new version)License
MIT
Available Tools
3 toolslist_categoriesA
List all unique memory categories. Returns TOON-formatted list or 'Ø' if empty.
Inputs: no named parameters.
save_memoryA
Persist a memory with categorization. Use for storing facts, preferences, context, or any information that should be recalled later.
Inputs: content (required), category (required).
search_memoriesA
Search stored memories using fuzzy substring matching. Supports partial words and phrases. Returns results in TOON format for token efficiency. Returns 'Ø' if no matches.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: storing memories, searching them, and listing categories. There is no functional overlap between the three operations.
All tool names follow a predictable verb_noun snake_case pattern: save_memory, search_memories, list_categories. The singular/plural noun variation is natural and does not create confusion.
Three tools is a minimal but well-scoped set for a focused memory server. Each tool covers a distinct core operation without unnecessary bloat.
The server supports saving, searching, and listing categories, but lacks update and delete operations for memories. This creates a notable lifecycle gap where incorrect or obsolete memories cannot be corrected or removed.
Maintenance
Related MCP Connectors
Cloud-hosted MCP server for durable AI memory
Persistent, verbatim, searchable memory for AI assistants — one memory across every MCP client.
Token-efficient MCP memory for Markdown vaults. Tiered search, GraphRAG, AI memories.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenancePersistent memory MCP server for AI coding agents. Stores, searches, and retrieves context across sessions using SQLite and FTS5.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing persistent memory management for AI agents using SQLite and FTS5, enabling storage, full-text search, and recall of memories with namespace isolation.1MIT
- AlicenseAqualityNot gradedmaintenancePersistent memory MCP server for AI agents, using SQLite with hybrid keyword and semantic search for long-term memory storage.5Do What The F*ck You Want To Public

hive-memoryofficial
FlicenseNot gradedqualityDmaintenanceMCP server for personal and shared memory with full-text search (SQLite FTS5) and outcome tracking, compatible with any MCP agent like Claude Code, Cursor, and Codex CLI.-