SQL MCP Server for Claude Desktop

A natural language interface to your local MySQL databases through Claude Desktop. This MCP (Machine Communication Protocol) server allows Claude to execute SQL queries on your local MySQL databases, enabling you to interact with your databases using natural language.

Features

• Natural language to SQL query conversion through Claude
• Secure connection to local MySQL databases
• Support for multiple databases
• Transaction management for data consistency
• Connection pooling for better performance
• Support for all types of SQL queries (SELECT, INSERT, UPDATE, DELETE, etc.)

Prerequisites

• Python 3.8 or higher
• MySQL server installed and running
• Claude Desktop application
• Virtual environment (recommended)

Installation

1. Clone this repository:

2. Create and activate a virtual environment:

3. Install dependencies:

4. Create a .env file in the project root with your MySQL credentials:

5. Update the directory path in run.sh:

6. Make the run script executable:

Configuration in Claude Desktop

1. Open Claude Desktop's MCP configuration
2. Add the following configuration:

Replace /absolute/path/to/your/mysql-mcp with the actual absolute path to your project directory.

Usage

Once configured, you can interact with your databases through Claude Desktop using natural language. Examples:

1. Selecting a database and creating a table:

2. Inserting data:

3. Querying data:

Important Notes

• Always use absolute paths in the run.sh script and Claude Desktop configuration
• Ensure MySQL server is running before using the MCP server
• Keep your .env file secure and never commit it to version control
• The MCP server uses connection pooling with a default pool size of 5 connections

Troubleshooting

1. If you get a "connection refused" error, ensure your MySQL server is running
2. If you get an authentication error, verify your credentials in the .env file
3. For permission errors, ensure your MySQL user has appropriate privileges for the operations you're trying to perform

Security Considerations

• Store sensitive credentials in the .env file
• Use a MySQL user with appropriate permissions (avoid using root)
• Keep your virtual environment and dependencies up to date
• Consider network security if accessing non-localhost MySQL servers