databases

MySQL Database Explorer

dpflucas

by dpflucas

Explore MySQL databases securely with read-only access. Execute safeguarded sequel queries and review schemas easily, wi

Provides secure, read-only access to MySQL databases for exploring schemas and executing SELECT queries with built-in safeguards against SQL injection, query timeouts, and row limits.

github stars

59

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Read-only with SQL injection protectionBuilt-in query timeouts and row limitsNo data modification risk

best for

  • / Database administrators exploring unfamiliar schemas
  • / Developers analyzing database structure
  • / Data analysts querying production databases safely
  • / Teams needing controlled database access

capabilities

  • / List databases and tables
  • / Describe table schemas and structure
  • / Execute SELECT queries with safety validation
  • / Browse database metadata
  • / Run SHOW and EXPLAIN statements
  • / Query with automatic timeouts and row limits

what it does

Provides secure, read-only access to MySQL databases for exploring schemas and running SELECT queries. Includes built-in protection against SQL injection and resource abuse.

about

MySQL Database Explorer is a community-built MCP server published by dpflucas that provides AI assistants with tools and capabilities via the Model Context Protocol. Explore MySQL databases securely with read-only access. Execute safeguarded sequel queries and review schemas easily, wi It is categorized under databases.

how to install

You can install MySQL Database Explorer in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

MySQL Database Explorer is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

