MCP Server MySQL Database Explorer

Created By
eth-ts-xa year ago
Overview

What is MCP Server MySQL Database Explorer?

MCP Server MySQL Database Explorer is a tool that connects to your MySQL database, allowing seamless access to database schemas, tables, and query capabilities through LLMs.

How to use MCP Server MySQL Database Explorer?

To use the MCP Server, install the required dependencies, configure your environment variables with your database credentials, and run the server using the provided commands. You can then interact with your database through an MCP Client.

Key features of MCP Server MySQL Database Explorer?

  • Connects to your MySQL database.
  • Exposes table schemas, create statements, and sample data as resources.
  • Runs read-only SQL queries with secure validation.

Use cases of MCP Server MySQL Database Explorer?

  1. Accessing and managing MySQL database schemas.
  2. Running SQL queries through LLMs for data analysis.
  3. Integrating with MCP Clients for enhanced database interaction.

FAQ from MCP Server MySQL Database Explorer?

  • What databases does MCP Server support?

MCP Server is designed to work with MySQL databases.

  • Is there a graphical interface for this tool?

No, it primarily operates through command-line and MCP Clients.

  • Can I run write operations with this server?

No, the server is designed for read-only SQL queries.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
eth-ts-x
Star
0
Language
Python
License
-

Recommend Servers

View All
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.

21 hours ago