redshift-comment-mcp
Related Servers
Alternatives to redshift-comment-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA secure, read-only MCP server for Amazon Redshift that enables AI assistants to discover, query, and export data through natural language via 10 specialized tools, with schema allowlisting and row limits for safety.-
- AlicenseAqualityDmaintenanceA read-only MCP server for exploring and analyzing a Secoda data catalog, enabling AI chat, semantic search, glossary browsing, and data lineage tracing.12Apache 2.0
- AlicenseAqualityCmaintenance🤖 Enable AI assistants (Claude, Cursor) to monitor, diagnose, and query Amazon Redshift using this MCP server and the AWS Data API.76MIT
- AlicenseCqualityDmaintenanceA read-only MCP server that enables users to query Databricks SQL, browse metadata, and monitor Delta Lake tables. It also supports tracking Databricks Jobs, DLT Pipelines, and cluster metrics through natural language interfaces.254MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that integrates Microsoft Copilot with Amazon Redshift, enabling catalog search, query template retrieval, and query execution with end-to-end user identity propagation.Apache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with Amazon Redshift databases, allowing for schema exploration, query execution, and statistics collection.32Apache 2.0
TDQS
Scored across 13 tools
Most tools are cleanly separated by resource and action (list/search/get on schemas/tables/columns), and execute_sql/setup_via_dialog are unambiguous. Some overlap remains: list_tables/list_columns with include_comments can partially substitute for get_table_comment/get_all_column_comments, and the 'authoritative' distinction is a bit subtle.
Tool names consistently follow a verb_noun snake_case pattern: list_*, search_*, get_*, execute_sql, setup_via_dialog. Resource nouns are regular across list/search tools, and comment getters follow object+_comment. No mixed conventions or vague verb choices.
13 tools is within the ideal range and covers discovery, search, comment retrieval, SQL, and setup. A few comment getters are arguably redundant with the include_comments options on list tools, but the count is still well-scoped for the domain.
The surface covers schema/table/column discovery, comment lookup, keyword search, ad-hoc SQL, and bootstrap/status, so core workflows have no dead ends. Minor gaps remain: there is no bulk table-comment fetch independent of listing, and column search requires a schema rather than supporting a true cluster-wide search.