MySQL MCP Server

Created By
sajithammaa year ago
Overview

what is MySQL MCP Server?

MySQL MCP Server is a powerful database management tool built with FastMCP that provides an interactive interface for managing SQLite databases. It includes both a server component and a client interface for easy database operations.

how to use MySQL MCP Server?

To use MySQL MCP Server, clone the repository, set up a virtual environment, install dependencies, and run the server and client components to interact with the database using natural language commands.

key features of MySQL MCP Server?

  • List all tables in the database
  • Get detailed schema information for any table
  • Execute SQL queries with formatted results
  • Interactive client interface for database operations

use cases of MySQL MCP Server?

  1. Managing SQLite databases with ease
  2. Executing SQL queries through a user-friendly interface
  3. Retrieving detailed schema information for database tables

FAQ from MySQL MCP Server?

  • What databases does MySQL MCP Server support?

MySQL MCP Server is designed for managing SQLite databases.

  • Is MySQL MCP Server free to use?

Yes! MySQL MCP Server is open-source and free to use.

  • What are the prerequisites for running MySQL MCP Server?

You need Python 3.8 or higher and pip installed to set up the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sajithamma
Star
0
Language
Python
License
-
Category
databases

Recommend Servers

View All
Payai X402 Tools

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.

a day ago