SQLite Project Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SQLITE_MCP_DB_PATH | No | Override the SQLite database file path. The default database path is data/project_memory.db under the repository root. | |
| SQLITE_MCP_TRANSPORT | No | The transport protocol to use, either 'stdio' or 'streamable-http'. | |
| SQLITE_MCP_EXPORT_DIR | No | The default output directory for generated markdown views. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_contextA | Return the current project root, DB path, and export directory. |
| set_project_rootB | Switch project context (root + db + export path) and reconnect database. |
| server_infoB | Return server metadata and schema settings. |
| create_entityC | Create a new authoritative project entity. |
| upsert_entityC | Create an entity if missing or merge updates into an existing entity. |
| update_entityC | Update an existing entity's top-level state. |
| append_contentD | Add a piece of content to an entity. |
| archive_entityA | Archive an entity without deleting its history or related project memory. |
| delete_entityA | Delete an entity with guardrails; non-forced deletion requires prior archiving and no critical dependents. |
| merge_entitiesB | Merge a duplicate source entity into a target entity with deterministic conflict handling. |
| get_entityC | Fetch an entity and optionally include related metadata, content, and events. |
| list_entitiesC | List entities with optional type, status, attribute, tag, and text filters. |
| find_similar_entitiesB | Find likely duplicate or related entities before creating a new one. |
| resolve_entity_by_nameC | Resolve a human-readable name to an existing entity when possible. |
| get_or_create_entityB | Reuse an exact entity when it already exists or create one with a generated stable id. |
| upsert_attributesB | Create or update flexible metadata for an entity. |
| set_tagsC | Set or merge tag labels for an entity. |
| add_relationshipC | Create a typed graph edge between two entities. |
| connect_entitiesC | Create a relationship if missing, otherwise return the existing edge. |
| delete_relationshipB | Delete a relationship by id and record the removal in project history. |
| list_relationshipsC | List graph edges, optionally constrained to an entity and direction. |
| write_contentC | Write narrative content in one unified API with append|replace semantics. |
| search_contentC | Search narrative content using FTS5 when available. |
| create_snapshotC | Create a named snapshot of current project state. |
| get_snapshotB | Fetch a named snapshot and its captured entities. |
| list_viewsB | List available view names for query_view discovery. |
| query_viewB | Query a named SQL view for generic reporting and model projections. |
| get_database_healthB | Report likely duplicates, low-quality records, and retention pressure in project memory. |
| refresh_task_summaryB | Rebuild a task summary materialized table for faster open task queries. |
| apply_performance_tuningC | Tune SQLite settings for throughput during heavy project-memory workloads. |
| get_decision_logB | Return decisions and recent supporting note excerpts without requiring ad hoc SQL. |
| get_architecture_summaryB | Return a compact architecture-oriented node and relationship summary. |
| get_recent_reasoningC | Return recent reasoning excerpts for quick AI context recovery. |
| get_dependency_viewC | Return dependency-oriented graph data with stable compact fields. |
| get_recent_activityC | Return recent entities, content, and events to help an AI resume context quickly. |
| prune_content_retentionC | Prune older reasoning/log content while keeping the most recent records per entity and type. |
| get_entity_graphC | Traverse outward relationship dependencies from an entity. |
| bootstrap_project_memoryC | Initialize a project root entity and standard memory-area anchor entities. |
| run_read_queryC | Run a constrained read-only SQL query for diagnostics, analytics, and ad hoc retrieval. |
| render_markdown_viewsA | Render markdown document views only after an explicit user request for a human-readable artifact. |
| export_markdown_viewsB | Write generated markdown views only after an explicit user request for a human-readable artifact. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| project_memory_policy | Guide an AI to store project memory cleanly and avoid data pollution. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 41 tools
The tools cover distinct operations like entity management, graph relationships, content handling, and queries, but there is notable overlap in some areas. For example, create_entity, get_or_create_entity, and upsert_entity have overlapping purposes for entity creation, and append_content vs. write_content could cause confusion in content addition. Descriptions help clarify, but agents might misselect between these similar tools.
Most tools follow a consistent verb_noun or verb_adjective_noun pattern (e.g., create_entity, list_entities, get_entity_graph), with clear and descriptive names. There are minor deviations like server_info (noun_verb) and apply_performance_tuning (verb_noun_noun), but overall the naming is predictable and readable across the set.
With 41 tools, the count is excessive for a project memory server, leading to potential cognitive overload and inefficiency. While the domain is broad, many tools could be consolidated or streamlined (e.g., multiple entity creation tools, overlapping content tools), making it feel heavy and less well-scoped than ideal for agent use.
The tool set provides comprehensive coverage for project memory management, including full CRUD operations for entities and relationships, content handling, graph traversal, queries, snapshots, health checks, and context management. There are no obvious gaps; agents can perform all core workflows from initialization to archiving and reporting without dead ends.