Adb MySQL MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADB_MYSQL_HOST | Yes | The host address of the AnalyticDB for MySQL database | |
| ADB_MYSQL_PORT | Yes | The port number of the AnalyticDB for MySQL database | |
| ADB_MYSQL_USER | Yes | The username for the AnalyticDB for MySQL database | |
| ADB_MYSQL_DATABASE | Yes | The database name in the AnalyticDB for MySQL cluster | |
| ADB_MYSQL_PASSWORD | Yes | The password for the AnalyticDB for MySQL database |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_sqlC | Execute a SQL query in the Adb MySQL Cluster |
| get_query_planC | Get the query plan for a SQL query |
| get_execution_planC | Get the actual execution plan with runtime statistics for a SQL query |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All of the databases | Display all of the databases in Adb MySQL |
TDQS
Scored across 3 tools
The tools have overlapping purposes focused on SQL query analysis, with execute_sql clearly distinct for running queries, but get_execution_plan and get_query_plan could be confused as both relate to query plans. Descriptions help differentiate them slightly (one includes runtime statistics), but the boundaries are somewhat unclear.
All tool names follow a consistent verb_noun pattern (execute_sql, get_execution_plan, get_query_plan) with clear, predictable naming. There are no deviations in style or convention across the set.
With only 3 tools, the server feels thin for a MySQL cluster management domain, as it lacks operations for database/table management, user permissions, or monitoring. However, the tools are focused on query execution and analysis, which is a reasonable but limited scope.
For a MySQL server, there are significant gaps in the tool surface: no CRUD operations for databases/tables, no user management, no backup/restore, and no monitoring tools. The set only covers query execution and plan analysis, leaving many core database management tasks unaddressed.