repo-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPO_MEMORY_ROOT | No | Absolute path to the repository root. Alternative to --repo argument. |
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 |
|---|---|
| get_repo_memoryA | Return the entire Args: fact_limit: cap on number of facts (default 50, most recent first). |
| add_factA | Record a structured fact you just verified about this codebase, so the next agent (or your next session) doesn't have to re-verify it. Args: claim: the factual statement (one sentence). file: source file path (relative to repo root) that proves the claim. lines: line range like '42' or '42-50'. tool: name of tool used to verify ('grep', 'read', 'bash', etc.). command: exact command if reproducible. tags: optional tags for later filtering. |
| list_factsA | List recorded facts, optionally filtered. Useful when you want only facts relevant to a specific area before reading them. |
| add_decisionB | Record a non-trivial decision made while working in this repo
(architecture choice, trade-off, deprecation, etc.) as a markdown file
under Args: title: one-line headline of the decision. body: full markdown explanation — context, options considered, reasoning, who/when. |
| add_gotchaA | Append a one-line 'watch out for X' note to |
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 purpose: recording decisions, facts, gotchas, retrieving all memory, or listing facts. No overlapping functionality.
All tools follow a consistent verb_noun snake_case pattern (add_decision, add_fact, add_gotcha, get_repo_memory, list_facts).
Five tools is well-scoped for a memory server covering add and retrieve operations without excess or insufficiency.
Covers adding and retrieving decisions, facts, and gotchas. However, lacks update or delete functionality, which would be useful for managing memory.