MySQL MCP服务器

Created By
lichuanrong7a year ago
在 cursor 工具中通过 mysql mcp 服务读取本地 mysql 库,方便通过 AI 来编程开发
Overview

What is MySQL MCP Server?

MySQL MCP Server is an API service developed in Node.js that provides direct access to MySQL databases for Cursor AI, allowing for SQL queries and data operations through a standardized interface.

How to use MySQL MCP Server?

To use MySQL MCP Server, clone the repository, install dependencies, configure environment variables, and start the service. You can then integrate it with Cursor AI to perform database operations using natural language.

Key features of MySQL MCP Server?

  • SQL Query Execution: Supports various SQL statements (SELECT, INSERT, UPDATE, DELETE).
  • Table Structure Query: Retrieve detailed information about database tables.
  • Real-time Data Access: Provides real-time access to the database for AI applications.
  • Secure Connection: Configurable database connection parameters via environment variables.
  • CORS Support: Built-in support for cross-origin requests.
  • Standardized Response: Unified API response format for easier integration.
  • MCP Protocol Support: Fully implements the MCP protocol for seamless integration with Cursor AI.

Use cases of MySQL MCP Server?

  1. Executing complex SQL queries through natural language.
  2. Retrieving database schema information for analysis.
  3. Integrating with AI applications for data-driven insights.

FAQ from MySQL MCP Server?

  • Can MySQL MCP Server handle all SQL operations?

Yes! It supports a wide range of SQL operations including querying, inserting, updating, and deleting data.

  • Is MySQL MCP Server free to use?

Yes! It is open-source and free to use for everyone.

  • How do I troubleshoot connection issues?

Check the database connection information, ensure the database service is running, and verify network settings.

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

20 hours ago
Gpt Scrambler

2 days ago