MySQL MCP Server

Created By
kerongona year ago
Overview

what is MySQL MCP Server?

MySQL MCP Server is a Model Context Protocol (MCP) server that provides MySQL database access functionality, allowing users to interact with MySQL databases seamlessly.

how to use MySQL MCP Server?

To use the MySQL MCP Server, clone the repository, install the dependencies, build the project, and set the necessary environment variables for MySQL connection. The server will start automatically when the MCP system initializes it.

key features of MySQL MCP Server?

  • List database tables and their schemas
  • Execute read-only SQL queries
  • Secure connection handling with connection pooling

use cases of MySQL MCP Server?

  1. Accessing and managing MySQL databases in a secure manner.
  2. Executing read-only queries for data analysis.
  3. Integrating with other applications that require MySQL database access.

FAQ from MySQL MCP Server?

  • What is the purpose of the MySQL MCP Server?

The MySQL MCP Server provides a secure and efficient way to access MySQL databases through the Model Context Protocol.

  • How do I install the MySQL MCP Server?

You can install it by cloning the repository, installing dependencies, and building the project as described in the installation section.

  • Is there a limit on the number of connections?

Yes, the default connection pool limit is set to 10, but it can be configured through the environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kerongon
Star
-
Language
-
License
-

Recommend Servers

View All
Gpt Scrambler

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

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago