MySQL MCP Server (mysql-mcp)

📚 Full Documentation (Wiki) • Changelog • Security • Release Article

💎 Value Proposition

Integrate your AI agents with a production-ready MySQL environment. Deploy MCP v2 stateless architecture via HTTP transport. Optimize token efficiency via Code Mode. Secure your database with OAuth 2.1.

🎯 Leverage Core Benefits

Feature	Description
Specialized Tools	Access specialized tools for core CRUD, JSON, spatial data, document stores, and clusters.
Resources	Monitor schema, performance metrics, process lists, replication status, and InnoDB diagnostics in real-time.
AI-Powered Prompts	Execute guided workflows for query building, schema design, performance tuning, and infrastructure setup.
Code Mode	Reduce LLM token consumption by consolidating operations inside a secure, sandboxed V8 isolate.
Token-Optimized Payloads	Maximize token efficiency. Use optional flags to reduce response size for large payloads.
OAuth 2.1 Security	Enforce granular access control with RFC compliance, strict scopes, and Keycloak integration.
Smart Tool Filtering	Use tool groups and shortcuts to stay within IDE tool limits.
Streamable & Stateless HTTP	Support MCP v2 streamable HTTP and stateless HTTP deployments.
Connection Pooling	Leverage built-in connection pooling for efficient, highly concurrent database access.
Ecosystem Integrations	Manage MySQL Router, ProxySQL, and MySQL Shell utilities directly from your agent.
Advanced Encryption	Enforce TLS/SSL connections. Manage data masking, encryption monitoring, and compliance effortlessly.
Production-Ready Security	Prevent SQL injection with parameterized queries. Rely on strict input validation and audit logging.
Deterministic Errors	Receive structured responses with actionable suggestions. Eliminate silent failures and raw exceptions.
Observability	Export Prometheus metrics. Track container logs with Dozzle and audit trails with Grafana Alloy/Loki.
Strict TypeScript	Rely on strict TypeScript backed by robust test suites.
MCP v2 Compliant	Fully support the MCP v2 specification. This includes stateless routing, caching, safety hints, and notifications.

🤖 Automate Tasks with Guided Workflows

This server includes intelligent prompts for guided workflows:

Prompt	Description
`mysql_tool_index`	Complete tool index with categories
`mysql_quick_query`	Quick query execution shortcut
`mysql_quick_schema`	Quick schema exploration
`mysql_setup_observability`	Complete observability stack setup guide (Datadog, etc.)

Note: This is a subset of available prompts. Use mysql_tool_index to discover the full list of guided workflows.

📊 Improve Observability with Resources

This server exposes a comprehensive set of resources for database observability and telemetry:

Resource	Category	Description
`mysql://schema`	Core	Full database schema
`mysql://tables`	Core	Table listing with metadata
`mysql://variables`	Core	Server configuration variables
`mysql://status`	Core	Server status metrics
`mysql://processlist`	Core	Active connections and queries
`mysql://pool`	Core	Connection pool statistics
`mysql://capabilities`	Extended	Server version, features, and tool categories
`mysql://health`	Extended	Comprehensive database health status
`mysql://performance`	Extended	Query performance metrics
`mysql://indexes`	Extended	Index usage and statistics
`mysql://replication`	Extended	Replication status and lag
`mysql://innodb`	Extended	InnoDB buffer pool and engine metrics
`mysql://events`	Domain	Event Scheduler status and scheduled events
`mysql://sysschema`	Domain	sys schema diagnostics summary
`mysql://locks`	Domain	InnoDB lock contention detection
`mysql://cluster`	Domain	Group Replication / InnoDB Cluster status
`mysql://spatial`	Domain	Spatial columns and indexes
`mysql://docstore`	Domain	Document Store collections
`mysql://insights`	Analytics	Business insights memo from mysql_append_insight
`mysql://metrics`	Observability	In-memory token usage, latency, and request metrics
`mysql://audit`	Observability	Forensic trail and snapshot of system errors
`mysql://help`	Documentation	Critical gotchas and high-level API reference
`mysql://help/{group}`	Documentation	Dynamic group-specific tool reference (e.g., `core`, `codemode`)

🚀 Deploy Your AI Database

Meet Prerequisites

Node.js >= 24.0.0 (See .node-version for the pinned local development version)
Bun (for executing repository automation scripts)
MySQL server
pnpm

Install the Server

Install via NPM / PNPM

bash

pnpm add -g @neverinfamous/mysql-mcp

Run the server:

bash

mysql-mcp --transport stdio --mysql "mysql://mcp_user:secure_password@localhost:3306/testdb"

Or use npx without installing:

Terminal

npx @neverinfamous/mysql-mcp --transport stdio --mysql "mysql://mcp_user:secure_password@localhost:3306/testdb"

Run with Docker

Note on Namespaces: The Docker image uses the writenotenow namespace. The GitHub repo uses neverinfamous.

