mysqldb-mcp-server MCP server

Created By
burakdirina year ago
An MCP server implementation that enables Claude AI to interact with MySQL databases.
Overview

what is mysqldb-mcp-server?

mysqldb-mcp-server is an MCP server implementation that allows Claude AI to interact seamlessly with MySQL databases, enabling efficient database management and query execution.

how to use mysqldb-mcp-server?

To use mysqldb-mcp-server, install the package via pip or uv, configure the necessary environment variables, and run the server to connect to your MySQL database and execute queries.

key features of mysqldb-mcp-server?

  • Connects to MySQL databases easily.
  • Executes SQL queries and returns results in JSON format.
  • Supports multiple queries in a single request.
  • Configurable environment settings for database connection.

use cases of mysqldb-mcp-server?

  1. Automating database interactions for AI applications.
  2. Executing complex SQL queries from AI-driven tools.
  3. Integrating MySQL database functionalities into various applications.

FAQ from mysqldb-mcp-server?

  • What programming language is mysqldb-mcp-server written in?

mysqldb-mcp-server is written in Python.

  • Is there a way to run multiple queries at once?

Yes, you can send multiple queries separated by semicolons.

  • How do I configure the database connection?

You can configure the connection using environment variables such as MYSQL_HOST, MYSQL_USER, MYSQL_PASSWORD, etc.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
burakdirin
Star
0
Language
Python
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)

a day ago