@f4ww4z/mcp-mysql-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is @f4ww4z/mcp-mysql-server?

@f4ww4z/mcp-mysql-server is a Model Context Protocol server that facilitates MySQL database operations, allowing AI models to interact with MySQL databases through a standardized interface.

how to use @f4ww4z/mcp-mysql-server?

To use the server, you can install it via Smithery or manually using the provided commands. Configuration requires setting specific environment variables in your MCP settings.

key features of @f4ww4z/mcp-mysql-server?

  • Secure connection handling with automatic cleanup
  • Prepared statement support for executing queries
  • Comprehensive error handling and validation
  • TypeScript support for developers
  • Automatic connection management

use cases of @f4ww4z/mcp-mysql-server?

  1. Connecting AI models to MySQL databases for data retrieval and manipulation.
  2. Executing complex SQL queries through a standardized interface.
  3. Integrating database operations into AI-driven applications.

FAQ from @f4ww4z/mcp-mysql-server?

  • Is this server secure?

Yes! It uses prepared statements to prevent SQL injection and supports secure password handling.

  • Can I contribute to this project?

Absolutely! Contributions are welcome, and you can submit a Pull Request on GitHub.

  • What programming languages does it support?

The server is designed with TypeScript support, making it suitable for JavaScript developers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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