vedb-mysql-mcp-server

An MCP server that exposes MySQL/SQL database access (via the vedb-mysql capability) to LLM agents through the Model Context Protocol, enabling agent-driven querying and retrieval from a MySQL database.

Evaluated Apr 04, 2026 (18d ago)

Homepage ↗ Infrastructure mcp database mysql sql agent-tools

⚙ 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

Direct database connectivity via an MCP server can be high-risk. Without explicit evidence of TLS enforcement, credential storage practices, or fine-grained tool restrictions/SQL whitelisting, assume moderate-to-high risk. Prefer least-privilege (read-only) DB accounts, network egress restrictions, and query/result redaction.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You can safely provide database credentials to a dedicated agent environment and you need SQL-backed retrieval via MCP with controlled tool access.

Avoid When

When you cannot restrict which tables/operations the agent can perform, or when database writes are not intended/allowed.

Use Cases

• Letting an AI agent run read queries against a MySQL database
• Building agent workflows that fetch customer/account data from MySQL
• Automating reporting tasks where the agent needs SQL results

Not For

• Untrusted agent environments where direct database access is unsafe
• Use cases requiring complex application-layer authorization beyond database credentials
• Public/anonymous usage without strong credential management

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: Database credentials (likely username/password or connection URI) configured for the MCP server

OAuth: No Scopes: No

Auth details were not provided in the prompt; MCP servers commonly rely on configured DB credentials rather than OAuth scopes.

Pricing

Free tier: No

Requires CC: No

No pricing information was provided; as a library/server, costs are typically infrastructure/hosting and database usage.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ SQL tool access can lead to unintended heavy queries (missing limits/where clauses).
⚠ Agents may generate non-read or destructive SQL if not constrained to SELECT/whitelisted operations.
⚠ Agents can expose sensitive data if query results are returned without redaction.

Alternatives

Use a database-specific API layer (REST/GraphQL) with explicit authorization instead of direct SQL tools Use a read-only database replica plus an API gateway in front of it Other MCP database servers or query tooling with stricter query whitelisting

Full Evaluation Report

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

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.