Memex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMEX_VAULT | Yes | Absolute path to the Memex vault directory (its own git repo) that the MCP server reads and writes. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Save or update a note in the user's persistent memory. Re-using a title updates that note. Pass a stable |
| recallA | Search memory. Returns up to 8 ranked hits as title, id and a short snippet. Use read_note for the full text. |
| read_noteC | Read one note's full body by id. |
| get_backlinksA | List the notes that link to the given note id via [[wikilinks]]. |
| list_notesB | List notes (id, title, project, tags), optionally filtered by project and/or tag. |
| list_tagsB | List tags with note counts, optionally within one project. |
| resolve_conflictA | Resolve a contradiction between two notes (ids from a |
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 7 tools
Each tool has a distinct role: read_note (fetch full body by id) vs recall (ranked snippet search), list_notes vs list_tags (different resources), and remember (write/update) vs resolve_conflict (deliberate contradiction workflow). The descriptions explicitly cross-reference each other (recall says 'use read_note for the full text'; remember's warnings feed resolve_conflict), so an agent can pick correctly.
Four tools follow a verb_noun pattern (read_note, get_backlinks, list_notes, list_tags) and all names are uniformly snake_case. The three memory-lifecycle tools use bare verbs (remember, recall, resolve_conflict), which is a minor but readable deviation rather than inconsistency.
Seven tools is well-scoped for a personal notes/memory server, and each earns its place: read, write, search, list, list tags, backlinks, and conflict resolution. No redundant or filler tools are present.
The surface covers the full read/write/search/update lifecycle plus backlinks and explicit conflict resolution, with supersede semantics substituting for deletion. Minor gaps remain: there is no 'forget'/delete operation at all, and no way to list a note's outgoing links (only backlinks), which agents may want for graph navigation.