mysql-mcp-server MCP server [![npm version](https://img.shields.io/npm/v/mysql-mcp-server?color=blue)](https://www.npmjs.com/package/mysql-mcp-server) [![smithery badge](https://smithery.ai/badge/@dpflucas/mysql-mcp-server)](https://smithery.ai/server/@dpflucas/mysql-mcp-server) # MySQL Database Access MCP Server This MCP server provides read-only access to MySQL databases. It allows you to: - List available databases - List tables in a database - Describe table schemas - Execute read-only SQL queries ## Security Features - **Read-only access**: Only SELECT, SHOW, DESCRIBE, and EXPLAIN statements are allowed - **Query validation**: Prevents SQL injection and blocks any data modification attempts - **Query timeout**: Prevents long-running queries from consuming resources - **Row limit**: Prevents excessive data return ## Installation ### 1. Install using one of these methods: #### Install from NPM ```bash # Install globally npm install -g mysql-mcp-server # Or install locally in your project npm install mysql-mcp-server ``` #### Build from Source ```bash # Clone the repository git clone https://github.com/dpflucas/mysql-mcp-server.git cd mysql-mcp-server # Install dependencies and build npm install npm run build ``` #### Install via Smithery To install MySQL Database Access MCP Server for Claude AI automatically via [Smithery](https://smithery.ai/server/@dpflucas/mysql-mcp-server): ```bash npx -y @smithery/cli install @dpflucas/mysql-mcp-server --client claude ``` ### 2. Configure environment variables The server requires the following environment variables: - `MYSQL_HOST`: Database server hostname - `MYSQL_PORT`: Database server port (default: 3306) - `MYSQL_USER`: Database username - `MYSQL_PASSWORD`: Database password (optional, but recommended for secure connections) - `MYSQL_DATABASE`: Default database name (optional) ### 3. Add to MCP settings Add the following configuration to your MCP settings file: If you installed via npm (Option 1): ```json { "mcpServers": { "mysql": { "command": "npx", "args": ["mysql-mcp-server"], "env": { "MYSQL_HOST": "your-mysql-host", "MYSQL_PORT": "3306", "MYSQL_USER": "your-mysql-user", "MYSQL_PASSWORD": "your-mysql-password", "MYSQL_DATABASE": "your-default-database" }, "disabled": false, "autoApprove": [] } } } ``` If you built from source (Option 2): ```json { "mcpServers": { "mysql": { "command": "node", "args": ["/path/to/mysql-mcp-server/build/index.js"], "env": { "MYSQL_HOST": "your-mysql-host", "MYSQL_PORT": "3306", "MYSQL_USER": "your-mysql-user", "MYSQL_PASSWORD": "your-mysql-password", "MYSQL_DATABASE": "your-default-database" }, "disabled": false, "autoApprove": [] } } } ``` ## Available Tools ### list_databases Lists all accessible databases on the MySQL server. **Parameters**: None **Example**: ```json { "server_name": "mysql", "tool_name": "list_databases", "arguments": {} } ``` ### list_tables Lists all tables in a specified database. **Parameters**: - `database` (optional): Database name (uses default if not specified) **Example**: ```json { "server_name": "mysql", "tool_name": "list_tables", "arguments": { "database": "my_database" } } ``` ### describe_table Shows the schema for a specific table. **Parameters**: - `database` (optional): Database name (uses default if not specified) - `table` (required): Table name **Example**: ```json { "server_name": "mysql", "tool_name": "describe_table", "arguments": { "database": "my_database", "table": "my_table" } } ``` ### execute_query Executes a read-only SQL query. **Parameters**: - `query` (required): SQL query (only SELECT, SHOW, DESCRIBE, and EXPLAIN statements are allowed) - `database` (optional): Database name (uses default if not specified) **Example**: ```json { "server_name": "mysql", "tool_name": "execute_query", "arguments": { "database": "my_database", "query": "SELECT * FROM my_table LIMIT 10" } } ``` ## Advanced Connection Pool Configuration For more control over the MySQL connection pool behavior, you can configure additional parameters: ```json { "mcpServers": { "mysql": { "command": "npx", "args": ["mysql-mcp-server"], "env": { "MYSQL_HOST": "your-mysql-host", "MYSQL_PORT": "3306", "MYSQL_USER": "your-mysql-user", "MYSQL_PASSWORD": "your-mysql-password", "MYSQL_DATABASE": "your-default-database", "MYSQL_CONNECTION_LIMIT": "10", "MYSQL_QUEUE_LIMIT": "0", "MYSQL_CONNECT_TIMEOUT": "10000", "MYSQL_IDLE_TIMEOUT": "60000", "MYSQL_MAX_IDLE": "10" }, "disabled": false, "autoApprove": [] } } } ``` These advanced options allow you to: - `MYSQL_CONNECTION_LIMIT`: Control the maximum number of connections in the pool (default: 10) - `MYSQL_QUEUE_LIMIT`: Set the maximum number of connection requests to queue (default: 0, unlimited) - `MYSQL_CONNECT_TIMEOUT`: Adjust the connection timeout in milliseconds (default: 10000) - `MYSQL_IDLE_TIMEOUT`: Configure how long a connection can be idle before being released (in milliseconds) - `MYSQL_MAX_IDLE`: Set the maximum number of idle connections to keep in the pool ## Testing The server includes test scripts to verify functionality with your MySQL setup: ### 1. Setup Test Database This script creates a test database, table, and sample data: ```bash # Set your MySQL credentials as environment variables export MYSQL_HOST=localhost export MYSQL_PORT=3306 export MYSQL_USER=your_username export MYSQL_PASSWORD=your_password # Run the setup script npm run test:setup ``` ### 2. Test MCP Tools This script tests each of the MCP tools against the test database: ```bash # Set your MySQL credentials as environment variables export MYSQL_HOST=localhost export MYSQL_PORT=3306 export MYSQL_USER=your_username export MYSQL_PASSWORD=your_password export MYSQL_DATABASE=mcp_test_db # Run the tools test script npm run test:tools ``` ### 3. Run All Tests To run both setup and tool tests: ```bash # Set your MySQL credentials as environment variables export MYSQL_HOST=localhost export MYSQL_PORT=3306 export MYSQL_USER=your_username export MYSQL_PASSWORD=your_password # Run all tests npm test ``` ## Troubleshooting If you encounter issues: 1. Check the server logs for error messages 2. Verify your MySQL credentials and connection details 3. Ensure your MySQL user has appropriate permissions 4. Check that your query is read-only and properly formatted ## License This project is licensed under the MIT License - see the [LICENSE](../LICENSE) file for details.

FAQ

What is the MySQL Database Explorer MCP server?
MySQL Database Explorer is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for MySQL Database Explorer?
This profile displays 33 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.

Use Cases

Direct Database Queries from AI

Enable Claude to query your database directly using natural language

Example

Ask 'Show me top 10 customers by revenue this month' and get SQL results instantly

Eliminate manual SQL writing for ad-hoc queries, get insights 10x faster

Data Analysis & Reporting

Generate complex reports and analytics without leaving conversation

Example

Analyze sales trends, cohort retention, user behavior patterns conversationally

Democratize data access—non-technical team members can query databases

Schema Exploration

Understand database structure, relationships, and data models

Example

'Explain the user_orders table schema and its relationships'

Onboard engineers faster, explore unfamiliar databases efficiently

Data Validation & Quality Checks

Run data quality queries to catch anomalies and inconsistencies

Example

Find duplicate records, missing values, orphaned foreign keys automatically

Maintain data integrity with less manual SQL work

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor with MCP support
  • Database credentials (read-only recommended for safety)
  • Network access from Claude client to database
  • Understanding of database security and access control

Time Estimate

15-30 minutes including configuration and testing

Installation Steps

  1. 1.Install MCP server: npm install -g @modelcontextprotocol/server-[name]
  2. 2.Configure database connection in Claude Desktop config (~/.claude/mcp.json)
  3. 3.Provide connection string: host, port, database, username, password
  4. 4.Restart Claude Desktop to load MCP server
  5. 5.Test connection: 'List all tables in database'
  6. 6.Run simple query: 'Show me 5 rows from users table'
  7. 7.Verify results and permissions are correct
  8. 8.Document query patterns for team use

Troubleshooting

  • Connection refused: Check database is running and network accessible
  • Authentication failed: Verify credentials, check user permissions
  • Claude can't see tables: Grant appropriate read permissions to database user
  • Slow queries: Add indexes, limit result set size, use read replicas
  • MCP server not loading: Check config syntax, restart Claude Desktop

Best Practices

✓ Do

  • +Use read-only database credentials to prevent accidental writes
  • +Connect to read replica, not production primary database
  • +Set query timeout limits to prevent long-running queries
  • +Document database schema and common queries for AI context
  • +Monitor query performance and optimize slow queries
  • +Use connection pooling for better performance
  • +Test with non-production data first

✗ Don't

  • Don't use production write credentials—risk of data corruption
  • Don't query production database during peak traffic hours
  • Don't expose sensitive PII without proper access controls
  • Don't skip query result validation—AI can misinterpret schema
  • Don't allow unlimited result set sizes—set LIMIT clauses
  • Don't share database credentials in plain text config files

💡 Pro Tips

  • Create database views for common queries to simplify AI access
  • Add schema comments/descriptions so AI understands column meanings
  • Use semantic table/column names ('customer_lifetime_value' not 'clv')
  • Set up query logging to audit what Claude is querying
  • Create saved query templates for recurring analysis
  • Combine with data visualization tools for better insights

Technical Details

Architecture

MCP server acts as bridge between Claude and database, translating natural language to SQL queries and returning results in structured format.

Protocols

  • Model Context Protocol (MCP)
  • Database-specific protocols (PostgreSQL, MySQL, MongoDB)

Compatibility

  • PostgreSQL
  • MySQL
  • SQLite
  • MongoDB
  • Redis

When to Use This

✓ Use When

Use for ad-hoc data queries, exploratory analysis, report generation, schema exploration, and democratizing data access. Best for read-heavy analytics workloads.

✗ Avoid When

Avoid for production write operations, mission-critical transactions, real-time OLTP workloads, or when database contains sensitive PII without proper access controls. Use read replicas, not primary.

Integration

  • Read replica connection for analytics queries
  • Database view layer to abstract complex joins
  • Query result caching for repeated questions
  • Audit logging of all AI-generated queries

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.733 reviews
  • Ishan Martin· Dec 28, 2024

    MySQL Database Explorer is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Mia Agarwal· Dec 20, 2024

    We wired MySQL Database Explorer into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Dhruvi Jain· Dec 16, 2024

    MySQL Database Explorer is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Xiao Okafor· Nov 19, 2024

    Useful MCP listing: MySQL Database Explorer is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Mia Bansal· Nov 15, 2024

    MySQL Database Explorer has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Ishan Khan· Nov 11, 2024

    MySQL Database Explorer reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Oshnikdeep· Nov 7, 2024

    Useful MCP listing: MySQL Database Explorer is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Rahul Santra· Nov 3, 2024

    MySQL Database Explorer has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Ganesh Mohane· Oct 26, 2024

    MySQL Database Explorer reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Pratham Ware· Oct 22, 2024

    According to our notes, MySQL Database Explorer benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

showing 1-10 of 33

1 / 4