MySQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSQL_HOST | No | MySQL host | localhost |
| MYSQL_PORT | No | MySQL port | 3306 |
| MYSQL_USER | No | MySQL user | root |
| MYSQL_DATABASE | No | MySQL database | test |
| MYSQL_PASSWORD | No | MySQL password |
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 |
|---|---|
| get-schemaA | Get the schema of a table |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose focused on retrieving table schema information.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'get-schema' follows a clear verb-noun pattern and uses kebab-case consistently (though this is trivial with one tool).
A MySQL server with only one tool is severely under-scoped for its domain. MySQL involves operations like querying, inserting, updating, deleting, managing connections, and handling transactions, so a single schema retrieval tool represents an extreme mismatch with the expected functionality.
The tool surface is severely incomplete for a MySQL server. It lacks basic CRUD operations (create, read, update, delete), query execution, connection management, and other essential database functions, making it impossible for agents to perform meaningful database interactions.