mcp-server-mysql

An MCP (Model Context Protocol) server that connects to a MySQL database and exposes operations to list tables, read table contents, and execute SQL queries via a structured, agent-facing interface, using MySQL credentials supplied via environment variables.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Infrastructure mcp mysql database ai-agents backend java data-access

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Security guidance is included at a high level (least-privilege DB user, avoid root, monitor/log operations, consider query whitelisting). However, the README does not document MCP-layer authorization, SQL query allow/deny rules, or whether database connections use TLS. Secrets are expected via environment variables, but detailed handling (e.g., logging/obfuscation) is not verified from the provided content.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You have a dedicated low-privilege MySQL user and a local/controlled environment where an MCP client will interact with the database safely.

Avoid When

You cannot restrict database permissions or need robust protections against overly broad SQL execution (e.g., destructive queries) or data exfiltration attempts.

Use Cases

• Letting AI assistants explore a MySQL schema (list tables, inspect data)
• Building data analysis workflows where an agent needs controlled database access
• Prototyping MCP-based database tools in a Java environment

Not For

• Production environments without least-privilege DB users and query restrictions
• Use cases requiring strong authorization (per-user/per-role) at the MCP layer
• Untrusted agent workloads where SQL execution cannot be constrained

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: MySQL credentials via environment variables (MYSQL_USER/MYSQL_PASSWORD)

OAuth: No Scopes: No

Authentication is delegated to MySQL via a configured database user; the MCP layer authentication/authorization mechanisms are not described in the provided README.

Pricing

Free tier: No

Requires CC: No

No pricing information in provided content.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ SQL execution can be risky without query whitelisting and a constrained DB user
⚠ The README references an installation command for Python tooling (pip) that may not match this Java repo, which could confuse operators/agents setting up the server

Alternatives

Other MCP database servers for PostgreSQL/MySQL if available with stronger query whitelisting Database access through a purpose-built API (REST/GraphQL) with strict server-side authorization Direct read-only database connectors (e.g., read replicas) paired with an LLM tool that enforces query templates

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-mysql.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.