mcp-mysql-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is mcp-mysql-server?

The mcp-mysql-server is a MySQL database operation server based on the Model Context Protocol, enabling AI models to interact with MySQL databases through standardized interfaces.

how to use mcp-mysql-server?

To use the mcp-mysql-server, install it via npm with the command npx @malove86/mcp-mysql-server, and configure it for either local or remote deployment by setting the necessary environment variables.

key features of mcp-mysql-server?

  • Multi-user concurrency support
  • Efficient connection pool management
  • Request-level isolation for tracking and debugging
  • Detailed logging of request execution and resource usage
  • Improved error handling and performance optimization

use cases of mcp-mysql-server?

  1. Enabling AI applications to perform database operations seamlessly.
  2. Supporting multiple users accessing the database concurrently.
  3. Providing a secure environment for database interactions without exposing sensitive credentials.

FAQ from mcp-mysql-server?

  • Can I run mcp-mysql-server locally?

Yes! You can run it in local mode by configuring the MCP settings.

  • Is there support for concurrent connections?

Yes! The server supports up to 50 concurrent connections.

  • How does mcp-mysql-server handle security?

It uses prepared statements to prevent SQL injection and manages sensitive credentials securely.

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
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