Linux Users: For host.docker.internal on Linux, run the container with --add-host host.docker.internal:host-gateway.

Terminal

docker run -i --rm -v ./data:/app/data -v ./logs:/var/log/mysql-mcp writenotenow/mysql-mcp:latest \
  --transport stdio \
  --allowed-io-roots /app/data \
  --mysql "mysql://mcp_user:secure_password@host.docker.internal:3306/testdb"

Enable Observability via Docker Compose

Launch the full observability stack using the included template. This includes Datadog, OpenTelemetry, Prometheus, and Grafana. This spins up the MCP server, MySQL database, Redis, and observability sidecars:

bash

cd examples/basic-mysql-datadog
cp .env.example .env
docker compose up -d

Grafana: Available at http://localhost:3001 (Dashboard pre-loaded).
Prometheus: Available at http://localhost:9090.
MCP Server: Available at http://localhost:3000.

Follow Datadog & OpenTelemetry Observability Rules

Datadog Constraints:

Authentication: Use pup CLI for authentication.
Autodiscovery: Avoid duplicate autodiscovery configurations. Add standard tracking labels (tags.datadoghq.com/env, tags.datadoghq.com/service, tags.datadoghq.com/version) to your containers.
WSL2 Hardening Limits: Enforce stop_grace_period: 30s, mem_limit: 1536m, and OpenMetrics timeouts of 10s.
Host Configuration: Use DD_HOSTNAME and native /etc/docker/daemon.json cgroup configurations ("default-cgroupns-mode": "host"). Disable DD_EXTRA_PERFORMANCE_METRICS.
Windows File Tailing: Be warned that Windows inotify tailing issues may occur with Docker/WSL2 log mapping.

OpenTelemetry Rules:

Semantic Conventions: Enforce gen_ai.* semantics.
Instrumentation: Use auto-instrumentation when possible.
Context Propagation: Ensure traceparent and tracestate propagation.
Processing & Logging: Utilize batch processors and ensure logs are formatted as JSON logs.

Audit Architecture & Exporter Healthcheck:

The primary MCP server writes execution traces to mcp-audit.jsonl via the --audit-log flag.
The metrics exporter runs as an independent sidecar process. It reads from mcp-audit.jsonl using the AUDIT_LOG_PATH environment variable to compute metrics.
The exporter isolates its own internal logs by setting its --audit-log flag to exporter-audit.jsonl.
The metrics server and exporter share a single process. Both operate on port 3000. This prevents port contention.
Exporter Healthcheck: wget --spider -q http://127.0.0.1:3000/metrics

Build From Source

bash

git clone https://github.com/neverinfamous/mysql-mcp.git
cd mysql-mcp
pnpm install
pnpm run build
node dist/cli.js --transport stdio --mysql "mysql://mcp_user:secure_password@localhost:3306/testdb"

🏗️ Use Infrastructure Templates

We provide production-ready Docker Compose templates in the examples/ directory. Use these to spin up test environments quickly. These templates include full Datadog observability out-of-the-box (Metrics, APM, and Logs).

Basic Template: A lightweight, single-node MySQL setup. Perfect for quick starts.
Enterprise HA Template: A highly-available InnoDB Cluster with MySQL Router and ProxySQL. Perfect for staging or production replicas.
Full Observability Ecosystem: A complete enterprise monitoring stack with Datadog, Prometheus, Grafana, Loki, and Alloy. See the Observability Wiki for deep-dive metrics configuration.

See the README in each directory for quick start instructions.

⚡ Optimize Token Usage with Code Mode

Code Mode (mysql_execute_code) reduces token usage by consolidating operations in a secure sandbox.

Code executes securely in a C++ V8 isolate sandbox. It enforces strict heap limits and synchronous termination. Native wrappers map all API calls across the boundary. This guarantees defense-in-depth and fleet-standard restrictions:

Enforce Engine-Level Restrictions

✅ Strict V8 Isolate Boundary — Code executes within a physically separate V8 isolate. It ensures native objects and prototypes cannot cross the boundary.
✅ Memory & CPU Constraints — enforced at the C++ level. This includes synchronous timeouts and strict heap limits.
✅ API Bindings via Reference — Injects MySQL methods securely using ivm.Reference wrappers.

Validate Code Statically

✅ Comprehensive blocked patterns — regex rules block require(), import(), eval(), Function, process, and __proto__. They also block filesystem/network access and system commands.
✅ Unicode & Comment Sanitization — Strips comments and performs NFKC normalization to prevent regex evasion.
✅ Configurable code input limit — prevents payload-based resource exhaustion.

Protect the Runtime

