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.314 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
- AlicenseAqualityBmaintenanceRead-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.6MIT
- 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
Most tools target distinct resources and actions, with a clear progression from list_tables to describe_table to query. Some overlap exists in the reporting cluster (list_recordings, history, recording_report, check, compare), but the descriptions largely disambiguate them.
The set is mostly consistent verb_noun naming (list_recordings, describe_table, get_finding, explain_rule, record_command). The single-word names query, check, compare, and history are minor deviations but still readable and conventional for their actions.
Fourteen tools is well within a reasonable range for a database health-check and query server. Each tool appears to earn its place across discovery, querying, checking, and reporting workflows.
The surface covers profile/database/table discovery, querying, health checks, history, findings, rule explanation, recordings, and comparisons. Minor gaps remain around creating or editing profiles and managing recordings directly, though users can work around these via the external registration/recording flow.