Alibaba Cloud RDS OpenAPI MCP Server
OfficialRelated Servers
Alternatives to Alibaba Cloud RDS OpenAPI MCP Server
No user-submitted related servers found.
Related Servers
AlicenseBqualityBmaintenanceA server that provides access to Alibaba Cloud resources including ECS, VPC, and CloudMonitor through API and OOS implementations, enabling resource management and monitoring via a unified interface.34130Apache 2.0- AlicenseAqualityCmaintenanceMCP server for Supabase instances running on Aliyun RDS, enabling AI assistants to interact with your Supabase instance hosted on Aliyun cloud infrastructure.2728 npm2MIT
- FlicenseBqualityDmaintenanceA server that provides access to Alibaba Cloud workitem descriptions through MCP protocol, allowing agents to retrieve structured workitem data including text, images, and HTML content by ID.11-
- AlicenseNot gradedqualityDmaintenanceMCP server for connecting to databases (PostgreSQL, MySQL, SQL Server, Redis) enabling SQL queries, table exploration, and Redis key-value operations.1MIT

Redis Cloud API MCP Serverofficial
AlicenseAqualityFmaintenanceThe Redis Cloud API MCP Server provides an MCP Server for Redis Cloud's API, allowing you to manage your Redis Cloud resources using natural language.165 npm41MIT- FlicenseNot gradedqualityDmaintenanceA proxy service that connects Claude Code to Alibaba Cloud International OpenAPI MCP Server, supporting services like ECS and OSS. It provides secure multi-user authentication via OAuth 2.1 and allows for dynamic configuration of MCP services.9 npm-
TDQS
Scored across 36 tools
Most tools have clearly distinct purposes, but there is some overlap between describe_db_instance_performance and describe_monitor_metrics (both query metrics), and a few tools like query_sql vs show_* tools could be confused. Additionally, attach_whitelist_template_to_instance has an incorrect description matching allocate_instance_public_connection, which may mislead agents.
The naming generally follows a verb_noun pattern (e.g., describe_db_instance_*, modify_db_instance_*), but there are minor inconsistencies like show_largest_table (no verb prefix), get_current_time (uses 'get' instead of describe/query), and explain_sql (verb_noun but different verb). Overall, the pattern is predictable.
With 36 tools covering instance lifecycle, monitoring, SQL execution, and network management, the count is well-suited for the RDS domain. Each tool adds clear value, and the set is neither too sparse nor overly bloated.
The tool surface lacks critical operations: no tool to delete an RDS instance, no create/modify/delete database tools (except via query_sql), and no backup/restore functionality. These gaps will likely cause agent failures when performing cleanup or database management tasks.