mysql_mcpserver_stdio

Created By
lanjunfeia year ago
批量生成基于mysql数据库的mcpserver,支持stdio传输。Generate MCP servers in batch based on MySQL database, supporting stdio transmission.
Overview

what is mysql_mcpserver_stdio?

mysql_mcpserver_stdio is a tool that allows users to generate MCP servers in batch based on a MySQL database, supporting stdio transmission.

how to use mysql_mcpserver_stdio?

To use mysql_mcpserver_stdio, set up a virtual environment and install the required packages from requirements.txt. Run the application using 'python app.py' and access the server file generation page at 127.0.0.1:5000. Input the MySQL database parameters including IP, port, username, password, and database name. The generated MCP server files will have a .py extension.

key features of mysql_mcpserver_stdio?

  • Batch generation of MCP server files from MySQL database.
  • Supports stdio transmission.
  • Built-in function to check database connectivity.
  • Customizable tool function definitions with SQL queries.

use cases of mysql_mcpserver_stdio?

  1. Quickly generating multiple MCP server files for different database configurations.
  2. Automating the setup of server environments for testing or production.
  3. Simplifying the process of managing database connections in MCP servers.

FAQ from mysql_mcpserver_stdio?

  • What programming language is used?

The project is developed in Python with a Flask frontend.

  • How do I test the generated server files?

You can use MCP Inspector to test the generated server files for proper tool invocation.

  • Is there a recommended client for MCP?

Yes, CherryStudio is recommended for its convenience.

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