Mysql

io.github.hughhan1Published by GitHub account hughhan1v0.4.1Updated Oct 26, 2026

MySQL statements and transactions over MCP

VerifiedSTDIODesktop onlyDatabases

Overview

AI-generated overview

Local MCP server that lets an assistant run MySQL statements and transactions against one existing MySQL 8.4 database.

What you can do
  • Run SQL statements against a single MySQL 8.4 database.
  • Execute transactions, so multi-statement work can be committed or rolled back.
  • Optionally connect to a Cloud SQL instance through its private IP instead of a direct URL.
When to use it
Useful when an assistant needs to query or modify a specific MySQL 8.4 database directly, for example to inspect schema, run ad-hoc queries, or perform transactional changes during development or operations work.
Requirements
Runs as a local process on the user's machine (desktop only, not web-executable), delivered as a container image over streamable-http. Requires a DATABASE_URL secret holding a SQLAlchemy mysql+pymysql URL for one existing MySQL 8.4 database. Optionally set CLOUD_SQL_INSTANCE as project:region:instance to connect through its private IP. Network access to the database is needed.
Before you install
The assistant gets direct SQL access to a real database, so statements and transactions can read, change or delete data; point it at a least-privileged account and a non-production database where possible. DATABASE_URL contains database credentials and should be supplied as a secret. Connecting through CLOUD_SQL_INSTANCE uses the instance's private IP, so the machine must be on the right network.

Installation

In SourceWeft

  1. Open Mysql in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.4.1LatestOct 19, 2026
  2. v0.1.0Oct 19, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.