MySQL Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYSQL_HOST | Yes | The MySQL server host | |
| MYSQL_PORT | Yes | The MySQL server port | |
| MYSQL_USER | Yes | The MySQL username | |
| MYSQL_DATABASE | Yes | The MySQL database name | |
| MYSQL_PASSWORD | Yes | The 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | Use this when you need to list tables and views in the configured MySQL database. |
| describe_tableA | Use this when you need the columns, types, keys, and defaults for one MySQL table. |
| queryA | Use this when you need to run one read-only MySQL query. It accepts SELECT, SHOW, DESCRIBE, EXPLAIN, and WITH statements only. |
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 3 tools
Each tool serves a clearly distinct purpose: listing tables, describing a table's schema, and executing arbitrary read-only queries. There is no overlap or ambiguity, so an agent can easily select the right tool for the task.
Two tools follow the verb_noun pattern (list_tables, describe_table), while 'query' is a bare verb. This is a minor deviation, but the naming remains predictable and readable, and the overall style is consistent (snake_case).
Three tools is a small but reasonable footprint for a read-only database bridge. They cover the core operations (listing, describing, and querying) without unnecessary bloat, though a slightly larger set could be justified.
For a read-only MySQL bridge, the surface covers the essential workflows: discovering available tables, understanding schema, and running arbitrary queries. A potential gap is lack of transaction or metadata utilities, but these are not expected for a simple bridge.