✅ RPC Quotas — Caps RPC API calls per execution. This prevents unbounded loops.
✅ Execution timeout — enforces timeouts to prevent resource exhaustion. Configurable via schema timeout.
✅ Egress boundary enforcement — streaming JSON.stringify serialization aborts mid-flight when exceeding size caps.
✅ Rate limiting — Enforces per-client limits (CODEMODE_RATE_LIMIT_MAX). Uses Redis with in-memory fallbacks.
✅ Readonly enforcement — Returns structured errors instead of executing write methods when readonly: true.
✅ Audit logging — Logs every execution with UUID, client ID, metrics, and redacted code preview.
✅ Admin scope — Code Mode requires admin scope when OAuth is enabled.
✅ Full API access — Exposes all tool groups via the mysql.* namespace.

⚡ Run Only Code Mode

Run with only Code Mode enabled. A single tool provides full capability access. See Option 1: Code Mode below for the recommended IDE configuration.

This exposes just mysql_execute_code. Agents write JavaScript against the typed SDK. They compose queries and chain operations across tool groups. They return exactly the needed data in one execution. This mirrors standard serverless edge execution patterns. It ensures fixed token costs.

[!TIP] Maximize Token Savings: Instruct your AI agent to prefer Code Mode.

"When using mysql-mcp, prefer mysql_execute_code (Code Mode) for multi-step operations. This minimizes token usage."

For maximum savings, run Code Mode as your only tool using --tool-filter codemode. See the Code Mode wiki for full API documentation.

🌐 Enable Remote Access via Streamable & Stateless HTTP

When to use HTTP mode: Deploy mysql-mcp as a standalone server. Multiple clients can connect remotely. Use stdio mode for local development.

Use cases for HTTP mode:

Run the server in a network-accessible Docker container
Deploy to cloud platforms (AWS, GCP, Azure)
Enable OAuth 2.1 authentication for enterprise security
Share one database connection across multiple AI clients

Use the HTTP transport for remote access:

Terminal

npx -y @neverinfamous/mysql-mcp \
  --transport http \
  --server-host 0.0.0.0 \
  --port 3000 \
  --allowed-io-roots /path/to/data \
  --mysql "mysql://mcp_user:secure_password@localhost:3306/testdb"

Docker:

Terminal

docker run --rm -p 3000:3000 \
  -v ./data:/app/data \
  -v ./logs:/var/log/mysql-mcp \
  -e MCP_AUTH_TOKEN=my-secret-token \
  writenotenow/mysql-mcp:latest \
  --transport http --server-host 0.0.0.0 --port 3000 --allowed-io-roots /app/data --mysql "mysql://mcp_user:secure_password@host.docker.internal:3306/testdb"

The server supports Streamable HTTP and Stateless HTTP deployments. Both stateful and stateless clients can connect:

Use Streamable HTTP (Recommended)

Modern MCP protocol — single endpoint, session-based:

Method	Endpoint	Purpose
`POST`	`/mcp`	JSON-RPC requests (initialize, tools/list, etc.)
`GET`	`/mcp`	SSE stream for server notifications
`DELETE`	`/mcp`	Session termination

Rate Limit: HTTP transport is rate limited per IP (default 100/min, configurable via MCP_RATE_LIMIT_MAX). Distribute limits across deployments via Redis using graceful in-memory fallbacks.

The server manages sessions via the Mcp-Session-Id header.

Run Statelessly

Use stateless deployments where sessions are not needed:

bash

node dist/cli.js --transport http --server-host 0.0.0.0 --port 3000 --allowed-io-roots /path/to/data --stateless --mysql "mysql://mcp_user:secure_password@..."

In stateless mode: GET /mcp returns 405. DELETE /mcp returns 204. Each POST /mcp instantiates a stateless HTTP transport.

Access Utility Endpoints

Method	Endpoint	Purpose
`GET`	`/health`	Health check (bypasses rate limiting, always available for monitoring)
`GET`	`/metrics`	Exports Prometheus metrics (available when `--metrics-export` is enabled)

🔐 Protect Your Data with Authentication

mysql-mcp supports two authentication mechanisms for HTTP transport:

Authenticate with Bearer Token (`--auth-token`)

Use lightweight authentication for development:

server.ts

node dist/cli.js --transport http --server-host 0.0.0.0 --port 3000 --allowed-io-roots /path/to/data --auth-token my-secret --mysql "mysql://mcp_user:secure_password@..."

# Or via environment variable
export MCP_AUTH_TOKEN=my-secret
node dist/cli.js --transport http --server-host 0.0.0.0 --port 3000 --allowed-io-roots /path/to/data --mysql "mysql://mcp_user:secure_password@..."

Clients must include Authorization: Bearer my-secret on all requests. /health and / are exempt. Unauthenticated requests receive 401. Responses include WWW-Authenticate: Bearer headers per RFC 6750.

Authenticate with OAuth 2.1

Use full OAuth 2.1 for production deployments:

bash

