MCP Memory Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_entitiesB | Create multiple new entities in the knowledge graph |
| create_relationsB | Create multiple new relations between entities in the knowledge graph. Relations should be in active voice |
| add_observationsB | Add new observations to existing entities in the knowledge graph |
| delete_entitiesA | Delete multiple entities and their associated relations from the knowledge graph |
| delete_observationsB | Delete specific observations from entities in the knowledge graph |
| delete_relationsA | Delete multiple relations from the knowledge graph |
| read_graphB | Read the entire knowledge graph |
| search_nodesC | Search for nodes in the knowledge graph based on a query |
| open_nodesC | Open specific nodes in the knowledge graph by their names |
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 9 tools
Most tools have distinct purposes focused on specific operations in the knowledge graph (e.g., create_entities vs. delete_entities, add_observations vs. delete_observations). However, 'open_nodes' and 'search_nodes' could potentially overlap in function—both involve accessing nodes, though 'open_nodes' seems to target specific nodes by name while 'search_nodes' uses queries, which might cause some confusion for an agent.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_observations, create_entities, delete_relations). The verbs are clear and descriptive, and there are no deviations in naming conventions across the set, making it predictable and easy to understand.
With 9 tools, this server is well-scoped for managing a knowledge graph, covering key operations like creation, deletion, reading, and searching. The count is appropriate for the domain, providing a comprehensive set without being overwhelming or too sparse.
The tool set offers strong coverage for knowledge graph management, including CRUD operations for entities, relations, and observations, plus utilities for reading and searching. A minor gap is the lack of update tools (e.g., update_entities or update_relations), which might require workarounds, but core workflows are well-supported.