MySQL MCP Server

Created By
designcomputera year ago
A Model Context Protocol (MCP) server that enables secure interaction with MySQL databases
Overview

what is MySQL MCP Server?

MySQL MCP Server is a Model Context Protocol (MCP) server designed to enable secure interactions with MySQL databases. It provides a structured interface for AI assistants to interact with databases safely, allowing for database exploration and analysis.

how to use MySQL MCP Server?

To use MySQL MCP Server, install it via pip and configure the required environment variables for your MySQL instance. You can run it standalone or integrate it with applications like Claude Desktop.

key features of MySQL MCP Server?

  • Lists available MySQL tables as resources
  • Reads table contents securely
  • Executes SQL queries with error handling
  • Configurable access through environment variables
  • Logs database operations comprehensively

use cases of MySQL MCP Server?

  1. Creating secure database interfaces for AI applications
  2. Enabling structured exploration of MySQL databases
  3. Logging and monitoring database queries for audit purposes

FAQ from MySQL MCP Server?

  • How do I install MySQL MCP Server?

Use the command pip install mysql-mcp-server to install it.

  • Can I run it as a standalone server?

Yes! You can run it independently by following the provided usage instructions.

  • Are there security practices I should follow?

Yes! It's advised to create a dedicated MySQL user with minimal permissions and enable logging for all database operations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
designcomputer
Star
571
Language
Python
License
MIT license

Recommend Servers

View All
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

a day ago