MCP.so
Sign In

Servidor de Consultas MySQL MCP Server

@fersoftware

Basic information

Category

Databases

Transports

stdio

Author

fersoftware

About Servidor de Consultas MySQL MCP Server

Servidor de Consultas MySQL baseado em MCP com suporte a SSE e segurança avançada

Servidor de Consultas MySQL MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mysql-mcp-server-sse-fersoftware": {
      "command": "python",
      "args": [
        "src/server.py"
      ]
    }
  }
}

Servidor de Consultas MySQL MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Servidor de Consultas MySQL?

Servidor de Consultas MySQL is an MCP (Model-Context-Protocol) server built with FastMCP that enables MySQL database operations over SSE (Server-Sent Events). It provides a query interface, automatic transaction management, and a built-in SQL security mechanism with risk level control and sensitive data protection. It is intended for developers who need a secure, real‑time MySQL query server that integrates with AI assistants or other MCP‑compatible clients.

How to use Servidor de Consultas MySQL?

Install Python 3.6+, clone the repository, install dependencies (pip install -r requirements.txt), and configure the .env file with MySQL credentials and security settings. Start the server with python src/server.py — it listens by default at http://127.0.0.1:3000/sse. Use the provided test client (test_client.py) or any MCP client to connect and execute tools such as mysql_query, mysql_show_tables, or mysql_paginate_results.

Key features of Servidor de Consultas MySQL

  • Real‑time SSE streaming for database queries
  • SQL security with four risk levels (LOW to CRITICAL)
  • Automatic transaction commit/rollback for modifications
  • Sensitive information detection and masking
  • Metadata queries (tables, columns, indexes, foreign keys)
  • Environment‑aware: different behaviour in development vs. production

Use cases of Servidor de Consultas MySQL

  • Allow AI assistants to run safe SELECT queries against a production MySQL database
  • Enable interactive database exploration through MCP‑compatible chat interfaces
  • Provide a secured query endpoint for internal tools that need SQL access
  • Automate schema inspections (table structure, indexes, foreign keys) via metadata tools
  • Run parameterised INSERT/UPDATE/DELETE operations with enforced WHERE clauses

Frequently asked questions

1

Why does my DELETE operation fail?

DELETE without a WHERE clause is classified as CRITICAL risk. Add a WHERE condition (even `WHERE 1=1`) to lower the risk level, and ensure `CRITICAL` is included in `ALLOWED_RISK_LEVELS`.

2

Environment variables are not working?

Make sure `load_dotenv()` is called before any other imports in `server.py`. Restart the server and check the log line “Configurações de nível de risco lidas das variáveis de ambiente”.

3

My query was rejected by the security mechanism?

Check that the operation’s risk level is allowed in `ALLOWED_RISK_LEVELS`. For UPDATE/DELETE without WHERE, add a condition to reduce the risk.

4

Can I see sensitive information (passwords, keys) in query results?

In development mode, set `ALLOW_SENSITIVE_INFO=true`. In production, sensitive fields are always masked; this is by design for security.

5

What are the system requirements?

Python 3.6+, a running MySQL server, and the Python packages `mysql-connector-python`, `python-dotenv`, and

Comments

More Databases MCP servers