Mysql_mcp_server_pro

Created By
wenb1n-dev(xwb602625136)a year ago
支持SSE,STDIO的mysql mcp server 。Support for SSE, STDIO in MySQL MCP server.
Overview

what is Mysql_mcp_server_pro?

Mysql_mcp_server_pro is a powerful tool designed for managing MySQL databases, providing features for SQL execution, database querying, and analysis.

how to use Mysql_mcp_server_pro?

To use Mysql_mcp_server_pro, you can operate in either STDIO mode or SSE mode by running the appropriate Python scripts and configuring your database connection settings in the .env file.

key features of Mysql_mcp_server_pro?

  • Support for STDIO and SSE modes for flexible operation
  • Multiple SQL execution capabilities
  • Ability to query database table names and fields based on comments
  • SQL Execution Plan Analysis
  • Chinese field to pinyin conversion

use cases of Mysql_mcp_server_pro?

  1. Executing complex SQL queries efficiently.
  2. Analyzing SQL execution plans for performance optimization.
  3. Managing and querying MySQL databases with ease.

FAQ from Mysql_mcp_server_pro?

  • What modes does Mysql_mcp_server_pro support?

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

  • How do I configure my database connection?

You can modify the .env file to set your MySQL host, port, user, password, and database name.

  • Can I execute multiple SQL statements at once?

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

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wenb1n-dev(xwb602625136)
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)

2 days ago