sqlite-memory-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_writeC | Write a memory entry to the knowledge base |
| memory_readA | Read a specific memory entry by key |
| memory_searchB | Search memories using full-text search (FTS5) |
| memory_listC | List memory entries with optional filters |
| memory_deleteB | Delete a memory entry |
| memory_statsC | Get memory statistics |
| context_setB | Set a context value for cross-skill state sharing |
| context_getC | Get a context value |
| context_listA | List all context values for a session |
| context_clearC | Clear context values |
| context_shareC | Share context from one session to another |
| skill_registerC | Register a skill installation |
| skill_getC | Get skill information |
| skill_listA | List all registered skills |
| skill_usage_startC | Start tracking skill usage |
| skill_usage_endC | End skill usage tracking |
| skill_recommendC | Get skill recommendations based on project type and success rates |
| skill_statsB | Get skill usage statistics |
| failure_recordC | Record a failure experience for future reference |
| failure_searchB | Search for failure experiences and solutions using FTS5 |
| failure_listC | List failure experiences |
| failure_updateB | Update a failure record with a solution |
| failure_statsC | Get failure statistics |
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 23 tools
Tools are grouped into clear domains: context, memory, skill, and failure, which makes their purposes generally obvious. A few retrieval tools like memory_read, memory_list, and memory_search have overlapping connotations, but their descriptions specify distinct lookup modes.
All tool names follow a consistent lowercase snake_case verb_noun pattern, such as memory_write, context_set, skill_register, and failure_record. Each domain uses predictable verbs, so the naming convention is uniform and scannable.
23 tools is on the higher end and feels slightly heavy, but the server covers four distinct subdomains that each need CRUD, search, and stats operations. The count is reasonable given the combined scope, though it could be tightened.
Each core domain has solid coverage: create, read, list, search, and delete/update where expected. Minor gaps exist, such as no memory update, no single-key context delete, and no skill unregister, but agents can generally work around these.