MySQL MCP Server (Optimized)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSQL_HOST | Yes | The hostname or IP address of the MySQL server. | localhost |
| MYSQL_PORT | Yes | The port number on which the MySQL server is listening. | 3306 |
| MYSQL_USER | Yes | The username to connect to the MySQL database. | |
| MYSQL_DATABASE | Yes | The name of the MySQL database to connect to. | |
| MYSQL_PASSWORD | Yes | The password to connect to the 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_queryC | Executa uma query SQL no banco MySQL |
| describe_tableC | Descreve a estrutura de uma tabela |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_table | Analisa uma tabela específica |
| find_large_tables | Encontra tabelas com mais registros |
| database_overview | Visão geral do banco de dados |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Lista de Bancos de Dados | Lista todos os bancos de dados disponíveis |
| Lista de Tabelas | Lista todas as tabelas do banco atual |
| Schema do Banco | Schema completo do banco de dados atual |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: describe_table is for metadata inspection of a table's structure, while execute_query is for running arbitrary SQL queries. There is no overlap or ambiguity between these functions, making it easy for an agent to choose the correct tool based on the task.
Both tools follow a consistent verb_noun pattern with snake_case naming: describe_table and execute_query. The naming is clear, predictable, and adheres to a uniform style throughout the tool set.
With only 2 tools, this server is severely under-equipped for a MySQL database management domain. Core operations like creating/dropping tables, inserting/updating/deleting data, managing users, or handling transactions are missing, making it inadequate for typical database workflows.
The tool surface is extremely incomplete for a MySQL server. It lacks basic CRUD operations (create, read, update, delete), schema modification tools, user management, and other essential database functions. Agents will frequently encounter dead ends when trying to perform common MySQL tasks.