Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect MySQL to Claude Code

Let Claude run scoped reads and controlled writes against your MySQL data. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect MySQL to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect MySQL, you add a MySQL MCP server: a small hosted service that exposes MySQL's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own MySQL account. No API keys pasted into config files.

claude mcp add --transport http mysql https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in MySQL once connected?

Full read-write MySQL access lets Claude run parameterized queries, insert and update rows, adjust schema, and stage migrations against a database you control. The data exploration, cleanup, and routine changes that used to mean hand-writing SQL in a client happen in conversation, with every write reviewed before it runs.

  • Insert or update rows from data you describe, using parameterized statements
  • Run a SELECT to explore a table, then propose the change it implies
  • Apply a schema migration such as adding a column or index after you approve it
  • Bulk-correct or normalize values across a table within a single transaction
  • Generate and run a backfill query, showing affected row counts first
  • Export the result of a query for a report or downstream task

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same MySQL access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the MySQL API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when MySQL changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build MySQL connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same MySQL connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own MySQL account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on MySQL's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to MySQL?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the MySQL account it signs in with. Revoking access is one click in MySQL.

More on the MySQL connector

MySQL connector for claude.aiAirtable + Claude CodePostgreSQL + Claude CodeMongoDB + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us