node dist/cli.js \
  --transport http \
  --server-host 0.0.0.0 \
  --port 3000 \
  --allowed-io-roots /path/to/data \
  --mysql "mysql://mcp_user:secure_password@localhost:3306/testdb" \
  --oauth-enabled \
  --oauth-issuer https://localhost:8080/realms/mysql-mcp \
  --oauth-audience mysql-mcp-client

Additional flags: --oauth-jwks-uri <url> (auto-discovered if omitted), --oauth-clock-tolerance <seconds> (default: 60).

Enforce OAuth Scopes

Enforce access control using OAuth scopes:

Scope	Access Level
`read`	Read-only queries (SELECT, EXPLAIN)
`write`	Read + write operations
`admin`	Full administrative access
`full`	Grants all access
`db:{name}`	Access to specific database
`table:{db}:{table}`	Access to specific table

Ensure RFC Compliance

This implementation follows full OAuth 2.1 for production multi-tenant deployments:

✅ RFC 9728 Protected Resource Metadata (/.well-known/oauth-protected-resource)
✅ RFC 8414 Authorization Server Discovery with caching
✅ RFC 7591 OAuth 2.1 Dynamic Client Registration
✅ JWT validation with JWKS support (TTL: 1 hour)
✅ MySQL-specific scopes: read, write, admin, full, db:{name}, table:{db}:{table}
✅ Per-tool scope enforcement via AsyncLocalStorage context threading

Note for Keycloak users: Add an Audience mapper to your client. This includes the correct aud claim. (Client → Client scopes → dedicated scope → Add mapper → Audience)

[!NOTE] Per-tool scope enforcement: The server enforces scopes at the tool level. Each tool group requires a specific scope. When OAuth is enabled, every tool invocation checks the calling token's scopes before execution. The server skips scope checks entirely when OAuth is not configured.

[!WARNING] HTTP without authentication: Exposing --transport http without authentication grants unrestricted access. Always enable authentication for production HTTP deployments. See SECURITY.md for details.

⚡ Simplify AI Integration with Client Configs

Install Agent Skills

For optimal AI performance, mysql-mcp includes specialized agent instructions in the skills/ directory. These skills teach AI coding assistants (like Cline, Antigravity, or Copilot) how to effectively use the server's capabilities, tool filters, and Code Mode.

To install: Copy the .md files from the skills/ directory into your AI assistant's designated skills or custom instructions folder (e.g., .cursor/rules/, .agents/skills/, etc.). This enables your agent to autonomously navigate the mysql-mcp ecosystem without hallucinating usage patterns.

Configure IDE Settings

Add a configuration to your IDE's MCP settings file:

Option 1: Code Mode (Maximum Token Savings, 🌟 Recommended)

Best for: General MySQL AI agent tasks. Exposes mysql_execute_code for full sandboxed toolset access.

config.json

{
  "mcpServers": {
    "mysql-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@neverinfamous/mysql-mcp",
        "--transport",
        "stdio",
        "--tool-filter",
        "codemode"
      ],
      "env": {
        "MYSQL_HOST": "localhost",
        "MYSQL_PORT": "3306",
        "MYSQL_USER": "mcp_user",
        "MYSQL_PASSWORD": "secure_password",
        "MYSQL_DATABASE": "testdb"
      },
      "timeout": 600
    }
  }
}

Option 2: Cluster (Tools for InnoDB Cluster Monitoring)

Best for: Monitoring InnoDB Cluster, Group Replication status, and cluster topology.

⚠️ Prerequisites:

InnoDB Cluster must be configured and running with Group Replication enabled

Connect to a cluster node directly (e.g., localhost:3307) — NOT a standalone MySQL instance

Use cluster_admin or root user with appropriate privileges

See MySQL Ecosystem Setup Guide for cluster setup instructions

config.json

{
  "mcpServers": {
    "mysql-mcp-cluster": {
      "command": "npx",
      "args": [
        "-y",
        "@neverinfamous/mysql-mcp",
        "--transport",
        "stdio",
        "--tool-filter",
        "cluster"
      ],
      "env": {
        "MYSQL_HOST": "localhost",
        "MYSQL_PORT": "3307",
        "MYSQL_USER": "cluster_admin",
        "MYSQL_PASSWORD": "cluster_password",
        "MYSQL_DATABASE": "mysql"
      },
      "timeout": 600
    }
  }
}

Option 3: Ecosystem (Tools for InnoDB Cluster Deployments)

Best for: MySQL Router, ProxySQL, MySQL Shell, and InnoDB Cluster deployments.

⚠️ Prerequisites:

InnoDB Cluster requires a running cluster. This enables Router REST API authentication.

Router REST API uses self-signed HTTPS certificates. Set MYSQL_ROUTER_INSECURE=true to bypass verification.

X Protocol: InnoDB Cluster includes the MySQL X Plugin by default. Set MYSQL_XPORT to the Router's X Protocol port (e.g., 6448). This enables mysqlsh_import_json and docstore tools

