Skip to main content
Glama
Secure MySQL MCP Server

Secure MySQL MCP Server

by Kavi-200312

๐Ÿ›ก๏ธ Secure MySQL MCP Server

The enterprise-grade, AST-guarded Model Context Protocol (MCP) server for MySQL.
Works seamlessly with Antigravity, Claude Code, Cursor, Devin, Codex, and any MCP client.

Node.js TypeScript MCP License: MIT Tests


๐ŸŒŸ Why This MCP Server?

Standard off-the-shelf MySQL MCP servers blindly execute any raw SQL string passed by the AI agent โ€” allowing unintended table drops, mass updates without WHERE clauses, or data corruption.

Secure MySQL MCP solves this by putting a protective AST parser, configurable permission gate, and automated SSH tunnel directly between the AI and your database.

AI Coding Agent (Antigravity / Claude / Cursor / Devin)
    โ”‚
    โ–ผ (stdio JSON-RPC)
Secure MySQL MCP Server
    โ”œโ”€โ”€ ๐Ÿ” AST SQL Parser (node-sql-parser)
    โ”‚     โ”œโ”€โ”€ Blocks multi-statements, INTO OUTFILE, session variables
    โ”‚     โ””โ”€โ”€ Enforces WHERE clauses on UPDATE and DELETE
    โ”œโ”€โ”€ ๐Ÿšฆ Configurable Policy Engine (Strict / Prompt / Autonomous)
    โ”‚     โ”œโ”€โ”€ Safe by default (Blocks DROP, TRUNCATE, DELETE, DDL)
    โ”‚     โ””โ”€โ”€ Granular opt-in auto-approval flags
    โ”œโ”€โ”€ ๐Ÿ” Dual Pool Isolation
    โ”‚     โ”œโ”€โ”€ ai_agent_reader (SELECT, SHOW VIEW only)
    โ”‚     โ””โ”€โ”€ ai_agent_writer (INSERT, UPDATE, DELETE in atomic transactions)
    โ””โ”€โ”€ ๐Ÿ“œ Pino Structured Audit Logger (Auto-redacts credentials & keys)
    โ”‚
    โ–ผ (127.0.0.1:13306 or Direct SSL)
SSH Tunnel / Cloud Database (DigitalOcean, AWS RDS, GCP Cloud SQL, Self-hosted VPS)

Related MCP server: MySQL ReadOnly MCP Server

๐Ÿš€ Key Features

  • ๐Ÿ›ก๏ธ Safe by Default: Destructive statements (DELETE, DROP, TRUNCATE, ALTER, CREATE) are blocked out of the box.

  • โšก Fully Customizable Autonomy: Want the AI to write without asking permission? Switch POLICY_MODE=autonomous or toggle granular flags (POLICY_AUTO_APPROVE_INSERT=true, POLICY_ALLOW_DELETE=true).

  • ๐Ÿ›‘ No Full-Table Accidents: AST parser rejects UPDATE or DELETE without a WHERE clause.

  • ๐Ÿ”’ Anti-Injection Guardrails: Permanently eliminates INTO OUTFILE, LOAD DATA INFILE, user session variable tampering (@var), and chained multi-statements.

  • ๐Ÿ”‘ Built-in SSH Tunnel: Automatically provisions and tears down a local SSH tunnel (ssh -N -L) or connects directly via TLS/SSL.

  • ๐Ÿ‘ฅ Least-Privilege Architecture: Dual connection pools route reads to a read-only DB user and writes to a write-restricted DB user.

  • ๐Ÿ“Š 10 Powerful Tools: 7 inspection & query tools, plus 3 write tools (propose_write, write_query, execute_approved_write).


๐Ÿ“ฆ Quick Installation

Option 1: Run with npx via GitHub (Zero manual build needed)

Thanks to the automated prepare build lifecycle, you can run directly from GitHub without cloning:

npx github:Kavi-200312/mysql-mcp

(Once published to the public npm registry, npx mysql-mcp will also be available).

Option 2: Clone and Build Locally

git clone https://github.com/Kavi-200312/mysql-mcp.git
cd mysql-mcp
npm install
npm test
npm run build

๐Ÿค– Client Setup Guides

1. Antigravity Setup

Add to ~/.gemini/config/mcp_config.json:

{
  "mcpServers": {
    "mysql": {
      "command": "node",
      "args": ["/path/to/mysql-mcp/dist/index.js"]
    }
  }
}

2. Claude Desktop / Claude Code Setup

Add to claude_desktop_config.json (Mac: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "mysql": {
      "command": "node",
      "args": ["/path/to/mysql-mcp/dist/index.js"],
      "env": {
        "DB_HOST": "127.0.0.1",
        "DB_PORT": "3306",
        "DB_NAME": "my_database",
        "DB_READER_USER": "ai_agent_reader",
        "DB_READER_PASSWORD": "your_password",
        "DB_WRITER_USER": "ai_agent_writer",
        "DB_WRITER_PASSWORD": "your_password"
      }
    }
  }
}

