mcp_mysql_server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is mcp_mysql_server?

The mcp_mysql_server is a powerful MySQL server tool that not only facilitates standard CRUD operations but also provides advanced database anomaly analysis capabilities, making it easy for developers to extend with custom tools.

how to use mcp_mysql_server?

To use mcp_mysql_server, install the package via pip, configure your environment variables in a .env file, and run the service in either SSE or STDIO mode.

key features of mcp_mysql_server?

  • Supports both STDIO and SSE modes for flexible operation.
  • Allows multiple SQL executions separated by semicolons.
  • Provides querying capabilities for database table names and fields based on comments.
  • Includes SQL execution plan analysis and database health status analysis.
  • Offers permission control with three roles: readonly, writer, and admin.
  • Supports custom tool extensions for enhanced functionality.

use cases of mcp_mysql_server?

  1. Executing complex SQL queries and analyzing their performance.
  2. Monitoring database health and identifying potential issues.
  3. Extending the server with custom tools for specific database operations.

FAQ from mcp_mysql_server?

  • Can mcp_mysql_server handle large databases?

Yes! It is designed to efficiently manage and analyze large databases.

  • Is there a user guide available?

Yes! Comprehensive documentation is provided in the README files for both English and Chinese users.

  • What programming language is mcp_mysql_server written in?

It is written in Python, making it easy to integrate with other Python applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
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