MySQL MCP Server

Created By
michael7736a year ago
MySQL MCP server project
Overview

what is MySQL MCP Server?

MySQL MCP Server is a Model Context Protocol (MCP) server that provides access to a MySQL database, allowing agents to execute SQL queries against it.

how to use MySQL MCP Server?

To use the MySQL MCP Server, clone the repository, install dependencies, configure the database connection settings, and then run the server. You can interact with it through commands in your application.

key features of MySQL MCP Server?

  • Execute SQL queries (SELECT, CREATE, INSERT, UPDATE, DELETE)
  • Returns query results in JSON format
  • Configurable database connection settings
  • Transaction logging with unique IDs

use cases of MySQL MCP Server?

  1. Executing SQL queries in applications using the MCP protocol.
  2. Managing MySQL databases programmatically.
  3. Integrating database operations into AI-driven applications.

FAQ from MySQL MCP Server?

  • What are the prerequisites for using MySQL MCP Server?

You need Node.js (v14 or higher) and a MySQL server.

  • How do I configure the MySQL MCP Server?

You need to set environment variables for the MySQL connection and configure the MCP settings in your application.

  • Can I use MySQL MCP Server for production?

Yes, but ensure to follow security best practices for database access.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
michael7736
Star
1
Language
JavaScript
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.

11 hours ago
Voyei

an hour ago