See MySQL Ecosystem Setup Guide for detailed instructions

config.json

{
  "mcpServers": {
    "mysql-mcp-ecosystem": {
      "command": "npx",
      "args": [
        "-y",
        "@neverinfamous/mysql-mcp",
        "--transport",
        "stdio",
        "--tool-filter",
        "ecosystem"
      ],
      "env": {
        "MYSQL_HOST": "localhost",
        "MYSQL_PORT": "3307",
        "MYSQL_XPORT": "6448",
        "MYSQL_USER": "cluster_admin",
        "MYSQL_PASSWORD": "cluster_password",
        "MYSQL_DATABASE": "testdb",
        "MYSQL_ROUTER_URL": "https://localhost:8443",
        "MYSQL_ROUTER_USER": "rest_api",
        "MYSQL_ROUTER_PASSWORD": "router_password",
        "MYSQL_ROUTER_INSECURE": "true",
        "PROXYSQL_HOST": "localhost",
        "PROXYSQL_PORT": "6032",
        "PROXYSQL_USER": "radmin",
        "PROXYSQL_PASSWORD": "radmin",
        "MYSQLSH_PATH": "mysqlsh"
      },
      "timeout": 600
    }
  }
}

Note: Port 6448 is the standard MySQL Router X Protocol port.

Customization Notes:

Replace /path/to/mysql-mcp/ with your actual installation path. This is only needed when building from source. It is also required when running local files directly.
Update credentials with your actual values
For Windows: Use forward slashes (e.g., C:/mysql-mcp/dist/cli.js) or escape backslashes
For Windows MySQL Shell: "MYSQLSH_PATH": "C:\\Program Files\\MySQL\\MySQL Shell\\bin\\mysqlsh.exe"
Router Authentication: Router REST API authenticates against the InnoDB Cluster metadata. The cluster must be running for authentication to work.
Cluster Resource: Connect to an InnoDB Cluster node. This unlocks the mysql://cluster resource

📖 See the Configuration Wiki for more configuration options.

🔗 Integrate Any MySQL Environment

Scenario	Host to Use	Example Connection String
MySQL on host machine	`localhost` / `host.docker.internal`	`mysql://mcp_user:secure_password@localhost:3306/testdb`
MySQL in Docker	Container name or network	`mysql://mcp_user:secure_password@mysql-container:3306/testdb`
Remote/Cloud MySQL	Hostname or IP	`mysql://mcp_user:secure_password@db.example.com:3306/testdb`

Connect to MySQL on Host Machine

For native local installations, use localhost. If running the server in Docker, use host.docker.internal:

config.json

[
  "--mysql",
  "mysql://mcp_user:secure_password@host.docker.internal:3306/testdb"
]

Connect to MySQL in Another Docker Container

For Docker setups, use host.docker.internal. For Docker Compose, use the mysql service name.

Create a network and run MySQL:

Terminal

docker network create mynet
docker run -d --name mysql-db --network mynet -e MYSQL_ROOT_PASSWORD=pass mysql:latest

Run MCP server on the same network:

Terminal

docker run -i --rm --network mynet writenotenow/mysql-mcp:latest \
  --transport stdio --mysql "mysql://mcp_user:secure_password@mysql-db:3306/testdb"

Connect to Remote/Cloud MySQL (RDS, Cloud SQL, etc.)

Use the remote hostname directly:

config.json

[
  "--mysql",
  "mysql://mcp_user:secure_password@your-instance.region.rds.amazonaws.com:3306/testdb"
]

Provider	Example Hostname
AWS RDS	`your-instance.xxxx.us-east-1.rds.amazonaws.com`
Google Cloud SQL	`project:region:instance` (via Cloud SQL Proxy)
Azure MySQL	`your-server.mysql.database.azure.com`
PlanetScale	`aws.connect.psdb.cloud` (SSL required)
DigitalOcean	`your-cluster-do-user-xxx.db.ondigitalocean.com`

Tip: Ensure remote MySQL servers allow connections from Docker's IP range. Verify firewalls/security groups permit port 3306.

🛠️ Optimize Limits with Tool Filtering

[!IMPORTANT] AI IDEs like Cursor have tool limits. Filter tools to ensure compatibility with IDE limits. We offer many specialized tools. All shortcuts and tool groups include Code Mode by default. To exclude it, add -codemode to your filter: --tool-filter core,json,-codemode

Discover Filtering Options

The --tool-filter argument accepts shortcuts, groups, or tool names — mix and match freely:

Filter Pattern	Example	Description
Shortcut only	`starter`	Use a predefined bundle
Groups only	`core,json,transactions`	Combine individual groups
Shortcut + Group	`starter,spatial`	Extend a shortcut
Shortcut - Tool	`starter,-mysql_drop_table`	Remove specific tools

Use Predefined Shortcuts

