MySQL Integration Link

Connect Claude Code directly to MySQL databases for real-time querying, schema exploration, and data management through the Model Context Protocol.

When to Use This MCP Server

Connect this server when you need to:

• Query MySQL databases directly from Claude Code without switching to a separate database client or terminal session
• Explore table schemas, indexes, and relationships while writing application code that depends on database structure
• Perform data validation, migration checks, or ad-hoc analysis during development without leaving your coding workflow

Consider alternatives when:

• You need to connect to PostgreSQL, SQLite, or other non-MySQL databases, which have their own dedicated MCP servers
• Your database requires SSH tunneling or VPN access that cannot be expressed through a simple connection string

Quick Start

Configuration

Copy
name: mysql-integration-link
type: mcp
category: database

Example Connection

Copy
claude mcp:connect mysql-integration-link

Available Tools

query:          Execute SQL queries against the connected MySQL database and return results
list-tables:    Retrieve all tables in the current database with row counts and engine info
describe-table: Show column definitions, types, indexes, and foreign keys for a table
list-databases: Enumerate all databases accessible with the current credentials
execute:        Run write operations (INSERT, UPDATE, DELETE) with transaction support

Core Concepts

MySQL MCP Architecture Overview

Aspect	Details
Transport	stdio-based process communication via uvx package runner
Authentication	MySQL connection string with user, password, host, port, and database
Query Execution	Read and write queries routed through a persistent connection pool
Schema Introspection	INFORMATION_SCHEMA queries for metadata without touching application data
Security Model	Credentials passed via environment variables, never stored in config files

Connection Architecture

Claude Code IDE
    |
    v
[MCP Client] --stdio--> [mcp-server-mysql]
                              |
                              v
                     [MySQL Connection Pool]
                              |
                              v
                   [MySQL Server Instance]
                     /        |        \
                  db_1      db_2      db_3

Configuration

Parameter	Type	Default	Description
MYSQL_CONNECTION_STRING	string	required	Full MySQL connection URI in the format mysql://user:password@host:port/dbname
connection_pool_size	integer	5	Maximum number of concurrent connections maintained in the pool
query_timeout	integer	30000	Maximum time in milliseconds before a query is terminated
read_only	boolean	false	When true, blocks all write operations at the MCP server level
ssl_mode	string	preferred	SSL connection mode: disabled, preferred, required, or verify-identity

Best Practices

1. Use Read-Only Connections for Exploration - When connecting to production databases, configure the connection string with a read-only user account. This prevents accidental data modifications while still allowing full schema exploration and SELECT queries during your development workflow.

2. Scope Connections to Specific Databases - Always include the database name in your connection string rather than connecting at the server level. This reduces the risk of accidentally querying the wrong database and ensures tool results are contextually relevant to your current project.

3. Leverage Schema Introspection Before Querying - Use the describe-table and list-tables tools before writing complex queries. Understanding the exact column types, nullable constraints, and index coverage helps you write more efficient queries and catch schema mismatches early.

4. Rotate Credentials Regularly - Store your MySQL credentials in environment variables and rotate them on a schedule. Never embed passwords directly in MCP configuration files, especially in shared or version-controlled project settings.

5. Set Appropriate Query Timeouts - Configure query_timeout to prevent long-running queries from blocking your development session. A timeout of 10-30 seconds is appropriate for most interactive development queries.

Common Issues

1. Connection Refused on localhost - Verify that MySQL is running and accepting connections on the specified port. Check that the bind-address in your MySQL configuration allows connections from 127.0.0.1, and confirm no firewall rules are blocking the port.

2. Authentication Plugin Not Supported - Older MySQL servers may use mysql_native_password while newer ones default to caching_sha2_password. Ensure your MySQL user account uses a compatible authentication plugin, or update the connection string to specify the auth method.

3. Query Returns Empty When Data Exists - Confirm you are connected to the correct database by running list-databases first. Connection strings that omit the database name may default to a system schema with no application tables.