memex-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMEX_MEMORY_ROOT | No | Root directory for storing memories. Defaults to ~/.memex/memory |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_memoryA | Create a durable markdown memory for facts, decisions, preferences, or project context that should survive beyond the current chat. |
| get_memoryB | Retrieve a memory note by id and return its complete markdown with YAML frontmatter. |
| append_memoryA | Append new markdown to an existing memory while preserving its current content and updating the modified timestamp. |
| update_memoryA | Patch memory metadata and optionally replace the full markdown body. Use append_memory when adding incremental observations. |
| archive_memoryA | Mark a memory as archived without deleting its markdown file. |
| delete_memoryA | Permanently delete a memory note by id. |
| list_memoriesA | List memory metadata for browsing or filtering without returning full note bodies. Use search_memory when you need relevance ranking. |
| search_memoryA | Search durable memories with relevance ranking over title, aliases, tags, path, description, and body terms. |
| build_memory_indexB | Build or refresh the human-readable markdown memory index at index.md. |
| rebuild_memoryA | Repair and rebuild the memory store: optionally fix frontmatter, apply or normalize wikilinks from memory titles and aliases using longest matches first, then rebuild index.md and index.yaml. |
| load_memory_indexB | Load the generated markdown memory index, optionally refreshing it first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: create, read, update, delete, archive, search, and index operations are all separate, with no overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_memory, search_memory), making them predictable and easy to understand.
11 tools is appropriate for a memory management server, covering essential operations without unnecessary bloat.
The tool set provides full lifecycle management: create, read (get, list, search), update (append, update, rebuild), delete, archive, and index operations, with no obvious gaps.