sqldb-mcp-server
Related Servers
Alternatives to sqldb-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA configurable, database-agnostic MCP server that enables LLMs to safely interact with SQL databases through read-only operations and schema inspection.-
- AlicenseNot gradedqualityAmaintenanceMCP server for safely exposing SQL Server database capabilities to LLM clients, with read-only mode, security features, and observability.28MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that enables LLMs to safely explore and query any SQLite database via natural language. It exposes tools for listing tables, describing schemas, and executing SELECT/WITH queries with built-in safety guards like write prevention and row limits.MIT
- FlicenseNot gradedqualityCmaintenanceA read-only MCP server that lets LLMs explore SQLite databases in plain English, with enforced write protection and sensitive column redaction.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides safe, read-only SQL access for AI agents to query databases (PostgreSQL, MySQL, SQLite) with schema awareness and guardrails.12MIT
- AlicenseAqualityCmaintenanceAn MCP server that provides safe, read-only access to a PostgreSQL warehouse, enabling schema introspection, guarded SQL queries, and truncated result reporting for LLMs.3MIT
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: listing tables, describing one table, running queries, explaining query plans, exporting results, and saving evidence. However, 'query' and 'saveQueryEvidence' both execute SQL queries, which could cause minor confusion if descriptions are not carefully read.
All tool names follow a camelCase pattern with verb+noun, e.g., 'describeTable', 'listTables', 'exportQuery'. The name 'query' is a single word and slightly generic compared to the others, but overall the pattern is consistent.
With 6 tools, the set covers essential operations for a read-only database exploration server: listing, describing, querying, explaining, exporting, and saving evidence. The number is well-scoped without unnecessary bloat.
For a read-only database tool, the set is largely complete. It covers table metadata, query execution, plan analysis, and result export. Minor gaps include missing support for views, schemas, or stored procedures, but these are not critical for the core use case.