litescope
Related Servers
Alternatives to litescope
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to inspect and operate SQLite, PostgreSQL, MySQL/MariaDB, Oracle, SQL Server and MongoDB through 16 tools covering schema discovery, parameterized SQL reads and transactions, MongoDB document operations, and concurrent hybrid SQL/MongoDB queries. Runs locally over stdio or loopback HTTP with pooled connections, bounded concurrency, row and response limits, and read-only defaults.16MIT
- AlicenseNot gradedqualityBmaintenanceMCP servers for SQL databases. One package per engine (SQLite, libSQL, MySQL, MariaDB, Postgres), two tools, read-only by default, secrets never in logs.5MIT
- AlicenseNot gradedqualityDmaintenanceProvides a set of MCP tools to let AI assistants like Claude, Cursor, and VS Code Copilot interact with SQLite databases, supporting querying, schema management, and data import/export.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceA universal SQLite database management tool that enables SQL query execution through MCP protocol. Supports SELECT/INSERT/UPDATE/DELETE/CREATE operations with built-in SQL injection protection across stdio, SSE, and streamable-http communication modes.MIT
- AlicenseNot gradedqualityCmaintenanceRead-only SQLite access for AI agents in a single ~1 MB static binary. Query tool with row limits, list_tables, and table schemas exposed as MCP resources. The database is opened read-only, so writes fail at the SQLite layer. No Python, no Node, no runtime to install; SQLite is compiled in. Binaries for Linux, macOS, and Windows.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server (stdio) that exposes schema-exploration tools and a natural-language ask tool, letting other AI apps list tables, describe them, sample rows, and run guarded, read-only SQL against SQLite or DuckDB databases.MIT
TDQS
Scored across 14 tools
Most tools target clearly distinct concerns (health, locks, advise, schema, query, diff, migrate_plan vs migrate_diff), and descriptions explicitly disambiguate near-neighbors like migrate_plan vs migrate_diff. However, the diagnostics cluster (health, fleet_health, locks, advise) shares substantial conceptual overlap, and the distinction between single-db health and advise requires reading the descriptions carefully.
All tools share a consistent litescope_ prefix and snake_case convention, with several clear verb_noun names (migrate_plan, snapshot_list, d1_list, fleet_health). A few names are bare nouns/verbs (health, schema, locks, advise, query, diff, fingerprint), which is readable but slightly less predictable than a uniform verb_noun pattern.
14 tools is well within a healthy range and each covers a distinct facet of the SQLite/D1 lifecycle: diagnostics, schema exploration, migration planning, fleet analysis, snapshots, and backup verification. No tool appears redundant or filler.
The read-only diagnostic surface is broad and coherent, but the toolset has dead ends: litescope_migrate_diff references a litescope_migrate_apply that is absent, and descriptions mention litescope_snapshot (create) and litescope_restore which are not in the set. An agent can plan migrations and inspect snapshots but cannot apply migrations or create/restore backups, which will cause workflow failures.