io.github.Umarjaum/repo-memory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| remember_correctionB | Store a correction or lesson learned during development. Use for durable guidance that should prevent repeated mistakes; do not store credentials, secrets, or transient chat context. |
| remember_ruleA | Store a durable repository-specific rule or convention. Use when the agent should follow a project constraint in future sessions. |
| remember_decisionB | Store an architectural or implementation decision together with its rationale. |
| recall_memoryA | Search active repository memories using deterministic local relevance scoring across topic, content, tags, context, and type. |
| get_startup_contextC | Return a concise startup context prioritizing critical and high-importance rules, conventions, decisions, and recent corrections. |
| list_project_rulesA | List all active durable project rules for the current repository. |
| list_memoriesB | List repository memories with optional type and status filters. |
| update_memoryA | Update an existing memory by ID. This changes the existing record and timestamp; it never silently creates a replacement. |
| forget_memoryA | Archive a memory so it is retained for auditability but excluded from normal recall and startup context. |
| export_memoryC | Export all active and archived memories as portable JSON to a user-specified path. |
| import_memoryA | Import a JSON export without overwriting existing memories; malformed records are rejected and duplicates are reported. |
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
Most tools have clearly distinct roles, but the remember_correction / remember_rule / remember_decision trio and list_project_rules overlapping list_memories create minor ambiguity. The descriptions explain the differences well enough for an agent to choose correctly.
All tool names follow a consistent snake_case verb_noun pattern: list_, update_, forget_, remember_, recall_, get_, export_, import_. The memory-themed vocabulary is coherent and predictable.
11 tools is well-scoped for a repository memory system: create variants, read/search, update, archive, export/import, and startup context. Each tool earns its place and the set does not feel bloated.
The surface covers create, read, search, update, archive, export, import, and startup context. The main gap is no explicit restore/unarchive operation for archived memories, but this can likely be worked around via update_memory or export data.