Servidor de Consultas MySQL

Created By
fersoftwarea year ago
Servidor de Consultas MySQL baseado em MCP com suporte a SSE e segurança avançada
Overview

What is MySQL MCP Server SSE?

MySQL MCP Server SSE is a MySQL query server based on the MCP (Model-Controller-Provider) framework that provides functionalities for database operations through Server-Sent Events (SSE).

How to use MySQL MCP Server SSE?

To use the server, clone the project from GitHub, install the required dependencies, configure the environment variables, and start the server using the provided command.

Key features of MySQL MCP Server SSE?

  • Built with the FastMCP framework
  • Real-time data transmission via SSE
  • Comprehensive logging system
  • Automatic transaction management (commit/rollback)
  • Advanced SQL security mechanisms including risk level control and SQL injection protection

Use cases of MySQL MCP Server SSE?

  1. Real-time data updates for web applications
  2. Secure database operations with automatic logging
  3. Managing complex SQL queries with enhanced security features

FAQ from MySQL MCP Server SSE?

  • Can I use this server for any MySQL database?

Yes! It is designed to work with any MySQL database.

  • Is there a way to customize the security settings?

Yes! You can configure various security parameters in the environment variables.

  • How do I handle errors during database operations?

The server includes a comprehensive error handling mechanism that logs errors and reverts transactions automatically.

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

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago