Changes Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHANGES_MEMORY_PATH | No | Backward compatibility: forces an exact file path for default project memory. Equivalent to --memory-path. | |
| CHANGES_MEMORY_ROOT | No | Backward compatibility: default project path. Equivalent to --memory-root. | |
| CHANGES_MEMORY_GLOBAL_PATH | No | Exact file path for global memory. Equivalent to --global-path. | |
| CHANGES_MEMORY_PROJECT_PATH | No | Default project path when a tool call does not pass projectPath. Equivalent to --project-path. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_localB | Guarda una nueva correccion o criterio aprendido en la memoria del proyecto. |
| add_globalC | Guarda una correccion o criterio transversal en la memoria global. |
| list_changesA | Lista los cambios guardados en la memoria del proyecto y la global. |
| list_change_indexA | Lista un indice compacto de cambios con id, titulo, store, tipo, tags y rutas para decidir que consultar despues. |
| list_tag_catalogA | Lista el catalogo recomendado de tags para usar al guardar memoria con add_local o add_global. |
| get_changeA | Recupera un cambio exacto por id |
| search_changesB | Busca cambios por texto libre |
| get_relevant_changesB | Devuelve los cambios mas relevantes para una tarea o riesgo concreto |
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 8 tools
Most tools are clearly distinct, but list_changes and list_change_index both list changes, and search_changes vs get_relevant_changes could overlap. Descriptions help clarify the intended use cases, so the ambiguity is limited.
All tool names follow a consistent verb-first snake_case pattern (e.g., add_local, search_changes, get_change). The add_local/add_global pair uses a predictable scope suffix, and the naming aligns well across the set.
With 8 tools, the server is well-scoped for a memory management system. Each tool serves a clear purpose, and the count is within the expected range to avoid unnecessary complexity.
The server covers creation, retrieval, search, and listing, but lacks update and delete operations for changes. Without these, correcting or removing stored memories is not possible, which is a notable gap in lifecycle coverage.