3. Cursor Setup

In Cursor, go to Settings > Features > MCP, click Add New MCP Server:

  • Name: mysql

  • Type: command

  • Command: node /path/to/mysql-mcp/dist/index.js

Or add to .cursor/mcp.json in your workspace:

{
  "mcpServers": {
    "mysql": {
      "command": "node",
      "args": ["/path/to/mysql-mcp/dist/index.js"]
    }
  }
}

4. Devin Setup

Add to your Devin machine configuration or devin.json:

{
  "mcpServers": {
    "mysql": {
      "command": "node",
      "args": ["/path/to/mysql-mcp/dist/index.js"]
    }
  }
}

โš™๏ธ Configuration Reference (.env)

Copy .env.example to .env in the project root:

cp .env.example .env

Variable

Default

Description

Database Connection

DB_HOST

127.0.0.1

MySQL server host (or localhost if using SSH tunnel)

DB_PORT

3306

MySQL port (e.g. 25060 for DigitalOcean, 3306 standard)

DB_NAME

""

Target development database name

DB_SSL

auto

true, false, or auto (auto-enables SSL for port 25060 or cloud hosts)

DB_READER_USER

ai_agent_reader

Least-privilege user for read tools

DB_READER_PASSWORD

""

Password for reader user

DB_WRITER_USER

ai_agent_writer

Dedicated user for write tools

DB_WRITER_PASSWORD

""

Password for writer user

SSH Tunneling

SSH_ENABLED

false

Set to true to tunnel connections through a remote VPS/Droplet

SSH_HOST

""

Remote SSH IP or hostname

SSH_PORT

22

Remote SSH port

SSH_USER

""

Remote SSH username

SSH_KEY_PATH

""

Path to private key (e.g. ~/.ssh/id_ed25519)

SSH_LOCAL_PORT

13306

Local forwarding port

Security & Permission Policies

POLICY_MODE

strict

strict (Prompt everything), prompt (Permissive with prompts), or autonomous (AI executes allowed ops with zero prompts)

POLICY_ALLOW_DELETE

false

Enable DELETE statements (still requires WHERE)

POLICY_ALLOW_DDL

false

Enable CREATE, ALTER, DROP, TRUNCATE

POLICY_REQUIRE_WHERE

true

Enforce mandatory WHERE clause on UPDATE & DELETE

POLICY_AUTO_APPROVE_INSERT

false

Auto-execute INSERT without asking user confirmation

POLICY_AUTO_APPROVE_UPDATE

false

Auto-execute UPDATE without asking user confirmation

POLICY_AUTO_APPROVE_DELETE

false

Auto-execute DELETE without asking user confirmation

POLICY_AUTO_APPROVE_DDL

false

Auto-execute DDL (CREATE, ALTER) without asking user confirmation

Limits & Auditing

DB_MAX_ROWS

500

Max rows returned per query to prevent memory bloat

DB_QUERY_TIMEOUT_MS

15000

Query execution timeout (15s)

DB_MAX_PAYLOAD_BYTES

524288

Payload size cap (512 KB)

APPROVAL_EXPIRY_SECONDS

300

Lifetime of write approval tokens (5 min)

LOG_LEVEL

info

Structured logging level (info, debug, warn)


๐Ÿ› ๏ธ Available MCP Tools

Read & Inspection Tools

Tool

Description

list_databases

Lists all accessible databases on the host.

list_tables

Lists all tables and views in the configured database.

describe_table

Inspects table schema, columns, data types, keys, and nullability.

read_query

Executes AST-validated SELECT query (max 500 rows, 15s timeout).

explain_query

Inspects MySQL execution plan (EXPLAIN) for performance tuning.

get_table_relationships

Inspects foreign key constraints and referenced tables.

get_database_overview

Generates summary of table sizes, engine, and row estimates.

Write & Execution Tools

Tool

Description

propose_write

Previews changes, estimates affected rows, and generates an approval token.

write_query

Smart execution tool: runs immediately if permitted by policy, or returns a prompt token if approval is required.

execute_approved_write

Atomically executes a previously authorized token with explicit confirmation.


๐Ÿ›ก๏ธ Database Provisioning Script

Run this on your remote MySQL server to create isolated accounts:

-- 1. Create read-only user (SELECT and SHOW VIEW only)
CREATE USER IF NOT EXISTS 'ai_agent_reader'@'%' IDENTIFIED BY 'STRONG_READER_PASSWORD';
GRANT SELECT, SHOW VIEW ON `my_dev_db`.* TO 'ai_agent_reader'@'%';

-- 2. Create writer user (Restricted to DML only)
CREATE USER IF NOT EXISTS 'ai_agent_writer'@'%' IDENTIFIED BY 'STRONG_WRITER_PASSWORD';
GRANT SELECT, INSERT, UPDATE, DELETE ON `my_dev_db`.* TO 'ai_agent_writer'@'%';

