cubrid-mcp-server
Related Servers
Alternatives to cubrid-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to interact with MySQL databases by inspecting schemas and executing safe, read-only queries within transactions.2 npm10MIT
- AlicenseAqualityBmaintenanceEnables LLMs to safely explore, query, diagnose, and modify relational databases through a unified set of schema introspection, SQL execution, and administration tools. Supports multiple database backends with AST-level read-only guards, automatic LIMIT injection, and explicit opt-in write permissions for DML and DDL.6Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to inspect database schemas and run strictly read-only SQL queries with guardrails against destructive statements, multi-statement chaining, and unbounded scans. Supports SQLite natively and PostgreSQL optionally.4363 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely discover database schemas and execute read-only SQL queries through guardrailed tools that block mutations and clamp result sizes.MIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to inspect database schemas and execute SQL queries, including listing tables and describing table schemas.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to inspect database schemas and execute SQL queries, including listing tables and describing table schemas.-
TDQS
Scored across 11 tools
Each tool has a distinct primary purpose, but schema_definitions and describe_table overlap on column metadata, and describe_table also overlaps with list_indexes on index information. Agents could initially confuse schema_definitions with describe_table, though the descriptions clarify the difference.
Names are readable and mostly snake_case, but conventions are mixed: verb-led names (filter_table_names, describe_table, list_indexes, execute_query) coexist with noun-led names (all_table_names, schema_definitions, table_row_counts, health_check). A uniform verb_noun pattern would improve predictability.
Eleven tools is well within the ideal range for a database introspection server. Each tool addresses a distinct need—discovery, schema, indexes, query planning, execution, and health—without feeling bloated or sparse.
The surface covers table discovery, schema/index metadata, row counts, serials, class hierarchy, query execution, and plan tracing—strong coverage for read-only CUBRID introspection. Minor gaps like foreign-key metadata or object-level DDL are absent but can be worked around via execute_query.