memanchor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMANCHOR_DB | No | Override the location of the memories database (default is ~/.memanchor/memory.db). | |
| MEMANCHOR_PROJECT | No | The project git repository path. The project is the git repository of the directory the server starts in. If your client starts servers elsewhere, set MEMANCHOR_PROJECT=/path/to/repo. |
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 something future sessions on this project should know: a decision and why, a convention, a gotcha, a fact or a todo. Keep it to one self-contained statement. Identical memories are updated, not duplicated. |
| recallA | Search this project's memories by keywords (BM25 full-text search). Call at the start of a task. Omit query to get the most recent memories. Results flagged STALE refer to files that changed since. |
| confirm_memoryA | Mark a stale memory as still correct after re-checking the code. Re-anchors it to the current files. |
| forgetA | Delete a memory that is wrong or no longer applies. |
| list_memoriesA | List all memories for this project, optionally only one kind or only stale ones (for cleanup). |
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 5 tools
Each tool has a distinct action: remember creates/updates, recall searches, confirm_memory re-anchors stale entries, forget deletes, and list_memories enumerates/filters. The boundary between recall and list_memories is clear because one is keyword search and the other is full listing with kind/staleness filters.
All names use lowercase snake_case and are verb-oriented, but remember/recall/forget are bare verbs while confirm_memory/list_memories follow a verb_noun pattern. The inconsistency is minor and still readable.
Five tools is well-scoped for a project-memory server. Each tool covers a necessary lifecycle operation without redundancy.
The surface covers the full memory lifecycle: create/update (remember), search/read (recall), list/filter (list_memories), re-validate stale entries (confirm_memory), and delete (forget). No obvious gaps remain for the stated purpose.