<h2 align="center">Self-hosted MCP memory server for personal use and teams</h4>
Most knowledge and memory work still happens through a UI a human drives. Memlord MCP server moves it into the conversation instead. Self-hosted MCP memory server for personal use and teams.
The server publishes 11 tools. What each one is for:
store_memory — Save a memory (idempotent by content); raises on near-duplicates; optional expires_atretrieve_memory — Hybrid semantic + full-text search; returns snippets by defaultrecall_memory — Search by natural-language time expression; returns snippets by defaultlist_memories — Paginated list with type/tag filterssearch_by_tag — AND/OR tag searchget_memory — Fetch a single memory by name with full content (expired included)update_memory — Update content, type, tags, metadata, or expiry by name (and optionally rename)delete_memory — Delete by namemove_memory — Move a memory to a different workspacelist_workspaces — List workspaces you are a member of (including personal)dream_report — Read-only consolidation candidates: similar memory pairs, expired and expiring-soon memoriesBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: MEMLORD_DB_URL, MEMLORD_BASE_URL, MEMLORD_OAUTH_JWT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Memlord's toolset — store_memory, retrieve_memory, recall_memory and 8 more — is a fair guide to whether it matches your workflow. It is maintained by myrikld; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Memlord's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| store_memory | Save a memory (idempotent by content); raises on near-duplicates; optional expires_at |
| retrieve_memory | Hybrid semantic + full-text search; returns snippets by default |
| recall_memory | Search by natural-language time expression; returns snippets by default |
| list_memories | Paginated list with type/tag filters |
| search_by_tag | AND/OR tag search |
| get_memory | Fetch a single memory by name with full content (expired included) |
| update_memory | Update content, type, tags, metadata, or expiry by name (and optionally rename) |
| delete_memory | Delete by name |
| move_memory | Move a memory to a different workspace |
| list_workspaces | List workspaces you are a member of (including personal) |
| dream_report | Read-only consolidation candidates: similar memory pairs, expired and expiring-soon memories |
| Variable | Description | Required |
|---|---|---|
| MEMLORD_DB_URL | Endpoint or connection string the server talks to. | Yes |
| MEMLORD_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| MEMLORD_OAUTH_JWT_SECRET | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.