FLUSH PRIVILEGES;

๐Ÿงช Testing & Security Verification

The test suite runs 40 automated security tests using Vitest:

npm test

Verifies:

  • SELECT, SHOW, DESCRIBE, EXPLAIN allowed

  • DELETE, DROP, TRUNCATE, ALTER, CREATE blocked by default

  • Configurable policies allow DELETE and DDL only when explicitly enabled

  • UPDATE and DELETE without WHERE rejected

  • Session variable injections (@var) and comment-obfuscated INTO OUTFILE permanently blocked

  • Cross-database subqueries, joins, CTEs, and UNIONs strictly prevented

  • Locking reads (FOR UPDATE / LOCK IN SHARE MODE) prohibited on read path

  • Approval tokens reject tampered queries, altered params, and re-executions

  • Row caps, server-side LIMIT injection, and query cancellation (KILL QUERY) enforced

  • Sensitive credentials and tokens automatically redacted from audit logs


IMPORTANT

Defense-in-Depth Architecture: The propose_write + execute_approved_write workflow and the userConfirmed: true flag are designed to prevent accidental model hallucinations and catastrophic runaway updates. For mission-critical environments where you defend against adversarial prompt injections, always pair this MCP server with:

  1. Dedicated least-privilege MySQL accounts (ai_agent_reader / ai_agent_writer) created via scripts/create-db-users.sql.

  2. Native MCP client permission prompts (e.g. Antigravity / Claude Code UI tool confirmation).


๐Ÿ“„ License

MIT ยฉ StinSoft & Open Source Contributors

Available Tools

10 tools
describe_tableB

Get column details, data types, keys, and nullability for a table.

Inputs: table (required), database.

execute_approved_writeA

Execute a previously proposed and user-approved write operation using its short-lived approval token. Strictly requires userConfirmed: true.

Inputs: approvalToken (required), userConfirmed (required).

explain_queryC

Get MySQL query execution plan (EXPLAIN) for a SELECT statement.

Inputs: sql (required), params, database.

get_database_overviewB

Get high-level summary of tables, estimated row counts, storage size, and collation.

Inputs: database.

get_table_relationshipsC

Inspect foreign key relationships and table constraints.

Inputs: table, database.

list_databasesA

List accessible databases on the remote MySQL instance.

Inputs: no named parameters.

list_tablesA

List all tables and views in the development database.

Inputs: database.

propose_writeA

Propose an INSERT, UPDATE, DELETE, or DDL statement. Validates SQL AST, shows preview diff of affected rows, and generates an approval token. NEVER executes immediately.

Inputs: sql (required), params, database, confirmBulk.

read_queryA

Execute a read-only SELECT query against the development database. AST-enforced, single statement only. Max 500 rows.

Inputs: sql (required), limit, params, database.

write_queryA

Execute a write statement (INSERT, UPDATE, DELETE, or DDL). If the operation is configured for auto-approval in policy, it executes immediately in an atomic transaction; otherwise, it returns a pending approval request.

Inputs: sql (required), params, database, userConfirmed.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Discovery tools (list_databases, list_tables, describe_table, get_database_overview, get_table_relationships) each target a distinct metadata scope, and read_query vs explain_query are clearly separated. The only real friction is the write trio: propose_write and write_query overlap in that write_query may just return a pending approval instead of executing, which could make an agent unsure which to call first, though the descriptions do resolve it.

    Naming Consistency5/5

    All ten tools use snake_case verb_noun form (list_databases, describe_table, read_query, propose_write, execute_approved_write) with no camelCase or style mixing. The pattern is predictable enough that an agent can infer naming for unseen operations.

    Tool Count5/5

    Ten tools is well within the ideal band and each earns its place: introspection, read path, explain, relationships, overview, and a three-stage guarded write lifecycle. Nothing looks redundant padding or conspicuously absent.

    Completeness4/5

    The surface covers discovery, read-only querying, plan inspection, and a full propose/approve/execute write lifecycle with DDL support, which is strong for a database server. Minor gaps remain: no index listing, no cancellation/rollback or transaction-status tool, and no way to inspect or list pending approval requests, which an agent would likely want.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language database operations on MySQL databases with AI integration, supporting CRUD operations, schema inspection, and audit logging with built-in security features including SQL injection protection and permission controls.
      798 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to safely query MySQL databases with read-only access, featuring SQL injection protection, connection pooling, and automatic query limits for secure database exploration.
      4
      124 npm
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to securely interact with MySQL databases through tools for query execution, schema inspection, and transaction management. It features built-in safety controls like row limits and query validation to ensure safe and standardized database access.
      798 npm
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to inspect and query a MySQL database through safe, structured tools, including schema discovery and read-only queries.
      9
      104 npm
      MIT