Mysql_mcp_server_ddz

Created By
fanzhenddz5 months ago
Mysql_mcp_server_ddz
Overview

what is Mysql_mcp_server_ddz?

Mysql_mcp_server_ddz is a MySQL server based on the Model Context Protocol (MCP) using the FastMCP framework, designed to allow AI applications to securely access and manipulate MySQL databases.

how to use Mysql_mcp_server_ddz?

To use Mysql_mcp_server_ddz, configure the database connection information through environment variables and run the server command to start the MCP server for MySQL operations.

key features of Mysql_mcp_server_ddz?

  • Secure access to MySQL databases for AI applications.
  • Encapsulates MySQL as an MCP server for standard protocol calls.
  • Supports various database configurations through environment variables.

use cases of Mysql_mcp_server_ddz?

  1. Enabling AI models to perform database operations like listing tables and executing SQL queries.
  2. Integrating with IDEs that support MCP for enhanced database management.
  3. Providing a tool layer for large models to interact with MySQL databases.

FAQ from Mysql_mcp_server_ddz?

  • What is the purpose of Mysql_mcp_server_ddz?

It serves as a tool layer for AI applications to interact with MySQL databases securely.

  • How do I configure the database connection?

You need to set environment variables for MYSQL_HOST, MYSQL_PORT, MYSQL_USER, MYSQL_PASSWORD, and MYSQL_DATABASE.

  • Is this a traditional web API service?

No, it is designed specifically for AI applications and not as a conventional web API.

Server Config

{
  "mcpServers": {
    "mysql": {
      "command": "uvx",
      "args": [
        "mysql-mcp-server-ddz"
      ],
      "env": {
        "MYSQL_HOST": "localhost",
        "MYSQL_PORT": "3306",
        "MYSQL_USER": "your_username",
        "MYSQL_PASSWORD": "your_password",
        "MYSQL_DATABASE": "your_database"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
4 months ago
Author Name
fanzhenddz
Star
-
Language
-
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)

13 minutes ago