memento-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 | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_entitiesB | Create multiple new entities in your Memento MCP knowledge graph memory system |
| create_relationsB | Create multiple new relations between entities in your Memento MCP knowledge graph memory. Relations should be in active voice |
| add_observationsB | Add new observations to existing entities in your Memento MCP knowledge graph memory |
| delete_entitiesA | Delete multiple entities and their associated relations from your Memento MCP knowledge graph memory |
| delete_observationsB | Delete specific observations from entities in your Memento MCP knowledge graph memory |
| delete_relationsB | Delete multiple relations from your Memento MCP knowledge graph memory |
| get_relationB | Get a specific relation with its enhanced properties from your Memento MCP knowledge graph memory |
| update_relationB | Update an existing relation with enhanced properties in your Memento MCP knowledge graph memory |
| read_graphA | Read the entire Memento MCP knowledge graph memory system |
| search_nodesB | Search for nodes in your Memento MCP knowledge graph memory based on a query |
| open_nodesB | Open specific nodes in your Memento MCP knowledge graph memory by their names |
| semantic_searchB | Search for entities semantically using vector embeddings and similarity in your Memento MCP knowledge graph memory |
| get_entity_embeddingA | Get the vector embedding for a specific entity from your Memento MCP knowledge graph memory |
| get_entity_historyA | Get the version history of an entity from your Memento MCP knowledge graph memory |
| get_relation_historyB | Get the version history of a relation from your Memento MCP knowledge graph memory |
| get_graph_at_timeA | Get your Memento MCP knowledge graph memory as it existed at a specific point in time |
| get_decayed_graphA | Get your Memento MCP knowledge graph memory with confidence values decayed based on time |
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 17 tools
Each tool has a clearly distinct purpose: CRUD operations for entities, relations, and observations are separated, and specialized tools for history, embeddings, and time-specific queries do not overlap. No ambiguity between tool functions.
All tool names follow a consistent verb_noun pattern (e.g., create_entities, delete_observations, get_entity_history). The naming is uniform and predictable, aiding agent selection.
With 17 tools, the count is slightly above the ideal 3-15 range but still well-scoped for a knowledge graph system. Each tool addresses a specific need, though a few could potentially be consolidated.
The tool surface covers most CRUD operations but lacks an update_entity tool and a dedicated get_entity (though open_nodes and read_graph partially fill this). Missing update for observations. These gaps may cause some workflow interruptions.