dm_mcp_server
Related Servers
Alternatives to dm_mcp_server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Dameng database that enables querying and managing database objects via JDBC, including tools for schemas, tables, views, indexes, and more.MIT
- AlicenseAqualityDmaintenanceMCP server enabling AI assistants to connect and query Dameng DM8 databases via JDBC. Supports SQL queries, listing tables, and describing schemas.312 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for DaMeng database, enabling AI assistants to execute SQL queries, list tables, describe table structures, and retrieve schema information.42 npm7MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for HighGo and MySQL databases, providing tools for querying, executing DDL, listing tables, and inspecting table structures.5 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Dameng databases through natural language or direct SQL operations. Provides a web interface for listing tables, executing queries, and viewing table structures with MCP protocol support for AI model integration.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Dameng databases through MCP, supporting query execution, schema exploration, and connection management.MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: connection testing, direct SQL execution, file-based SQL execution, table listing/counting, schema inspection/switching, batch column comments, and file-directory introspection. Although multiple tools execute SQL, their input modes and constraints are explicit enough to avoid misselection.
All tool names follow a consistent snake_case verb_noun pattern, such as test_connection, list_tables, switch_schema, and execute_sql_file. Even the more specialized batch_comment_columns_sql follows the same imperative style.
Nine tools is well-scoped for a database MCP server. Each tool covers a meaningful part of the workflow, from schema navigation to SQL execution, without feeling bloated or redundant.
The core database operations are covered: connection testing, SQL execution, schema switching, and table listing. A minor gap is the lack of a dedicated describe-table or column-metadata tool, though this can be worked around with execute_sql.