Database Mcp Mysql

io.github.arifulislamatPublished by GitHub account arifulislamatv0.5.0Updated Oct 24, 2026

MCP server for MySQL. Read-only by default, row caps, statement timeouts, secrets never logged.

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

A local MCP server for MySQL that gives an AI assistant two guarded tools to run SQL and inspect schema, read-only by default.

What you can do
Run SQL statements against a configured MySQL database through execute_sql, with read-only mode, row caps and statement timeouts on by default. Explore schema with search_objects: call it with no arguments to list tables, or with a table name to get columns, indexes and foreign keys. Connection details are set at launch from flags, a YAML config file or environment variables, never through a tool call.
When to use it
Useful when an assistant needs to query or explore a MySQL database from the desktop, for example to answer data questions or inspect table structure, and you want a small two-tool surface with conservative guardrails rather than broad database access.
Requirements
Runs as a local process over stdio; install via npm, PyPI (uvx) or a Rust binary. Needs MYSQL_HOST, MYSQL_DATABASE and MYSQL_USER, plus MYSQL_PASSWORD or a mounted password file. Network access to the MySQL host is required. Desktop only.
Before you install
The server holds database credentials (MYSQL_PASSWORD); a read-only database user is recommended. Read-only mode, row caps and timeouts are defaults, so check the configuration before relying on them. Statements still reach the database, so misconfiguration could allow writes or heavy queries.

Installation

In SourceWeft

  1. Open Database Mcp 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

database-mcp

[CI] [License: MIT] [npm] [PyPI] [crates.io] [Node >= 22]

MCP servers that give AI clients safe, structured access to SQL databases.

One installable package per database engine, in TypeScript (npm), Python (PyPI), and Rust (crates.io). Every package exposes the same minimal two-tool surface, execute_sql and search_objects, with guardrails on by default: read-only mode, row caps, and statement timeouts.

Packages

All three lines are published and pass the same language-agnostic conformance suite against real databases in CI, so behavior is identical regardless of language. Every engine is also listed on the MCP Registry with all three install options: npm, PyPI, and cargo.

Rust crates are named database-mcp-rs-<engine> because the plain names are taken on crates.io; the command each one installs is still database-mcp-<engine>. Go is planned.

Design principles

  • Two tools, no more. A tiny tool surface keeps the model's context window clean. search_objects progressively discloses schema: call it with no arguments to list tables, with a table name to get columns, indexes, and foreign keys.
  • Safe by default. Read-only mode is enforced in two layers: a conservative SQL guard, plus a session-level read-only setting in the database itself. Rows are capped (default 1000) and statements time out (default 30s).
  • Configured at launch, never via chat. Connection details come from flags, a YAML config file, or environment variables. Credentials are never accepted through a tool call.
  • Secrets never appear in logs. Passwords live in non-printable secret types, DSNs are sanitized before logging, and a redaction filter guards the log boundary.

Quick start

Pick your engine's package; each README has the full config surface. SQLite via npm:

json
{  "mcpServers": {    "sqlite": {      "command": "npx",      "args": ["-y", "@database-mcp/sqlite", "--dsn", "/absolute/path/to/database.db"]    }  }}

Or via PyPI: use "command": "uvx" and "args": ["database-mcp-sqlite", "--dsn", "/absolute/path/to/database.db"].

Or as a native binary, with no Node or Python runtime: run cargo install database-mcp-rs-sqlite, then use "command": "database-mcp-sqlite" with the same args minus the package name.

Flags, environment variables, and YAML config are identical across all three lines.

Networked engines take credentials from the environment (MYSQL_*, MARIADB_*, POSTGRES_*/DATABASE_URL, LIBSQL_URL/LIBSQL_AUTH_TOKEN), *_FILE mounted secrets, or a YAML file via --config. Never from a chat prompt.

Contributing

See CONTRIBUTING.md. The short version: the conformance suite is the definition of done. A change is mergeable only when conformance/run.mjs passes against every affected server.

License

MIT

Source: README.md at commit 775af94

Tools

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

Version history

2
  1. v0.5.0LatestOct 17, 2026
  2. v0.4.2Sep 16, 2026

Score

50% 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
  • License10 pts