fastmcp-sqlite
Related Servers
Alternatives to fastmcp-sqlite
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server enabling natural-language querying of SQLite databases via schema discovery, GraphRAG retrieval, and safely guarded read-only SQL execution.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides safe, read-only access to SQLite databases through MCP. This server is built with the FastMCP framework, which enables LLMs to explore and query SQLite databases with built-in safety features and query validation.108-
- AlicenseAqualityDmaintenancePersistent memory MCP server with FTS5 fuzzy search, storing data in SQLite with automatic maintenance and token-efficient TOON output.310 npm1MIT
- AlicenseNot gradedqualityBmaintenanceThis MCP server autonomously introspects SQLite databases to auto-generate CRUD tools and join prompts, while enforcing zero-knowledge security through pre-validated SQL templates.MIT
- AlicenseNot gradedqualityAmaintenanceToken-efficient MCP server for MySQL, PostgreSQL, and SQLite written in Rust, providing SQL query execution and analysis tools with strong security guards.1MIT
- FlicenseAqualityAmaintenanceA FastMCP server that enables safe, read-only exploration and querying of relational databases (SQLite, PostgreSQL, MySQL) through natural language, with tools for schema inspection, query execution, plan explanation, and migration validation.75-
TDQS
Scored across 6 tools
Each tool has a clearly distinct scope: whole-database schema vs. single-table details, in-chat query results vs. file export, query plan analysis, and database file discovery. There is no meaningful overlap or ambiguity between them.
Names are readable and consistently lowercase snake_case, but they mix noun-style resource names (schema, table_info) with verb-style action names (query, export_query, explain, list_databases). A consistent verb_noun or get_/list_ pattern would improve predictability.
Six tools is a well-scoped set for a SQLite database server. Each tool serves a distinct need—exploration, querying, export, and query planning—without unnecessary duplication or bloat.
Within the apparent read/analysis-oriented scope, the tool surface is complete: it covers database discovery, schema inspection, detailed table metadata, querying, query plan explanation, and large result exports. There are no obvious dead ends or missing operations for this stated purpose.