MySQL MCP Server

Created By
vitalyDVa year ago
MySQL MCP server for cursor
Overview

what is MySQL MCP Server?

MySQL MCP Server is an implementation of a Model Context Protocol (MCP) server designed for interacting with MySQL databases.

how to use MySQL MCP Server?

To use the MySQL MCP Server, clone the repository from GitHub, install the necessary dependencies, and configure the mcp.json file with your MySQL database credentials.

key features of MySQL MCP Server?

  • Execute SQL queries (only SELECT, SHOW, EXPLAIN, DESCRIBE)
  • Retrieve table structures and list all tables in the database
  • Access data from specified tables (up to 100 rows)

use cases of MySQL MCP Server?

  1. Simplifying database interactions for applications using MySQL.
  2. Providing a structured way to execute queries and retrieve data.
  3. Facilitating database management tasks through MCP tools.

FAQ from MySQL MCP Server?

  • What is the purpose of the MySQL MCP Server?

It serves as a protocol server to facilitate interactions with MySQL databases using the Model Context Protocol.

  • How do I configure the server?

You need to add your MySQL connection details in the mcp.json configuration file.

  • What types of queries can I execute?

You can execute SELECT, SHOW, EXPLAIN, and DESCRIBE queries.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vitalyDV
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 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.

a day ago