TiDB Cloud Zero MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIDB_URL | No | MySQL connection string for your own TiDB Cloud instance (e.g., mysql://user:password@host/database) | |
| TIDB_HOST | No | TiDB Cloud host (e.g., gateway01.us-west-2.prod.aws.tidbcloud.com) | |
| TIDB_DATABASE | No | TiDB Cloud database name | |
| TIDB_PASSWORD | No | TiDB Cloud password | |
| TIDB_USERNAME | No | TiDB Cloud username |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryA | Execute a read-only SQL query (SELECT, SHOW, DESCRIBE, EXPLAIN). Returns results as a formatted table. Examples: query("SELECT * FROM users LIMIT 10") query("SHOW TABLES") query("DESCRIBE users") |
| executeA | Execute a write SQL statement (CREATE, INSERT, UPDATE, DELETE, ALTER, DROP). Returns the number of affected rows. Examples: execute("CREATE TABLE users (id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(255))") execute("INSERT INTO users (name) VALUES ('Alice')") |
| batch_executeA | Execute multiple SQL statements sequentially. Args: statements: List of SQL statements to execute in order Example: batch_execute([ "CREATE TABLE users (id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(255))", "INSERT INTO users (name) VALUES ('Alice')", "INSERT INTO users (name) VALUES ('Bob')" ]) |
| list_tablesA | List all tables in the current database with row counts. |
| describe_tableA | Get the schema of a table (columns, types, keys). Args: table: Table name to describe |
| get_database_infoA | Get database connection info, TiDB version, and instance status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_crud_table | Generate SQL to create a table with common CRUD patterns. |
| analyze_data | Generate a data analysis workflow for a table. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_tables | List of all tables in the database. |
| resource_info | Database connection info and TiDB version. |
TDQS
Scored across 6 tools
Some overlap exists between query and list_tables/describe_table since query supports SHOW and DESCRIBE, which can duplicate those tools. However, the descriptions clarify the intended use cases, making selection mostly straightforward.
Names use a consistent lowercase underscore style with imperative verbs, but mix single-word verbs (query, execute) with verb_noun pairs (list_tables, describe_table). This is a minor deviation from a fully uniform pattern.
Six tools is well within the ideal range for a database server MCP, covering both read and write operations without being bloated.
The tool set covers core database operations: listing tables, describing schema, running read-only queries, executing write statements, batch execution, and retrieving server info. No obvious gaps for its stated purpose.