@dudqls816/database-mcp
Related Servers
Alternatives to @dudqls816/database-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for safely exposing SQL Server database capabilities to LLM clients, with read-only mode, security features, and observability.28MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Microsoft SQL Server enabling safe read-only queries, schema discovery, and natural-language query via LangChain.MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for Microsoft SQL Server that enables AI agents to safely explore and query SQL Server databases.571 npmMIT
- AlicenseBqualityDmaintenanceAn MCP server that connects AI assistants to Microsoft SQL Server databases, enabling schema exploration and read-only queries safely.499 npm4MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes SQL Server databases to Claude, allowing natural language queries with tools to list tables, describe schemas, and run read-only SELECT statements.-
- FlicenseNot gradedqualityDmaintenanceA read-only MCP server for MS SQL Server, written in Python. Lets AI agents query your database safely — no writes, no stored procedures, no shell access.1-
TDQS
Scored across 3 tools
Each tool has a clear, distinct role: listing all tables/views, describing a specific table's schema, and executing a read-only SELECT query. There is no functional overlap.
The first two tools follow a verb_noun pattern (list_tables, describe_table), but 'query' deviates by being a single verb. Overall, the naming is readable and predictable.
With 3 tools, the set is at the lower end of the typical range but still well-scoped for a read-only database server. Each tool provides a necessary capability and none feels redundant.
For the intended read-only scope, the toolset covers schema discovery and data querying adequately. It lacks write operations and complex SQL, but these are deliberately excluded, so the surface is reasonably complete.