Combined MCP Server
Related Servers
Alternatives to Combined MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables AI agents to interact with Amazon Redshift databases using natural language to execute queries, list tables, describe schemas, and retrieve sample data.5-
- FlicenseAqualityDmaintenanceEnables AI agents to interact with Amazon Redshift databases using natural language to execute queries, explore schemas, and retrieve sample data.5-
- AlicenseNot gradedqualityDmaintenanceEnables interacting with Amazon Redshift databases through SQL queries, schema exploration, and execution plan analysis.5MIT
- AlicenseNot gradedqualityAmaintenanceEnables secure, read-only access to Amazon Redshift data warehouses for AI assistants, allowing schema inspection, query execution, and data understanding.17 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs and AI agents to securely query and interact with Amazon Redshift databases with configurable access modes (readonly, readwrite, admin) for safe data exploration and management.-
- FlicenseNot gradedqualityBmaintenanceEnables SQL query execution and knowledge base search via RAG agent through two tools.-
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap. The vectorstore tools (build, get_status, query) handle knowledge base operations, while the Redshift tools (list_schemas, list_tables, describe_table, run_query) handle database operations. The separation between these two domains is unambiguous.
All tools follow a consistent verb_noun naming pattern. The verbs are descriptive (build, describe, get, list, query, run) and the nouns clearly indicate the target resource (vectorstore, table, schemas, tables, query). There are no deviations in naming conventions.
With 7 tools, the count is reasonable for a combined server covering two domains. However, the vectorstore side feels slightly thin with only three tools (build, status, query), lacking operations like update or delete. The Redshift side is well-covered with four tools.
For the Redshift domain, the toolset provides comprehensive coverage (list schemas/tables, describe table, run query). For the vectorstore domain, core operations exist (build, query, status), but there are minor gaps such as updating or deleting documents from the knowledge base, which agents might need to work around.