Shortcut	Use Case	What's Included
`starter`	Standard Package	core, json, transactions, text, codemode
`essential`	Minimal footprint	core, transactions, codemode
`dev-power`	Power Developer	core, schema, performance, fulltext, transactions, codemode
`dev-analytics`	Developer Analytics	core, stats, performance, codemode
`ai-data-nosql`	AI Data NoSQL	core, json, docstore, codemode
`ai-search`	AI Search	core, text, fulltext, vector, codemode
`ai-spatial`	AI Spatial Analyst	core, spatial, transactions, codemode
`ai-vector`	AI Vector Analyst	core, vector, fulltext, codemode
`dba-monitor`	DBA Monitoring	core, monitoring, performance, sysschema, optimization, codemode
`dba-manage`	DBA Management	core, admin, backup, replication, partitioning, events, codemode
`dba-secure`	DBA Security	core, security, roles, transactions, codemode
`dba-schema`	DBA Schema	core, schema, introspection, migration, codemode
`base-relational`	Base Relational	core, transactions, text, schema, codemode
`base-analytics`	Base Analytics	stats, events, codemode
`base-nosql`	Base NoSQL	docstore, spatial, vector, codemode
`ecosystem`	External Tools	cluster, proxysql, router, shell, codemode

Filter by Tool Groups

Note: Code Mode (mysql_execute_code) is automatically added to all groups.

Group	Description
`codemode`	Code Mode (sandboxed code execution) 🌟 Recommended
`core`	Read/write queries, tables, indexes
`transactions`	BEGIN, COMMIT, ROLLBACK, savepoints
`json`	JSON functions, merge, diff, stats
`text`	REGEXP, LIKE, SOUNDEX
`fulltext`	Natural language & boolean search
`performance`	EXPLAIN, query analysis, anomaly detection
`optimization`	Index hints, database-wide audits, EXPLAIN recommendations
`admin`	OPTIMIZE, ANALYZE, CHECK, insights
`monitoring`	PROCESSLIST, status variables
`backup`	Export, import, mysqldump, audit backups
`replication`	Master/slave, binlog
`partitioning`	Partition management
`schema`	Views, procedures, triggers, constraints
`introspection`	Dependency graphs, cascade simulation, snapshots
`migration`	Schema versioning, apply, rollback, history
`shell`	MySQL Shell utilities
`events`	Event Scheduler management
`sysschema`	sys schema diagnostics
`stats`	Statistical analysis, window functions, sampling
`spatial`	Spatial/GIS operations
`security`	Audit, SSL, encryption, masking
`roles`	MySQL role management
`docstore`	Document Store collections
`cluster`	Group Replication, InnoDB Cluster
`proxysql`	ProxySQL management
`router`	MySQL Router REST API
`vector`	Vector embeddings, KNN search, hybrid search

Review Syntax Reference

Legacy Syntax (still supported): If you start with a negative filter (e.g., -ecosystem), it enables all tools first. It then subtracts the specified tools.

Prefix	Target	Example	Effect
(none)	Shortcut	`starter`	Whitelist Mode: Enable ONLY this shortcut
(none)	Group	`core`	Whitelist Mode: Enable ONLY this group
(none)	Tool	`mysql_read_query`	Whitelist Mode: Enable ONLY this tool
`+`	Group	`+spatial`	Add tools from this group to current set
`-`	Group	`-admin`	Remove tools in this group from current set
`+`	Tool	`+mysql_explain`	Add one specific tool
`-`	Tool	`-mysql_drop_table`	Remove one specific tool

Customize Tool Selection

List tool names without + prefix to create a custom whitelist.

The easiest way to filter is using whitelist mode. Simply specify the shortcut you want. Everything else is automatically disabled.

bash

# Enable specific tools (whitelist mode)
--tool-filter "mysql_read_query,mysql_write_query,mysql_list_tables"

# Mix tools from different groups
--tool-filter "mysql_read_query,mysql_explain,mysql_json_extract"

# Combine with a shortcut or group
--tool-filter "starter,+mysql_spatial_distance,+mysql_json_diff"

Use this for automated clients requiring a minimal capability set.

📖 See the Tool Filtering Wiki for advanced examples.

🔧 Customize with Advanced Configuration

See the configuration templates in the project root for setup details.

For specialized setups, see these Wiki pages:

Topic	Description
MySQL Router	Configure Router REST API access for InnoDB Cluster
ProxySQL	Configure ProxySQL admin interface access
MySQL Shell	Configure MySQL Shell for dump/load operations

⚡ Maximize Server Performance

The server caches schema metadata to reduce repeated queries during tool/resource invocations.

Review Performance Benchmarks

The server handles millions of ops/sec across core execution paths. This ensures minimal latency and maximum throughput. Every component is tuned for enterprise-scale workloads. Enjoy sub-millisecond sandbox cold starts and optimized reverse lookups.

