VERIFIED

Go MCP MySQL

Safety: 50/100

0.0(0)

A ready-to-use Model Context Protocol (MCP) server for interacting with MySQL databases, supporting CRUD operations and read-only modes.

MCP ServersFreemium

Boost this tool

Subscribe to listing upgrades or segmented pushes.

Overview

A ready-to-use Model Context Protocol (MCP) server for interacting with MySQL databases, supporting CRUD operations and read-only modes.

This MCP server offers a balance between functionality and risk. The read-only mode and explain check provide some safety, but the ability to execute arbitrary write queries and the handling of credentials require careful management and oversight. It is safest when used in read-only mode with trusted queries, and riskiest when write access is enabled without proper input validation.

Performance will depend on the complexity of the SQL queries and the size of the database. Consider indexing frequently queried columns to improve read performance.

The primary cost consideration is the resource usage of the MySQL server itself. Complex queries can consume significant CPU and memory.

Go51 starsMITReleased 3/19/2025CI/CD

Connections & Capabilities

Connects To

GitHubMySQL

Capabilities

ReadWriteExecAdmin

Client Compatibility

Claude Desktop

full

Cursor

untested

Windsurf

untested

VS Code (Copilot)

untested

Quickstart

Claude Desktop Config

{
  "mcpServers": {
    "mysql": {
      "command": "go-mcp-mysql",
      "args": [
        "--host", "localhost",
        "--user", "root",
        "--pass", "password",
        "--port", "3306",
        "--db", "mydb"
      ]
    }
  }
}

Tools (9)

safe

list_database

Lists all databases available on the MySQL server.

Read-only operation, no data modification.

safe

list_table

Lists tables in the MySQL server, optionally filtered by name.

Read-only operation, no data modification.

high

create_table

Creates a new table in the MySQL server using a provided SQL query.

Modifies the database schema, potentially causing disruption.

high

alter_table

Alters an existing table in the MySQL server using a provided SQL query.

Modifies the database schema, potentially causing disruption.

safe

desc_table

Describes the structure of a specified table.

Read-only operation, no data modification.

safe

read_query

Executes a read-only SQL query against the database.

Read-only operation, no data modification.

high

write_query

Executes a write SQL query against the database.

Modifies data in the database.

high

update_query

Executes an update SQL query against the database.

Modifies data in the database.

critical

delete_query

Executes a delete SQL query against the database.

Deletes data from the database.

Security

Auth Method

None

Known Risks

!SQL injection vulnerabilities if the LLM constructs malicious queries.
!Exposure of database credentials if command-line arguments or DSN are logged or leaked.
!Unintended data modification or deletion if write operations are not carefully controlled.
!Lack of authentication or authorization mechanisms beyond database credentials.
!Potential for denial-of-service if the server is overwhelmed with requests.

Safety Score

moderate risk

Positive

+Optional read-only mode restricts potentially harmful operations.
+Includes a query plan check using `EXPLAIN` before executing queries.
+No external internet exposure by default; operates within the local environment.
+Uses command-line arguments or DSN for configuration, avoiding hardcoded credentials in code.

Risks

-Write operations allowed by default, posing a risk of unintended data modification.
-Secrets (database credentials) are passed as command-line arguments or within the DSN string.
-No built-in RBAC or fine-grained permission controls.
-Potential for SQL injection if queries are not properly sanitized by the LLM.

Use Cases

Database Schema Management

-Listing existing databases and tables.
-Creating new tables based on LLM-generated schemas.
-Modifying existing table structures.

Data Extraction and Analysis

-Retrieving data from tables using SQL queries.
-Generating reports based on query results.
-Performing data analysis using LLM-generated queries.

Data Modification and Maintenance

-Updating existing data in tables.
-Deleting obsolete or incorrect data.
-Populating tables with new data.

Database Exploration

-Discovering available databases and tables.
-Understanding table schemas.
-Examining data through read queries.

Who Is This For?

Best For

Rapid prototyping of database interactions.
Automated schema exploration and documentation.
Generating simple reports from database data.
Performing ad-hoc data analysis.

Not Ideal For

Production environments requiring high security and control.
Applications requiring complex transaction management.
Systems handling sensitive data without proper safeguards.
Multi-user environments without proper access controls.

Autonomy & Execution

Default ModeRead and Write enabled

Destructive Tools

The server defaults to read and write access, giving the LLM full control over the database unless the `--read-only` flag is enabled. There is no built-in sandboxing or rollback mechanism, so caution is advised.

StatelessYes

Retry LogicNot documented

ConcurrencySingle-threaded

Production Tip

Enable the `--read-only` flag in production environments to prevent accidental data modification, and carefully monitor query execution.

FAQ

How do I enable read-only mode?

Add the `--read-only` flag to the command-line arguments when starting the server.

How do I specify the database connection details?

Use either command-line arguments (`--host`, `--user`, `--pass`, `--port`, `--db`) or a DSN string via the `--dsn` flag.

What happens if a query fails?

The server will likely return an error message from the underlying MySQL driver.

Does this server support connection pooling?

The documentation does not explicitly mention connection pooling; it may or may not be implemented.

How do I update the server to the latest version?

Download the latest release from GitHub or use `go install -v github.com/Zhwt/go-mcp-mysql@latest`.

Is there any authentication required to access the server?

Authentication is handled through the MySQL database credentials; there is no separate authentication layer for the MCP server itself.

Can I use this server with a remote MySQL database?

Yes, as long as the server has network access to the remote database and the appropriate connection details are provided.

Metrics

Discovered2/14/2026

Reviews0

Saved By0 users

Related Tools

Go MCP MySQL - AI Tool Review & Alternatives | Flaex AI