jalipata-mcp-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_DB_PATH | No | SQLite database file | ./memory/memory.db |
| MEMORY_HTTP_PORT | No | Port when transport is 'http' | 3000 |
| MEMORY_TRANSPORT | No | Transport mode: 'stdio' or 'http' | stdio |
| MEMORY_SERVER_NAME | No | Server name advertised over MCP | jalipata-memory |
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": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_entitiesA | Create multiple new entities in the knowledge graph. Entities with an existing name are ignored. |
| create_relationsA | Create multiple new relations between entities. Relations should be in active voice. Missing endpoint entities are created automatically. |
| add_observationsA | Add new observations (atomic facts) to existing entities in the knowledge graph. Fails if an entity does not exist. |
| delete_entitiesA | Delete entities and their associated relations and observations from the knowledge graph (cascading). Silent if an entity does not exist. |
| delete_observationsA | Delete specific observations from entities in the knowledge graph. Silent if an observation does not exist. |
| delete_relationsA | Delete specific relations from the knowledge graph. Silent if a relation does not exist. |
| read_graphA | Read the entire knowledge graph for a namespace, including all entities and relations. |
| search_nodesA | Keyword search for nodes in the knowledge graph by entity names, entity types, and observation content. Returns matching entities and their connected relations. |
| open_nodesA | Retrieve specific nodes by name, along with relations connected to them. Silently skips non-existent nodes. |
| list_namespacesA | List all memory namespaces (scopes) stored in this server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| memory-guidance | Instructions that teach the model how to use the memory knowledge graph (retrieve, store, and maintain memories across conversations). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| namespaces | List of all memory namespaces known to this server |
TDQS
Scored across 10 tools
Each tool targets a distinct operation: creating entities, creating relations, adding observations, and deleting each of those, plus distinct retrieval methods (read graph, search, open by name) and namespace listing. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun snake_case pattern (create_entities, delete_relations, open_nodes, etc.). The only slight variation is 'add_observations' versus 'create_*', but 'add' is still a clear active verb in the same style.
With 10 tools, the server is well-scoped for a knowledge graph memory system. Each tool covers a essential operation without redundancy, and the count is within the ideal range for a focused server.
The surface covers the full CRUD lifecycle for entities, relations, and observations, plus retrieval and namespace listing. Minor gaps exist such as no update/rename operation for entities or relations, but these are not critical for typical memory graph workflows.