MCP.so
Sign In

MySQL查询服务器 / MySQL Query Server MCP Server

@mangooer

Basic information

Category

Databases

Last updated

License

MIT

Transports

stdio

Author

mangooer

About MySQL查询服务器 / MySQL Query Server MCP Server

MySQL query server based on the MCP sse.Multi-level SQL risk control & injection protection Docker support for quick deployment

MySQL查询服务器 / MySQL Query Server MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mysql-mcp-server-sse": {
      "command": "docker",
      "args": [
        "pull",
        "mangooer/mysql-mcp-server-sse:latest"
      ]
    }
  }
}

MySQL查询服务器 / MySQL Query Server MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MySQL查询服务器 / MySQL Query Server?

A MySQL query server built on the MCP framework, supporting real-time database operations via SSE protocol. It provides comprehensive security, logging, configuration, and sensitive information protection for secure MySQL data access in development, testing, and production environments.

How to use MySQL查询服务器 / MySQL Query Server?

Deploy via Docker with environment variables for MySQL connection, or run from source using python -m src.server. The server listens on an SSE endpoint (/sse) by default. Configuration is done through environment variables or a .env file.

Key features of MySQL查询服务器 / MySQL Query Server

  • High-performance async with FastMCP framework
  • Connection pool with flexible parameter tuning
  • SSE real-time push support
  • Multi-level SQL risk control & injection protection
  • Database isolation with three-level access control
  • Automatic sensitive info masking

Use cases of MySQL查询服务器 / MySQL Query Server

  • Secure MySQL data access in production environments
  • Database schema exploration and metadata querying
  • Development and testing with automated SQL risk control
  • Multi-tenant database isolation for secure multi-database access

Frequently asked questions

1

Why does DELETE not work?

DELETE without a WHERE clause is classified as CRITICAL risk. You must allow CRITICAL level in the `ALLOWED_RISK_LEVELS` environment variable.

2

How to customize sensitive fields?

Set the `SENSITIVE_INFO_FIELDS` environment variable with a comma-separated list, e.g., `SENSITIVE_INFO_FIELDS=password,token`.

3

How to enable database isolation?

Set `ENABLE_DATABASE_ISOLATION=true` and `DATABASE_ACCESS_LEVEL=strict`, or use `ENV_TYPE=production` which automatically enables database isolation with `restricted` mode.

4

Cannot query system tables after enabling database isolation?

The `strict` mode blocks access to system tables. Switch to `restricted` mode (which allows system databases) if you need that access.

Comments

More Databases MCP servers