sqlite-memory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE_REPO | No | Path to the bridge git repository. Only needed for bridge/collab flows. | |
| SQLITE_MEMORY_DB | No | Path to the SQLite database file. Defaults to ~/.claude/memory/memory.db. | ~/.claude/memory/memory.db |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_entitiesA | Create new entities in the knowledge graph. Each entity dict has: name (str), entityType (str), observations (list[str]). Optional: project (str). Duplicates are silently ignored. |
| add_observationsA | Add new observations to existing entities. Each dict has: entityName (str), contents (list[str]). Duplicate observations are silently ignored. |
| create_relationsA | Create relations between entities in the knowledge graph. Each dict has: from (str), to (str), relationType (str). Duplicate relations are silently ignored. |
| delete_entitiesA | Delete entities and their associated observations and relations (CASCADE). Also cleans up the FTS index. |
| delete_observationsA | Delete specific observations from entities. Each dict has: entityName (str), observations (list[str]). |
| delete_relationsA | Delete specific relations from the knowledge graph. Each dict has: from (str), to (str), relationType (str). |
| read_graphA | Read the full knowledge graph with pagination. Returns JSON: {entities: [{name, entityType, observations: [...]}], relations: [{from, to, relationType}], total: int, has_more: bool} |
| search_nodesA | Search the knowledge graph using hybrid BM25 + semantic search. When sqlite-vec is installed, combines FTS5 keyword matching with vector cosine similarity via Reciprocal Rank Fusion. Falls back to FTS5-only otherwise. Results are re-ranked with 6 contextual signals (recency, project affinity, graph proximity, richness, canonical facts, session). |
| open_nodesB | Open specific entities and retrieve their inter-relations. Returns the requested entities with observations and all relations that exist between them. |
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
Each tool targets a distinct operation on a specific resource (entities, observations, relations, graph). No overlapping functionality.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_entities, delete_observations, search_nodes), making it predictable.
9 tools cover the core operations for a knowledge graph memory system without being excessive or insufficient.
Missing update/modify operations for entities and relations; only create, read, delete are present, which is a notable gap for full lifecycle management.