Mcp_server_mysql

Created By
benborlaa year ago
Overview

What is MCP Server for MySQL?

MCP Server for MySQL is a Model Context Protocol server built on Node.js that provides access to MySQL databases, enabling large language models (LLMs) to inspect database schemas and execute SQL queries.

How to use MCP Server for MySQL?

To use the MCP Server, install it via npm or through Smithery, configure your MySQL connection details, and run the server. You can execute SQL queries through the server once it's set up.

Key features of MCP Server for MySQL?

  • Execute SQL queries against MySQL databases.
  • Supports read and write operations with proper permissions.
  • Provides comprehensive database information including table schemas and statistics.
  • Security features like SQL injection prevention and query whitelisting.
  • Performance optimizations such as connection pooling and query caching.

Use cases of MCP Server for MySQL?

  1. Integrating LLMs with MySQL databases for dynamic data retrieval.
  2. Automating database management tasks through SQL queries.
  3. Enhancing applications with real-time data access and manipulation capabilities.

FAQ from MCP Server for MySQL?

  • Can I use MCP Server with any version of MySQL?
    Yes, it supports MySQL 5.7 and higher, with MySQL 8.0+ recommended.

  • Is there a way to enable write operations?
    Yes, you can enable INSERT, UPDATE, and DELETE operations through configuration settings.

  • How do I troubleshoot connection issues?
    Ensure your MySQL server is running, check your credentials, and verify SSL settings if applicable.

Server Config

{
  "mcpServers": {
    "mcp_server_mysql": {
      "command": "npx",
      "args": [
        "-y",
        "@benborla29/mcp-server-mysql"
      ],
      "env": {
        "MYSQL_HOST": "127.0.0.1",
        "MYSQL_PORT": "3306",
        "MYSQL_USER": "root",
        "MYSQL_PASS": "password",
        "MYSQL_DB": "your_db",
        "ALLOW_INSERT_OPERATION": "true",
        "ALLOW_UPDATE_OPERATION": "true",
        "ALLOW_DELETE_OPERATION": "true"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
benborla
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago