SQLite Memory
Related Servers
Alternatives to SQLite Memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive SQLite database interaction for AI agents, including data manipulation, schema inspection, and automated query logging. It features a unique context preservation pattern that uses a dedicated meta-table to help autonomous agents maintain self-documenting database architectures.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to explore and query SQLite databases through read-only tools for listing databases, inspecting tables, searching values, and running single SELECT statements. Layered defenses—static SQL parsing, read-only connections, an authorizer, query timeouts, and row caps—ensure models cannot modify data even if they try.MIT
- AlicenseAqualityDmaintenanceProvides persistent SQLite-based memory and unified tool abstraction for AI agents to support long-term context and complex tool chaining. It enables automated code analysis, file operations, and environment discovery through a standardized interface.5MIT
- AlicenseAqualityCmaintenanceEnables AI agents to explore and query SQLite databases through read-only, sandboxed tools for listing tables, describing schemas, fetching DDL, and running a single capped SELECT statement. Also supports plain-English questions that are converted to SQL and routed through the same sandbox.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to safely work with SQLite databases by enforcing read/write separation, dry-run writes with confirmation, automatic backups, and an audit trail.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an LLM to explore and query a SQLite database through tools for listing tables, describing schemas, sampling rows, and running bounded read-only SELECT queries, with table/column restrictions, resource limits, and audit logging.MIT
TDQS
Scored across 12 tools
Each tool has a clearly distinct role: the three query tools are separated by intent (read/write/destructive), and the introspection trio (list_tables, describe_table, get_schema) differs by granularity. Memory tools (checkpoint, append_event, get_resume_context, verify_chain) are distinguishable by write-vs-read purpose.
Most names follow a verb_noun pattern (read_query, write_query, list_tables, describe_table, get_schema, create_view, append_event, verify_chain, search_text). Exceptions are 'checkpoint' (bare noun) and 'destructive_query' (adjective_noun), but both remain readable and predictable.
12 tools is well-scoped for a SQLite memory store that also exposes generic DB operations. Every tool earns its place with no redundancy.
Full lifecycle coverage: read/write/destructive queries, schema introspection, view creation, plus a hash-chained memory log with append, checkpoint, resume, and verification. search_text adds value beyond SQL, and destructive_query covers drops/alters, leaving no obvious gaps.