Skip to main content
Glama
HaokaiLau

mysql-readonly-mcp

by HaokaiLau

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MYSQL_HOSTYesMySQL host
MYSQL_PORTYesMySQL port
MYSQL_USERYesMySQL user
MYSQL_DATABASEYesMySQL database name
MYSQL_PASSWORDYesMySQL 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
mysql_get_server_infoA

Return the configured MySQL database, server version, charset, timezone, and safety limits.

mysql_list_tablesC

List tables and views in the configured database.

mysql_describe_tableB

Describe columns and foreign-key relationships for one table or view.

mysql_list_indexesA

List indexes and ordered indexed columns for one table.

mysql_queryB

Execute one safe, read-only SELECT or read-only CTE against the configured database.

mysql_explainA

Return the JSON execution plan for a safe read-only SELECT query.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a clearly distinct introspection or query concern: server metadata, table listing, column/FK description, index listing, query execution, and plan explanation. The describe_table vs list_indexes boundary is clear (columns vs indexes), so an agent can reliably select the right tool.

Naming Consistency5/5

All six tools use a consistent mysql_verb_noun snake_case pattern (get_server_info, list_tables, describe_table, list_indexes, query, explain). Predictable and uniform throughout.

Tool Count5/5

Six tools is well-scoped for a read-only database server. Each tool earns its place across discovery (info, tables, describe, indexes) and querying (query, explain) with no redundancy.

Completeness4/5

The read-only surface covers introspection plus querying and plan analysis, which is solid for the stated purpose. Minor gaps like listing databases or schema-level search exist but are workable given the server targets a single configured database.

Maintenance

ActivityMaintained
ResponsivenessNo issues