MySQL has no first-party MCP server, so Atlas either uses the maintained community server or drives the mysql CLI directly, reading SHOW CREATE TABLE output before it writes an ALTER. Oracle ships only a HeatWave proof of concept, so the practical choice in 2026 is @benborla29/mcp-server-mysql, Google's vendor-neutral MCP Toolbox for Databases, or no server at all.
MySQL has no first-party MCP server
MySQL has no first-party MCP server. Oracle ships only a HeatWave proof of concept, so in 2026 an Atlas user connecting to MySQL picks between the maintained community server, Google's vendor-neutral MCP Toolbox for Databases, and simply letting Atlas drive the mysql CLI.
This is the fact that shapes every other decision on this page. Unlike platforms that publish an official server, MySQL leaves the choice to you, and the HeatWave proof of concept Oracle does ship is not a general MySQL integration. That is not a blocker for Atlas. MySQL has a mature CLI and a well understood introspection surface, so all three routes get Atlas what it actually needs: the real schema, the real charset, and the real column definitions, before it writes a single ALTER statement.
Adding the community MySQL MCP server to Atlas
The maintained community server is @benborla29/mcp-server-mysql. Add it with atlas mcp add mysql --env MYSQL_HOST=127.0.0.1 --env MYSQL_PORT=3306 --env MYSQL_USER=$MYSQL_USER --env MYSQL_PASS=$MYSQL_PASS --env MYSQL_DB=$MYSQL_DB -- npx -y @benborla29/mcp-server-mysql, passing all five connection variables through the environment.
The community server takes its connection details as five separate environment variables rather than a single URI: MYSQL_HOST, MYSQL_PORT, MYSQL_USER, MYSQL_PASS, and MYSQL_DB. Passing MYSQL_PASS through the environment rather than an argument keeps the password out of the process list. Note the port default of 3306 and the host default of 127.0.0.1, both of which you will change for anything other than a local database. Once registered, the server gives Atlas the ability to run SQL against the database, which brings the caution in the next section.
Point the MySQL MCP server at a least-privilege user
Point @benborla29/mcp-server-mysql at a read replica or a least-privilege user, because Atlas will execute whatever SQL it composes. In 2026 that single sentence is the whole security model for the community MySQL server: it does not gate writes for you, so the database grants have to.
Unlike servers that ship a read-only mode, the community MySQL server executes the SQL Atlas hands it. That makes MYSQL_USER the control surface. Give Atlas a user with SELECT and SHOW privileges and nothing else, or point MYSQL_HOST at a read replica, and the worst case becomes an expensive query rather than a dropped table. Do the grant work before you add the server, not after. If Atlas needs to write, let it write a migration file that you review and apply yourself, which is the workflow described further down.
Google's MCP Toolbox for Databases as an alternative
Google's MCP Toolbox for Databases, published as googleapis/mcp-toolbox, is a vendor-neutral alternative that covers MySQL and Postgres from one server. For an Atlas user running both databases in 2026, it means one MCP configuration instead of two separate community servers with different environment variable conventions.
Most teams that run MySQL also run Postgres somewhere, and maintaining two unrelated MCP servers with two credential styles is friction that adds up. googleapis/mcp-toolbox covers both from a single server, and being vendor-neutral it is not tied to a particular cloud. Weigh it against @benborla29/mcp-server-mysql on the basis of which one you would rather keep updated. Either way, the same rule applies: the database user Atlas connects as defines what Atlas can do, so provision it narrowly.
The zero-install path: Atlas driving the mysql CLI
The zero-install path is the mysql CLI. Let Atlas shell out to mysql -e and gate it with permission.bash set to ask. No MCP server, no new dependency, and in 2026 every statement Atlas wants to run stops in front of you for an explicit approval before it touches the database.
Atlas has a bash tool, and mysql is already installed on any machine that talks to MySQL. That is a complete integration on its own. Atlas composes the statement, runs it with mysql -e, and reads the output. permission.bash set to ask is what makes this safe: you see the exact SQL before it executes, every time, which is arguably tighter oversight than an MCP server that runs queries silently. The cost is a slower loop, because you are approving each call. For schema reads and migration review, most teams find that acceptable.
The daily workflow: SHOW CREATE TABLE, then the ALTER
The Atlas and MySQL workflow in 2026 has a fixed first step. Ask Atlas to read SHOW CREATE TABLE output first, so the ALTER it writes matches the real schema and charset. Charset and collation are where MySQL migrations most often go wrong, and SHOW CREATE TABLE is where they are stated plainly.
A model writing an ALTER TABLE from memory will get the column right and the charset wrong, and a charset mismatch is the kind of bug that surfaces months later as mangled text. SHOW CREATE TABLE gives Atlas the ground truth: the exact column definitions, the engine, the charset, and the collation the table was actually created with. With that in hand, the ALTER it writes is consistent with what is already there. Have Atlas produce both the up and the down migration as a diff you review, never as a live statement, so the change is reversible and recorded.
Setup
- 01Understand the constraint first: MySQL has no first-party MCP server, since Oracle ships only a HeatWave proof of concept.
- 02Add the maintained community server: atlas mcp add mysql --env MYSQL_HOST=127.0.0.1 --env MYSQL_PORT=3306 --env MYSQL_USER=$MYSQL_USER --env MYSQL_PASS=$MYSQL_PASS --env MYSQL_DB=$MYSQL_DB -- npx -y @benborla29/mcp-server-mysql
- 03Point it at a read replica or a least-privilege user, because Atlas will execute whatever SQL it composes.
- 04If you run both MySQL and Postgres, consider Google's MCP Toolbox for Databases (googleapis/mcp-toolbox), a vendor-neutral server that covers both.
- 05For a zero-install setup, skip MCP entirely: let Atlas shell out to mysql -e and gate it with permission.bash set to ask.
- 06Ask Atlas to read SHOW CREATE TABLE output first, so the ALTER it writes matches the real schema and charset.
- 07Have Atlas produce both the up and the down migration as a diff you review, never as a live statement.
Frequently asked questions
- is there an official mysql mcp server
- No. MySQL has no first-party MCP server, and Oracle ships only a HeatWave proof of concept. Use the maintained community server or the mysql CLI.
- how to connect atlas to mysql
- Run atlas mcp add mysql --env MYSQL_HOST=127.0.0.1 --env MYSQL_PORT=3306 --env MYSQL_USER=$MYSQL_USER --env MYSQL_PASS=$MYSQL_PASS --env MYSQL_DB=$MYSQL_DB -- npx -y @benborla29/mcp-server-mysql
- is the community mysql mcp server safe
- Only as safe as the user you give it. Point it at a read replica or a least-privilege user, because Atlas will execute whatever SQL it composes.
- can i use one mcp server for both mysql and postgres
- Yes. Google's MCP Toolbox for Databases (googleapis/mcp-toolbox) is a vendor-neutral alternative that covers MySQL and Postgres from one server.
- can atlas use mysql without an mcp server
- Yes. The zero-install path is the mysql CLI: let Atlas shell out to mysql -e and gate it with permission.bash set to ask.
- how do i stop atlas writing a bad mysql alter statement
- Ask Atlas to read SHOW CREATE TABLE output first, so the ALTER matches the real schema and charset, then review the migration as a diff.
- should atlas run mysql migrations directly
- No. Have Atlas produce both the up and the down migration as a diff you review, never as a live statement.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Atlas with Mixtral 8x22B: The Largest Open MoE of Its Era in 2026
Mixtral 8x22B scaled the MoE idea in April 2024: 64,000 tokens at $2.00 / 1M input tokens and $6.00 / 1M output tokens. Atlas setup, self-hosting, and honest limits.
Atlas vs Cursor: terminal AI coding agents compared (2026)
A grounded 2026 comparison of Atlas and Cursor across workflow, change review, extensibility, and pricing for developers choosing an AI coding agent.
Atlas for Phoenix in 2026
Atlas is a terminal-native AI coding agent for Phoenix in 2026. It reads contexts, LiveView modules, and Ecto changesets, then runs mix test behind a prompt.
Atlas for React in 2026
Adopt Atlas, the terminal-native AI coding agent, for React development in 2026. Enhance your workflow with intelligent code search, refactoring, and testing for React components and hooks.
Atlas with Command A Plus: Run a Frontier Model Inside Your Own VPC (2026)
Command A Plus drives Atlas at $2.50 / $10 per Mtok on a 128K window, and Cohere can deploy it in your own VPC or on-prem so code never leaves your network.
Atlas for Actix Web in 2026
Atlas is a terminal-native AI coding agent for Actix Web in 2026. It reads extractors and app_data, then runs cargo test and cargo clippy behind a prompt.
Atlas with Azure OpenAI (gateway) in 2026: The GPT-5 Codex Line Under Enterprise IAM
Azure OpenAI (gateway) runs Atlas on the full GPT-5 lineup including gpt-5.3-codex, with up to 1.05M context and passthrough Azure pricing in your own region.
Atlas for Electron: Terminal-Native AI Coding for Main, Preload, and Renderer in 2026
Atlas is a terminal-native AI coding agent for Electron in 2026, where the main and renderer split, contextIsolation, and preload bridges are the security model.