codeDB Lens
OfficialRelated Servers
Alternatives to codeDB Lens
- AlicenseAqualityCmaintenanceRead-only MySQL/MariaDB MCP server for running SELECT queries safely, with automatic read-only enforcement and query limits.34 npmMIT
- AlicenseAqualityDmaintenanceEnables natural language to SQL queries on MSSQL databases via Claude, with safe SELECT-only execution and schema discovery.3ISC
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with SQL Server databases through tools for connectivity, schema exploration, SQL queries, and OEE metrics analysis.-
- FlicenseNot gradedqualityDmaintenanceEnables querying and inspecting a PostgreSQL database, including executing SQL queries, listing schemas and tables, and describing table columns.-
Related Servers
- AlicenseNot gradedqualityFmaintenanceRead-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.MIT
- FlicenseAqualityDmaintenanceA read-only MCP server for SQL Server and PostgreSQL that enables exploring and querying databases (schemas, tables, views, procedures, indexes, foreign keys) and running arbitrary SELECT queries.37-
- AlicenseNot gradedqualityBmaintenanceA safe, read-only MCP server for local development databases (PostgreSQL and SQLite) that provides guarded introspection tools like schema listing, sample rows, and explain plans with column masking and query budgets.MIT
- AlicenseAqualityBmaintenanceSQL Server MCP server with AST-based query validation, read-only safety, schema exploration, ER diagram generation, and DBA toolkit integration (First Responder Kit, DarlingData, sp_WhoIsActive).128MIT
- AlicenseAqualityAmaintenanceRead-only PostgreSQL performance auditing via MCP. Collects metrics from PostgreSQL system views, applies deterministic checks for index, query, vacuum, configuration, and connection issues, and returns structured findings for MCP clients.5MIT
- AlicenseNot gradedqualityDmaintenanceProvides a read-only PostgreSQL MCP server with schema introspection. Enforces least-privilege database roles to prevent any writes, even from malicious SQL.MIT
TDQS
Scored across 14 tools
The set forms a clear hierarchy (list_databases → list_tables → describe_table → query) and the analysis tools (check, history, compare, get_finding) are well separated. Two minor overlaps remain: get_finding vs explain_rule both return 'detail of a rule' (instance evidence vs rule definition), and check vs recording_report both produce analyses, though the descriptions do distinguish them.
A majority use verb_noun (list_tables, describe_table, explain_rule, get_finding, record_command), giving a recognizable pattern. But single bare words (check, compare, query, history) and a noun_noun (recording_report) break it, making it mixed though still readable.
14 tools is squarely in the well-scoped range, and each maps to a distinct step in the DB health-check workflow (discover, inspect, query, check, review, record). Nothing appears redundant or padding.
Covers schema exploration, read-only querying, rule catalog, health checks, run history/compare, and recordings — a full read/analyze lifecycle. Minor gaps: no profile create/edit/delete (presumably managed in the app) and no rule search/filter, but agents can work around these.