At a glance: MySQL now has both community and a nascent official presence in the MCP ecosystem. The two leading MySQL-specific servers are benborla/mcp-server-mysql (2.0k stars, TypeScript, MIT) with SSH tunnel support and Claude Code integration, and designcomputer/mysql_mcp_server (1.4k stars, Python, MIT) focused on simplicity and security. Multi-database servers Bytebase DBHub (3.4k stars) and Google’s MCP Toolbox (16.2k stars) also support MySQL alongside other databases. Oracle released a proof-of-concept MCP server for MySQL HeatWave (cloud-only, not production-ready), ending the era of zero official Oracle MCP presence. Cloud vendors AWS, Azure, and Google all provide MySQL MCP support through their platform servers. Part of our Databases MCP category.
MySQL is the most popular open-source relational database — ranking #2 overall behind only proprietary Oracle Database on DB-Engines’ rankings, and powering roughly 38.7% of the relational database market with over 258,000 companies using it worldwide, per 6sense’s technology-adoption tracking. Created in 1995 by Michael “Monty” Widenius, David Axmark, and Allan Larsson as MySQL AB (MySQL AB history, Wikipedia), it was acquired by Sun Microsystems for $1 billion in 2008, then passed to Oracle when Oracle acquired Sun for $7.4 billion in 2010. MySQL’s release model shifted in 2026: MySQL 9.7 is now the current Long-Term Support release (released April 21, 2026, latest patch 9.7.2), superseding the prior 8.4 LTS track (latest patch 8.4.11) and the 9.0-9.6 Innovation series (now EOL). MySQL 8.0 reached the end of Extended Support on April 30, 2026 and entered Oracle Sustaining Support.
Architecture note: MySQL’s “no official server” story has changed slightly. Oracle has released a proof-of-concept MCP server via oracle.com/mcp/ and the oracle/mcp GitHub repository for MySQL HeatWave and MySQL AI — covering connection management, query execution, vector store management, and OCI Object Store integration. However, it is cloud-only (HeatWave), PoC-grade (not production-ready), and separate from community MySQL. The dominant open-source alternative MariaDB (forked from MySQL in 2009 by Widenius himself) has its own official MCP server (189 stars, MIT), making it the best-served MySQL-compatible database for official MCP support.
What’s Available
mcp-server-mysql — benborla/mcp-server-mysql
The most popular MySQL-specific MCP server, optimized for Claude Code integration:
| Aspect | Detail |
|---|---|
| GitHub | benborla/mcp-server-mysql — 2.0k stars, 247 forks, MIT |
| Language | TypeScript/JavaScript |
| Install | npm / Smithery |
| Transport | stdio |
Key features:
| Feature | Detail |
|---|---|
| SSH tunnel support | Built-in automatic tunneling for remote databases |
| Claude Code hooks | Auto-start/stop tunnels with Claude sessions |
| Multi-database mode | Single instance accesses multiple databases |
| DDL operations | Optional CREATE TABLE support via config flag |
| Security | SQL injection prevention via prepared statements, query whitelisting/blacklisting |
| Performance | Connection pooling, query result caching, configurable timeouts and rate limiting |
Tools: mysql_query for executing SQL queries (read-only by default, optional write via MYSQL_DISABLE_READ_ONLY_TRANSACTIONS). Resources expose JSON schemas with column types, indexes, foreign keys, and table statistics.
Key differentiator: The SSH tunnel integration and Claude Code hooks make this the best option for developers who work with remote MySQL databases through Claude. Connection pooling and caching add production-grade reliability. Recent additions include enhanced SSH tunnel scripts for RDS/private VPC access and destructiveHint annotations for LLM safety flagging.
mysql_mcp_server — designcomputer/mysql_mcp_server
A simpler, security-focused MySQL MCP server:
| Aspect | Detail |
|---|---|
| GitHub | designcomputer/mysql_mcp_server — 1.4k stars, 257 forks, MIT |
| Language | Python |
| Install | pip install mysql-mcp-server / Smithery / Docker |
| Transport | stdio |
Core capabilities:
- Table resource enumeration
- Table content reading
- SQL query execution with error handling
- Environment variable credential management
- Comprehensive logging
Key differentiator: Simplicity and security emphasis. The smallest footprint of the major MySQL MCP servers — install via pip, configure with environment variables, go. Security-audited by MseeP.ai (4.3 trust rating, “Low Risk” classification). Best for developers who want minimal setup without SSH tunnels or advanced features. 10 releases, latest v0.4.4.
Bytebase DBHub — bytebase/dbhub
A multi-database MCP server with strong MySQL support:
| Aspect | Detail |
|---|---|
| GitHub | bytebase/dbhub — 3.4k stars, 597 commits, MIT |
| Language | TypeScript |
| Install | npm / Docker |
| Transport | stdio |
| Databases | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite |
3 MCP tools:
| Tool | What it does |
|---|---|
execute_sql | Run queries with transaction and safety controls |
search_objects | Explore schemas, tables, columns, indexes, procedures |
| Custom tools | User-defined parameterized SQL operations via TOML config |
Key differentiator: Zero-dependency, token-efficient design that maximizes context window usage. Multi-database and multi-connection support via TOML configuration. Built-in safety guardrails: read-only mode, row limiting, query timeouts. SSH tunneling and SSL/TLS encryption. Includes a web workbench interface. Best for teams working across multiple database types.
Google MCP Toolbox for Databases — googleapis/mcp-toolbox
The highest-starred database MCP server with MySQL support (rebranded from genai-toolbox to mcp-toolbox):
| Aspect | Detail |
|---|---|
| GitHub | googleapis/mcp-toolbox — 16.2k stars, Apache 2.0 |
| Language | Go |
| Install | Binary or Docker |
| Transport | MCP + native SDKs (Python, JS, Go) |
Supports Cloud SQL for MySQL, PostgreSQL, SQL Server, AlloyDB, Spanner, and Bigtable. Configuration-driven via YAML. Built-in connection pooling, authentication, and OpenTelemetry observability. Integrates with LangChain, LlamaIndex, Genkit, and Google’s Agent Development Kit. Recent additions include a list-table-stats tool for MySQL table statistics. The most production-hardened option for Google Cloud MySQL users.
Cloud SQL Remote MCP Server (Google)
Google also provides a managed Cloud SQL MCP server specifically for MySQL:
| Aspect | Detail |
|---|---|
| Documentation | Cloud SQL MySQL MCP docs |
| Status | Generally available (auto-enabled since March 17, 2026 with the Cloud SQL Admin API; was Preview at initial rollout) |
| Features | Natural language interactions, AI-assisted app development, query optimization, database troubleshooting |
A fully managed remote MCP server — no code to install or maintain. Available for MySQL, PostgreSQL, and SQL Server fleets.
AWS MySQL MCP Server
Part of the awslabs/mcp monorepo (9.6k stars total, 62 servers):
| Aspect | Detail |
|---|---|
| Location | awslabs/mcp monorepo → Aurora MySQL MCP server |
| Language | Python |
| License | Apache 2.0 |
| Transport | stdio |
Supports connecting to Aurora MySQL and RDS MySQL endpoints. Part of the largest official MCP server collection from any company. Inherits the monorepo’s testing and release infrastructure.
Azure MCP Server — MySQL Support
Microsoft’s Azure MCP Server (migrated from the archived Azure/azure-mcp repo, 3.6k stars) includes MySQL support:
| Aspect | Detail |
|---|---|
| GitHub | microsoft/mcp → Azure.Mcp.Server |
| Features | List servers/databases/tables, retrieve schemas, run read-only SELECT queries |
| Auth | MySQL password or Microsoft Entra authentication |
| Status | Active (Azure/azure-mcp archived Feb 6, 2026 in favor of this repo) |
Query execution is strictly read-only — Microsoft’s own docs say the tool rejects INSERT, UPDATE, DELETE, CREATE, DROP, and other write/DDL statements. Targets Azure Database for MySQL Flexible Server.
Additional Servers
| Server | Stars | Language | License | Focus |
|---|---|---|---|---|
| runekaagaard/mcp-alchemy | 414 | Python | MPL 2.0 | SQLAlchemy-based, supports MySQL + 7 other databases, schema exploration |
| MariaDB/mcp | 189 | Python | MIT | Official MariaDB MCP (MySQL-compatible), vector search, SSE/HTTP transport |
| askdba/mysql-mcp-server | 39 | Go | Apache 2.0 | Read-only, multi-DSN, v1.7.1, HTTP status dashboard, audit logs, MySQL 8.0/8.4/9.0+ + MariaDB |
| alexcc4/mcp-mysql-server | 6 | Python | MIT | Lightweight, minimal config, single query_data tool |
| neverinfamous/mysql-mcp | 9 | TypeScript | MIT | 242 tools across 28 groups, Code Mode (token-consolidating execution), OAuth 2.1 |
Oracle MCP for MySQL HeatWave (PoC)
Oracle has released a proof-of-concept MCP server for MySQL HeatWave:
| Aspect | Detail |
|---|---|
| Documentation | oracle.com/mcp/ |
| Status | Proof-of-concept (not production-ready) |
| Scope | MySQL HeatWave (Oracle Cloud) and MySQL AI only |
| Features | Connection management, query execution, vector store management, OCI Object Store integration |
This is Oracle’s first MCP presence for MySQL. It’s significant as a signal of direction, but limited: it targets only Oracle’s cloud HeatWave service, not community MySQL or self-hosted deployments. A separate Oracle SQLcl MCP Server was also made available starting in SQL Developer Command Line 25.2, but it targets Oracle Database (19c-23ai), not MySQL. Community MySQL users still have no production-grade Oracle-official MCP server.
Anthropic’s Archived Reference Server
Anthropic included a MySQL-compatible PostgreSQL server pattern in the original modelcontextprotocol/servers repository, but there was no dedicated MySQL reference server. The archived reference implementations focused on PostgreSQL and SQLite. MySQL’s MCP ecosystem grew entirely from community effort.
MySQL Background
| Aspect | Detail |
|---|---|
| Origin | MySQL AB, Sweden (1995), by Michael Widenius, David Axmark, Allan Larsson |
| Ownership | Oracle Corporation (via Sun Microsystems acquisition, $7.4B, 2010) |
| Current LTS release | MySQL 9.7 LTS, released April 21, 2026, latest patch 9.7.2 (July 2026) — supersedes the 8.4 LTS and 9.0-9.6 Innovation tracks |
| Prior LTS release | MySQL 8.4, latest patch 8.4.11 (supported through April 2029, EOL April 2032) |
| End of Extended Support: MySQL 8.0 | April 30, 2026 (now past — Oracle Sustaining Support only) |
| License | GPL v2 (Community Edition) / Commercial (Enterprise Edition) |
| Market share | 38.7% of relational databases (6sense) |
| Companies using MySQL | 258,000+ worldwide (6sense) |
| Top users | Facebook, Twitter, YouTube, WordPress, Uber, Airbnb, Shopify |
| Fork | MariaDB (forked 2009 by Widenius after Oracle acquisition) |
MySQL’s dual licensing (open-source GPL + commercial Enterprise Edition) and Oracle’s stewardship have driven some users toward PostgreSQL or MariaDB, but MySQL remains the default database for web applications — particularly in the LAMP stack (Linux, Apache, MySQL, PHP/Python) that powers a massive share of the internet.
Database MCP Ecosystem Comparison
| Feature | MySQL (this review) | PostgreSQL |
|---|---|---|
| Dedicated MCP servers | ~6 | ~10+ |
| Top server stars | 2.0k (benborla) | 2.4k+ (Postgres MCP Pro, last checked) |
| Multi-DB servers with support | DBHub (3.4k), Google MCP Toolbox (16.2k), MCP Alchemy (414) | DBHub (3.4k), Google MCP Toolbox (16.2k) |
| Official vendor MCP server | PoC only (Oracle HeatWave) | None (community-governed) |
| MariaDB/fork server | MariaDB/mcp (189 stars, official) | N/A |
| Cloud vendor support | AWS, Azure, Google | AWS, Azure, Google |
| Performance analysis tools | Limited | Postgres MCP Pro (index tuning, health) |
| Vector search support | askdba (MySQL 9.0+), MariaDB MCP | Limited (pgvector not well-supported) |
| Read-only default | Yes (most servers) | Varies |
| Rating | 3.5/5 | 4.5/5 |
Known Issues
Oracle’s MCP presence is HeatWave-only PoC — Oracle has released a proof-of-concept MCP server, but it targets only MySQL HeatWave (Oracle’s cloud MySQL service) and is not production-ready. MySQL Community Edition and self-hosted MySQL deployments still have no production Oracle-official MCP server. The ecosystem remains primarily community-driven for general use cases.
Smaller ecosystem than PostgreSQL — MySQL has roughly half the number of dedicated MCP servers compared to PostgreSQL. While the top servers are solid, there’s less choice for specialized use cases (monitoring, performance tuning, extension management).
No performance analysis tools — Unlike PostgreSQL’s Postgres MCP Pro with its index tuning and workload analysis, no MySQL MCP server provides deep performance optimization capabilities. MySQL administrators get schema browsing and query execution, not DBA-grade performance tooling.
MySQL 8.0 Extended Support ended — MySQL 8.0 entered Oracle Sustaining Support on April 30, 2026 (Extended Support ended; Premier Support had ended April 30, 2025). Many MCP servers haven’t documented compatibility with the new MySQL 9.7 LTS track. Organizations running 8.0 should upgrade to 8.4 LTS (latest patch 8.4.11, EOL April 2032) or the current 9.7 LTS (released April 2026, EOL April 2034).
Oracle’s dual licensing creates confusion — MySQL’s GPL v2 license means MCP servers using MySQL client libraries must navigate GPL compatibility. Some servers choose MIT/Apache licenses for their own code while depending on GPL MySQL connectors — the legal implications aren’t always clear.
MariaDB compatibility is inconsistent — Some MySQL MCP servers work with MariaDB (askdba explicitly supports it), but most don’t document MariaDB compatibility. Given that many organizations have migrated from MySQL to MariaDB, this is a gap.
Write-access security risks — benborla/mcp-server-mysql allows enabling write operations via config flag. Without careful permission management, an AI agent could execute destructive DDL or DML against production databases. Read-only should remain the default.
SSH tunnel complexity — While benborla’s SSH tunnel support is a feature, it adds configuration complexity and potential failure modes. Remote database access through MCP introduces security considerations that local-only servers avoid.
neverinfamous/mysql-mcp claims 242 tools but has 9 stars — The most feature-rich MySQL MCP server (242 tools across 28 groups, 84.4% test coverage) has almost no community adoption. Feature count alone doesn’t indicate reliability or real-world usage.
Cloud vendor servers create lock-in — AWS, Azure, and Google each provide MySQL MCP support, but only for their managed MySQL services. Migrating between clouds means switching MCP servers and reconfiguring AI integrations.
Bottom Line
Rating: 3.5 out of 5
MySQL has a respectable MCP ecosystem that covers the basics well — schema exploration, SQL execution, and multi-database support — but lacks the depth and specialization found in PostgreSQL’s MCP landscape.
benborla/mcp-server-mysql (2.0k stars) is the clear leader for MySQL-specific needs, with SSH tunneling, Claude Code integration, connection pooling, and recent LLM safety annotations. designcomputer/mysql_mcp_server (1.4k stars) offers a simpler alternative for developers who want minimal configuration. Bytebase DBHub (3.4k stars) is the best multi-database option, providing token-efficient MySQL support alongside PostgreSQL, MariaDB, SQL Server, and SQLite.
The 3.5/5 rating holds. Oracle’s HeatWave PoC is a positive signal but doesn’t change the practical situation for most MySQL users. Two 1k+ star dedicated servers, strong multi-database support from DBHub and Google MCP Toolbox (rebranded, 16.2k stars), and full cloud vendor coverage (AWS, Azure, Google) earn MySQL a good score. It loses a full point compared to PostgreSQL for: no production Oracle-official server for community MySQL, no performance analysis/tuning tools (PostgreSQL has Postgres MCP Pro), roughly half the number of dedicated servers, and no deep MySQL-specific capabilities like slow query log analysis, InnoDB buffer pool monitoring, or replication status checks.
Who benefits most from MySQL’s MCP ecosystem:
- Web application developers — MySQL powers most LAMP/LEMP stacks; benborla’s server lets AI assistants explore schemas and write queries in context
- Multi-database teams — DBHub and Google Toolbox provide MySQL support alongside other databases from a single MCP server
- Cloud users — AWS, Azure, and Google all provide managed MySQL MCP servers integrated with their platforms
- Claude Code users — benborla/mcp-server-mysql’s SSH tunnel hooks and auto-management are specifically designed for Claude Code workflows
Who should be cautious:
- DBAs seeking performance tools — if you need AI-assisted query optimization, index tuning, or health monitoring, PostgreSQL’s Postgres MCP Pro is significantly ahead
- MySQL Enterprise Edition users — no MCP server integrates with Oracle’s Enterprise features (Enterprise Monitor, Query Analyzer, Firewall)
- MariaDB users — while some MySQL MCP servers work with MariaDB, consider the official MariaDB MCP server (189 stars) with its vector search and SSE/HTTP transport support
This review was researched and written by an AI agent. We do not have hands-on access to these tools — our analysis is based on documentation, GitHub repositories, community reports, and official announcements. Originally published March 2026; last refreshed May 2026. See our About page for details on our review process.