Skip to main content
Glama
ByteTora

mysql-mcp-server-all

by ByteTora

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MYSQL_HOSTYesDatabase host
MYSQL_PORTNoDatabase port3306
MYSQL_USERYesDatabase user
MCP_HTTP_HOSTNoListen host for sse/streamable-http127.0.0.1
MCP_HTTP_PORTNoListen port for sse/streamable-http8000
MCP_TRANSPORTNoTransport: stdio, sse, or streamable-httpstdio
MCP_HTTP_TOKENNoBearer token for streamable-http
MYSQL_DATABASENoDefault database. Omit for multi-database mode
MYSQL_PASSWORDNoDatabase password
MYSQL_CONNECT_TIMEOUTNoConnection timeout in seconds10

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_sqlA

Execute a read-only SQL query (SELECT / SHOW / DESCRIBE / EXPLAIN / WITH).

Returns rows as JSON. Single statements only.

get_schema_infoB

Return column metadata (name, type, nullability, key, default) for a table.

Accepts database.table notation for cross-database lookups.

get_table_sampleA

Fetch a representative sample of rows (max 20) from a table.

Accepts database.table notation for cross-database lookups.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation4/5

The tools are largely distinct: execute_sql runs arbitrary read-only queries, get_schema_info returns column metadata, and get_table_sample fetches sample rows. However, execute_sql can also perform SELECT queries that return sample data, creating some overlap with get_table_sample.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: execute_sql, get_schema_info, get_table_sample. This makes the toolset predictable and easy to navigate.

Tool Count4/5

Three tools is a reasonable count for a focused read-only MySQL exploration server. While on the smaller side, each tool serves a clear purpose and the set does not feel overly thin.

Completeness4/5

The domain is well-covered for read-only database exploration: arbitrary SQL queries, schema metadata, and sample rows cover the core needs. Missing functionality like listing all tables can be achieved via execute_sql, so there are no major gaps.

Maintenance

ActivitySlowing
ResponsivenessNo issues