At a glance: MySQL has a solid community-driven MCP ecosystem — but no official server from Oracle. The two leading MySQL-specific servers are benborla/mcp-server-mysql (1.4k stars, TypeScript, MIT) with SSH tunnel support and Claude Code integration, and designcomputer/mysql_mcp_server (1.2k stars, Python, MIT) focused on simplicity and security. Multi-database servers Bytebase DBHub (2.4k stars) and Google’s MCP Toolbox (13.5k stars) also support MySQL alongside other databases. Cloud vendors AWS, Azure, and Google all provide MySQL MCP support through their platform servers. Part of our Databases MCP category.
MySQL is the world’s most popular open-source relational database — powering roughly 39% of the relational database market with over 235,000 companies using it worldwide. Created in 1995 by Michael “Monty” Widenius, David Axmark, and Allan Larsson as MySQL AB, it was acquired by Sun Microsystems for $1 billion in 2008, then passed to Oracle when Oracle acquired Sun for $5.6 billion in 2010. The latest Innovation release is MySQL 9.6 (January 2026); the current Long-Term Support release is MySQL 8.4.5. MySQL 8.0 reaches end-of-life in April 2026.
Architecture note: Like PostgreSQL, MySQL has no single “official” MCP server from its corporate steward (Oracle). Unlike PostgreSQL, MySQL’s ecosystem is smaller — roughly half the number of dedicated servers. The dominant open-source alternative MariaDB (forked from MySQL in 2009 by Widenius himself) has its own official MCP server (151 stars), making MariaDB the only MySQL-compatible database with a first-party MCP implementation.
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 — 1.4k stars, 181 forks, 222 commits, 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. 34 open issues suggest active community usage.
mysql_mcp_server — designcomputer/mysql_mcp_server
A simpler, security-focused MySQL MCP server:
| Aspect | Detail |
|---|---|
| GitHub | designcomputer/mysql_mcp_server — 1.2k stars, 229 forks, 69 commits, 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. Best for developers who want minimal setup without SSH tunnels or advanced features. 6 releases, last at v0.2.2.
Bytebase DBHub — bytebase/dbhub
A multi-database MCP server with strong MySQL support:
| Aspect | Detail |
|---|---|
| GitHub | bytebase/dbhub — 2.4k stars, 194 forks, 482 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/genai-toolbox
The highest-starred database MCP server with MySQL support:
| Aspect | Detail |
|---|---|
| GitHub | googleapis/genai-toolbox — 13.5k stars, 1.3k forks, 1,614 commits |
| 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. 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 | Preview (auto-enabled after March 17, 2026 with Cloud SQL Admin API) |
| 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 (8,540 stars total, 68 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 Azure/azure-mcp, 1.2k stars) includes MySQL support:
| Aspect | Detail |
|---|---|
| GitHub | microsoft/mcp → Azure.Mcp.Server |
| Features | List databases, list tables, retrieve schemas, execute read queries, insert/update, create/drop tables |
| Auth | MySQL password or Microsoft Entra authentication |
| Status | Active (migrated Feb 2026) |
SELECT-only query capabilities in the management suite. Targets Azure Database for MySQL Flexible Server.
Additional Servers
| Server | Stars | Language | License | Focus |
|---|---|---|---|---|
| runekaagaard/mcp-alchemy | 397 | Python | MPL 2.0 | SQLAlchemy-based, supports MySQL + 7 other databases, schema exploration |
| MariaDB/mcp | 151 | Python | — | Official MariaDB MCP (MySQL-compatible), vector search, SSE/HTTP transport |
| askdba/mysql-mcp-server | 16 | Go | Apache 2.0 | Read-only, multi-DSN, vector search (MySQL 9.0+), MariaDB support |
| alexcc4/mcp-mysql-server | 6 | Python | MIT | Lightweight, minimal config, single query_data tool |
| neverinfamous/mysql-mcp | 3 | TypeScript | MIT | 192 tools across 25 groups, Code Mode (90% token savings), OAuth 2.1 |
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, 2010) |
| Latest Innovation release | MySQL 9.6.0 (January 2026) |
| Latest LTS release | MySQL 8.4.5 |
| End-of-life: MySQL 8.0 | April 2026 |
| License | GPL v2 (Community Edition) / Commercial (Enterprise Edition) |
| Market share | 39.3% of relational databases (6sense) |
| Companies using MySQL | 235,000+ worldwide |
| Top users | Facebook, YouTube, Twitter/X, WordPress, Uber, Netflix, Airbnb, Shopify |
| Cloud Database MySQL market | ~$15 billion (2025), ~15% CAGR through 2033 |
| 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 | 1.4k (benborla) | 2.4k (Postgres MCP Pro) |
| Multi-DB servers with support | DBHub (2.4k), Google (13.5k), MCP Alchemy (397) | DBHub (2.4k), Google (13.5k) |
| Official vendor MCP server | None (Oracle) | None (community-governed) |
| MariaDB/fork server | MariaDB/mcp (151 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
-
No Oracle-official MCP server — Despite owning MySQL, Oracle has not released an MCP server for MySQL Community or Enterprise Edition. The ecosystem is entirely community-driven, which means no guaranteed long-term support from MySQL’s corporate steward.
-
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 end-of-life approaching — MySQL 8.0 reaches EOL in April 2026. Many MCP servers haven’t documented compatibility with MySQL 9.x Innovation releases or the 8.4 LTS track. Users on older versions may face compatibility gaps.
-
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 192 tools but has 3 stars — The most feature-rich MySQL MCP server (192 tools, 25 groups, 2,169 tests) 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 (1.4k stars) is the clear leader for MySQL-specific needs, with SSH tunneling, Claude Code integration, connection pooling, and active development across 222 commits. designcomputer/mysql_mcp_server (1.2k stars) offers a simpler alternative for developers who want minimal configuration. Bytebase DBHub (2.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 reflects solid fundamentals with clear gaps. Two 1k+ star dedicated servers, strong multi-database support from DBHub and Google Toolbox, and full cloud vendor coverage (AWS, Azure, Google) earn MySQL a good score. It loses a full point compared to PostgreSQL for: no Oracle-official server, 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 (151 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. Information is current as of March 2026. See our About page for details on our review process.