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
Voyei

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago