mcp_mysql_server

Created By
wenb1n-deva year ago
Support for SSE, STDIO in MySQL MCP server, includes CRUD, database anomaly analysis capabilities .支持SSE,STDIO;不仅止于mysql的增删改查功能; 还包含了数据库异常分析能力;且便于开发者们进行个性化的工具扩展
Overview

What is mcp_mysql_server?

The mcp_mysql_server is a MySQL MCP server that supports both SSE and STDIO modes, allowing for efficient database operations and management.

How to use mcp_mysql_server?

To use the mcp_mysql_server, you can operate in either STDIO mode or SSE mode by running the respective Python scripts and configuring your MCP client tools with the provided JSON structure.

Key features of mcp_mysql_server?

  • Support for STDIO and SSE modes for flexible database interaction.
  • Ability to execute multiple SQL commands separated by semicolons.
  • Query database table names and fields based on comments.
  • SQL Execution Plan Analysis for performance insights.
  • Chinese field to pinyin conversion for better data handling.

Use cases of mcp_mysql_server?

  1. Managing MySQL databases in a development environment.
  2. Executing complex SQL queries efficiently.
  3. Analyzing SQL execution plans for optimization.
  4. Converting Chinese field names to pinyin for easier integration.

FAQ from mcp_mysql_server?

  • What modes does mcp_mysql_server support?

It supports both STDIO and SSE modes for different operational needs.

  • How do I configure my database connection?

You can modify the .env file to set your MySQL connection parameters.

  • Can I execute multiple SQL commands at once?

Yes, you can execute multiple SQL commands separated by semicolons.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wenb1n-dev
Star
151
Language
Python
License
MIT 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