Multi-Memory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_BASE_DIR | No | Base directory for all memory categories (default: '.aim' in current working directory) | .aim |
| DEFAULT_CATEGORY | No | Default category when none specified (default: "default") | default |
| SERIALIZATION_FORMAT | No | Output format for tool responses. 'json' (Standard JSON with 2-space indentation) or 'toon' (Token-Oriented Object Notation - compact format optimized for LLMs). Default: "json" | json |
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 |
|---|---|
| create_entitiesA | Create multiple new entities in the knowledge graph. Returns entities with their assigned IDs. Constraints: entities unique by (name, entityType); observations unique by (entity, observationType, source). Use override=true to replace existing entities. |
| create_relationsB | Create multiple new relations between entities. Each endpoint (from/to) can be specified by id OR by name/type. Returns relations with their assigned IDs. Use override=true to update existing relations. |
| add_observationsA | Add new observations to existing entities. Entity can be specified by entityId OR by entityName/entityType. Returns observation IDs. Constraint: observations unique by (entity, observationType, source). Use override=true to update existing observations. |
| delete_entitiesA | Delete entities and their relations. Specify each entity by id OR by name/entityType. |
| delete_observationsB | Delete specific observations. Specify by observation id OR by entity identifier + observationType + source. |
| delete_relationsA | Delete relations. Specify by relation id OR by entity IDs (fromId/toId/relationType) OR by entity names (from/fromType/to/toType/relationType). |
| read_graphA | Read the entire knowledge graph. Returns all entities (with IDs) and relations (with IDs). |
| search_nodesA | Full-text search with BM25 ranking. Returns matching entities sorted by relevance. Supports FTS5 query syntax: simple terms (auth), phrases ("user auth"), AND/OR/NOT operators (user AND auth), prefix matching (auth*), proximity search (NEAR(user auth, 5)). Simple queries auto-convert to prefix-matching AND search. |
| open_nodesB | Open specific entities. Specify each by id OR by name/entityType. Returns entities with their IDs. |
| list_categoriesA | List all available memory categories. |
| delete_categoryA | Delete an entire memory category and all its contents. |
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
Each tool targets a specific resource or action: entities, relations, observations, categories, graph reading, and search. The deletion tools are clearly differentiated by object type (entities, observations, relations, categories). Retrieval tools (open_nodes, read_graph, search_nodes) serve distinct purposes.
All tool names follow a verb_noun pattern with lowercase and underscores (e.g., create_entities, delete_observations). However, the verbs vary: 'add' vs 'create' for creation, and 'open' is an unusual choice for retrieval, introducing slight inconsistency.
With 11 tools, the server covers the essential operations for managing a knowledge graph (CRUD for entities, relations, observations, plus categories, graph reading, and search). The count is well within the typical 3-15 range and feels appropriate for the domain.
The tools cover create, read, delete, and search operations, but lack update functionality for entities and relations (e.g., update_entity, update_relation). Also, categories can only be listed and deleted, not created or renamed. These gaps limit completeness.