MySQL MCP Server

@designcomputer

リポジトリホームページ

基本情報

カテゴリ

データベース

ライセンス

MIT

トランスポート

stdio

作者

designcomputer

MySQL MCP Server について

A Model Context Protocol (MCP) server that enables secure interaction with MySQL databases

#mysql #database #mcp-server

MySQL MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mysql_mcp_server": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "designcomputer/mysql-mcp-server",
        "--client",
        "claude"
      ]
    }
  }
}

MySQL MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is MySQL MCP Server?

MySQL MCP Server is a Model Context Protocol implementation that enables secure interaction between AI applications (hosts/clients) and MySQL databases. It facilitates structured database exploration and analysis through a controlled interface.

How to use MySQL MCP Server?

Install via pip install mysql-mcp-server, then configure environment variables (e.g. MYSQL_HOST, MYSQL_USER, MYSQL_PASSWORD) and integrate with hosts like Claude Desktop or VS Code by adding the server to their MCP configuration. Supports both STDIO and SSE transport modes. For remote deployments, use SSE with a reverse proxy for authentication.

Key features of MySQL MCP Server

List MySQL tables as resources
Read table contents and execute SQL queries
Multi-database mode when MYSQL_DATABASE is omitted
SSE/HTTP transport support with MCP_TRANSPORT=sse
SSH tunneling for secure connections
Comprehensive schema information via get_schema_info
Table data sampling via get_table_sample
Secure database access through environment variables

Use cases of MySQL MCP Server

AI agents exploring database structure before analysis
Running safe, single‑statement SQL queries through a chat interface
Sampling data from tables to understand content without large fetches
Cross‑database queries using database.table notation
Self‑hosted deployments with SSH tunneling or SSL/TLS encryption

よくある質問

What transport modes does MySQL MCP Server support?

It supports both STDIO (standard input/output) and Streamable HTTP (SSE) transport modes. SSE is recommended for remote or self‑hosted deployments.

How do I enable multi‑database mode?

Omit the `MYSQL_DATABASE` environment variable. The server then returns all user databases for resource listing and allows fully qualified names like `mydb.mytable` in queries.

Does SSE transport include built‑in authentication?

No. SSE binds to `0.0.0.0` by default and accepts connections without credentials. If exposed beyond localhost, place it behind a reverse proxy (e.g., nginx with HTTP Basic Auth) and set `MCP_SSE_HOST=127.0.0.1`.

What are the limitations on SQL queries?

Only single‑statement queries are supported. Multi‑statement queries (e.g., `USE db; SELECT …`) are not allowed. DML operations (`INSERT`, `UPDATE`, `DELETE`) are marked with a destructive hint.

How are table/column identifiers validated?

Identifiers in `get_schema_info` and `get_table_sample` are restricted to alphanumeric characters, underscores, and `$`. A single dot is allowed as a separator between database and table names. Other special characters are rejected to prevent SQL injection.