gaussdb-ro-mcp
Related Servers
Alternatives to gaussdb-ro-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceA read-only MCP server that enables AI agents to explore database schemas and execute safe queries on PostgreSQL and MySQL.-
- AlicenseAqualityAmaintenanceA read-only MCP server for exploratory data analysis across PostgreSQL, MySQL, and ClickHouse databases, providing safe, read-only access with comprehensive analysis capabilities.10186 PyPI6MIT
- AlicenseNot gradedqualityCmaintenanceA read-only PostgreSQL MCP server that enables AI agents to perform schema introspection and execute SELECT-only queries. It supports secure database connections through SSL and SSH tunnels while offering a structure-only mode to restrict query access.10 npmMIT
- AlicenseNot gradedqualityCmaintenanceA zero-config, read-only PostgreSQL MCP server that enforces read-only access at the database level using READ ONLY transactions, allowing AI agents to safely explore schemas and run SELECT queries without risk of mutation.22 npmMIT
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server for PostgreSQL enabling schema introspection and SELECT queries via MCP clients like Claude, with multi-layered write protection.-
- AlicenseAqualityDmaintenanceA read-only MCP server that enables users to query and explore StarRocks databases through AI assistants like Claude. It supports SQL execution, schema discovery, and secure LDAP authentication for data analysis and metadata exploration.41MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: connectivity testing, schema listing, table listing, table structure inspection, and read-only query execution. The discovery flow is explicit and there is no overlap between tools.
All tool names use consistent snake_case verb_noun naming: list_schemas, list_tables, describe_table, execute_select, test_connection. The convention is predictable throughout.
Five tools is well-scoped for a read-only GaussDB exploration server. Each tool earns its place and supports a distinct step in the discovery/query workflow.
The surface covers the full read-only lifecycle: connectivity check, schema discovery, table/view discovery, structural inspection, and SELECT querying. No write operations are expected for a read-only server, and no obvious dead ends are present.