@davewind/mysql-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is @davewind/mysql-mcp-server?

@davewind/mysql-mcp-server is a Model Context Protocol server that provides read-only access to MySQL databases, enabling LLMs to inspect database schemas and execute read-only queries.

how to use @davewind/mysql-mcp-server?

To use the server, install it via npm and configure the MCP settings in a JSON file. You can then execute read-only SQL queries against the connected database.

key features of @davewind/mysql-mcp-server?

  • Read-Only Database Access: Enforces read-only operations through SQL validation and READ ONLY transactions.
  • Schema Discovery: Automatically identifies and exposes database table structures.
  • SQL Query Execution: Provides a query tool for executing SELECT statements.
  • Model Context Protocol Compliance: Implements the MCP specification for seamless integration with compatible LLMs.
  • Simple Configuration: Easy setup with minimal configuration required.

use cases of @davewind/mysql-mcp-server?

  1. Allowing LLMs to query MySQL databases without modifying data.
  2. Enabling data analysis and reporting through read-only access.
  3. Facilitating integration with AI systems that require database insights.

FAQ from @davewind/mysql-mcp-server?

  • Can I modify data using this server?

No, the server only allows read-only operations.

  • How do I install the server?

You can install it using the command: npm install @davewind/mysql-mcp-server -g.

  • What is the security model?

The server implements strict security measures, allowing only SELECT statements and executing all queries within READ ONLY transactions.

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