Benchmark Baselines:

parseToolFilter: ~32,000-62,000 ops/sec
CodeModeSandbox.create cold start: ~2.78M ops/sec
Sandbox dispose: ~2.37M ops/sec
SandboxPool init: ~109k ops/sec
Set.has tool check: ~4.4M ops/sec
Map.get reverse lookup: ~4.5M ops/sec
Map.get URI match: ~5.1M ops/sec
validateCode safe short: ~173k ops/sec
validateCode blocked: ~298k ops/sec
checkRateLimit: ~205k ops/sec
sanitizeResult small payload: ~1.49M ops/sec
prompt schema parse: ~1.3M ops/sec

Tip: Lower METADATA_CACHE_TTL_MS for development (e.g., 5000). Increase it for production with stable schemas (e.g., 300000 = 5 min).

Payload optimization: Tools support summary: true and limit parameters. These condense large payloads.

🎛️ Master Server Configuration

Configure CLI Options

Note: Items marked with — in the CLI flag column are configured exclusively via environment variables.

Option	Environment Variable	Description
`--config`, `-c`	—	Configuration file path (.yaml or .json)
`--dump-config`	—	Dump current configuration to stdout and exit
`--version`, `-v`	—	Show version number
`--help`, `-h`	—	Show help
`--json`	—	Output in JSON format
`--transport`, `-t`	—	Transport type: stdio, http, sse (default: stdio)
`--port`, `-p`	`MYSQLMCP_PORT`	HTTP port for http transport
`--server-host`	`MCP_HOST`	Host to bind HTTP transport to (default: localhost)
`--mysql`, `-m`	—	MySQL connection string
`--mysql-host`	`MYSQL_HOST`	MySQL host
`--mysql-port`	`MYSQL_PORT`	MySQL port
`--mysql-user`	`MYSQL_USER`	MySQL username
`--mysql-password`	`MYSQL_PASSWORD`	MySQL password
`--mysql-database`	`MYSQL_DATABASE`	MySQL database name
`--pool-size`	`MYSQL_POOL_SIZE`	Connection pool size (default: 10)
`--pool-timeout`	—	Connection acquire timeout in ms (default: 30000)
`--pool-queue-limit`	—	Queue limit for waiting requests (default: 0)
`--tool-filter`, `-f`	`TOOL_FILTER`	Tool filter string
`--name`	—	Server name
`--auth-token`	`MCP_AUTH_TOKEN`	Simple bearer token for HTTP authentication
`--stateless`	—	Enable stateless HTTP mode
`--trust-proxy`	`TRUST_PROXY`	Trust X-Forwarded-For for client IP
`--enable-hsts`	`MCP_ENABLE_HSTS`	Enable HTTP Strict Transport Security
`--metrics-export`	`MCP_METRICS_EXPORT`	Metrics export format (e.g., prometheus)
`--log-level`	`LOG_LEVEL`	Log level: debug, info, warn, error
`--allowed-io-roots`	`ALLOWED_IO_ROOTS`	JSON array or comma list of allowed paths for all file I/O operations
`--audit-log`	`MCP_AUDIT_LOG`	File path for writing audit logs (write-path)
—	`AUDIT_LOG_PATH`	File path for the exporter to read audit logs (read-path)
`--audit-backup`	—	Enable pre-mutation snapshots
`--audit-reads`	—	Include read-scope tool calls in the audit log
`--audit-redact`	—	Redact sensitive arguments in the audit log
`--audit-log-max-size`	—	Max file size before rotation (bytes)
`--audit-backup-data`	—	Include sample data in pre-mutation snapshots
`--audit-backup-max-size`	—	Max table size in bytes for data capture
`--oauth-enabled`, `-o`	`OAUTH_ENABLED`	Enable OAuth 2.1 authentication
`--oauth-issuer`	`OAUTH_ISSUER`	Authorization server URL
`--oauth-audience`	`OAUTH_AUDIENCE`	Expected token audience
`--oauth-jwks-uri`	`OAUTH_JWKS_URI`	JWKS URI (auto-discovered)
`--oauth-clock-tolerance`	`OAUTH_CLOCK_TOLERANCE`	Clock tolerance in seconds
—	`MYSQL_ROUTER_URL`	MySQL Router URL
—	`MYSQL_ROUTER_USER`	MySQL Router user
—	`MYSQL_ROUTER_PASSWORD`	MySQL Router password
—	`MYSQL_ROUTER_INSECURE`	Bypass Router TLS verification
—	`MYSQL_ROUTER_API_VERSION`	MySQL Router REST API version (default: /api/20190715)
—	`PROXYSQL_HOST`	ProxySQL host
—	`PROXYSQL_PORT`	ProxySQL port
—	`PROXYSQL_USER`	ProxySQL user
—	`PROXYSQL_PASSWORD`	ProxySQL password
—	`MYSQLSH_PATH`	Path to MySQL Shell executable
—	`MYSQL_XPORT`	MySQL X Protocol port (default 33060)
—	`CODEMODE_ISOLATION`	Code Mode isolation level (controls V8 memory limits and strictness)
—	`CODEMODE_MAX_RESULT_SIZE`	Max Code Mode result payload in bytes
—	`METADATA_CACHE_TTL_MS`	Cache TTL for schema metadata
—	`REDIS_URL`	Redis connection URL (used for rate limiting)
—	`MCP_RATE_LIMIT_MAX`	Max HTTP requests per minute per IP (default 100)
—	`CODEMODE_RATE_LIMIT_MAX`	Max Code Mode executions per minute (default 60)

