mysql-mcp-server

Created By
Mineru98a year ago
A server application designed on top of MCP to interact with Cursor and MySQL.
Overview

What is MCPMySQLBoilerPlate?

MCPMySQLBoilerPlate is a server application designed to interact with MySQL using the Model Control Protocol (MCP). It provides various tools for database operations, ensuring scalability and maintainability.

How to use MCPMySQLBoilerPlate?

To use MCPMySQLBoilerPlate, you can run it using Docker, Docker Compose, or directly with Python. Adjust the database connection settings as needed.

Key features of MCPMySQLBoilerPlate?

  • Interaction with MySQL databases through MCP.
  • Support for various database operations via executors.
  • Easy to extend with new tools and functionalities.

Use cases of MCPMySQLBoilerPlate?

  1. Automating database management tasks.
  2. Integrating AI models with MySQL for data processing.
  3. Developing custom database tools for specific needs.

FAQ from MCPMySQLBoilerPlate?

  • Can I run this application without Docker?

Yes, you can run it directly using Python after installing the required dependencies.

  • Is there a way to add new tools?

Yes, you can add new executors in the executors directory and register them in the init.py file.

  • What programming language is used?

The application is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Mineru98
Star
17
Language
Python
License
MIT 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.

8 hours ago