Priority: When both --auth-token and --oauth-enabled are set, OAuth 2.1 takes precedence. If neither is configured, the server warns and runs without authentication.

Enforce Scopes

See Enforce OAuth Scopes.

📖 See the OAuth Wiki for Keycloak setup and detailed configuration.

💻 Accelerate Development by Contributing

See Build From Source above for setup. After cloning:

bash

pnpm run lint
pnpm run typecheck
pnpm test
pnpm run test:e2e  # Run individually to avoid timeouts

Debug with MCP Inspector

Use MCP Inspector to visually test and debug mysql-mcp:

Build the server first:

bash

pnpm run build

Launch Inspector with mysql-mcp:

Terminal

npx @modelcontextprotocol/inspector node dist/cli.js \
  --transport stdio \
  --mysql mysql://mcp_user:secure_password@localhost:3306/testdb

Open http://localhost:5173 to browse all tools, resources, and prompts interactively.

CLI mode for scripting:

List all tools:

Terminal

npx @modelcontextprotocol/inspector --cli node dist/cli.js \
  --transport stdio --mysql mysql://... \
  --method tools/list

Call a specific tool:

Terminal

npx @modelcontextprotocol/inspector --cli node dist/cli.js \
  --transport stdio --mysql mysql://... \
  --method tools/call --tool-name mysql_list_tables

📖 See the MCP Inspector Wiki for detailed usage.

Run Unit Tests

The project maintains high test coverage using Vitest.

bash

pnpm test

Run coverage report:

bash

pnpm run test:coverage

Test Infrastructure:

Centralized mock factories in src/__tests__/mocks/
All test files use shared mocks for consistency
Tests run without database connection (fully mocked)
Unit tests are mocked. The E2E and stress suites require a live database connection.

Execute Benchmarks

The project includes a performance benchmarking suite. It tracks efficiency of critical paths. These include Code Mode sandbox initialization, tool filtering, and URI routing.

bash

pnpm run bench

Contributing Guidelines • Security Policy • MIT License • Code of Conduct

MySQL MCP Server (mysql-mcp)

💎 Value Proposition

🎯 Leverage Core Benefits

🤖 Automate Tasks with Guided Workflows

📊 Improve Observability with Resources

🚀 Deploy Your AI Database

Meet Prerequisites

Install the Server

Install via NPM / PNPM

Run with Docker

Enable Observability via Docker Compose

Follow Datadog & OpenTelemetry Observability Rules

Build From Source

🏗️ Use Infrastructure Templates

⚡ Optimize Token Usage with Code Mode

Enforce Engine-Level Restrictions

Validate Code Statically

Protect the Runtime

⚡ Run Only Code Mode

🌐 Enable Remote Access via Streamable & Stateless HTTP

Use Streamable HTTP (Recommended)

Run Statelessly

Access Utility Endpoints

🔐 Protect Your Data with Authentication

Authenticate with Bearer Token (--auth-token)

Authenticate with OAuth 2.1

Enforce OAuth Scopes

Ensure RFC Compliance

⚡ Simplify AI Integration with Client Configs

Install Agent Skills

Configure IDE Settings

Option 1: Code Mode (Maximum Token Savings, 🌟 Recommended)

Option 2: Cluster (Tools for InnoDB Cluster Monitoring)

Option 3: Ecosystem (Tools for InnoDB Cluster Deployments)

🔗 Integrate Any MySQL Environment

Connect to MySQL on Host Machine

Connect to MySQL in Another Docker Container

Connect to Remote/Cloud MySQL (RDS, Cloud SQL, etc.)

🛠️ Optimize Limits with Tool Filtering

Discover Filtering Options

Use Predefined Shortcuts

Filter by Tool Groups

Review Syntax Reference

Customize Tool Selection

🔧 Customize with Advanced Configuration

⚡ Maximize Server Performance

Review Performance Benchmarks

🎛️ Master Server Configuration

Configure CLI Options

Enforce Scopes

💻 Accelerate Development by Contributing

Debug with MCP Inspector

Run Unit Tests

Execute Benchmarks

Authenticate with Bearer Token (`--auth-token`)