An intelligent MySQL MCP Server with enterprise data federation capabilities, enabling LLMs to query and analyze data across multiple disparate MySQL data sources. Goes beyond basic querying to provide comprehensive business intelligence, cross-system data correlation, and federated analytics with high-performance caching.
- π Multi-source MySQL access: Connect to completely different business systems (CRM, ERP, E-commerce, etc.)
- π§ Intelligent source classification: Automatically identify and catalog CRM, E-commerce, ERP, Marketing, Support systems
- π Cross-source query engine: Execute federated queries combining data from multiple business systems
- π 360Β° business intelligence: Complete customer view across all touchpoints and systems
- π Relationship detection: Find connections between disparate systems (shared customer IDs, etc.)
- π₯ User behavior federation: Track customers across CRM β Marketing β E-commerce β Support journey
- πΌ Business process analytics: End-to-end analysis from procurement β inventory β sales β finance
- π― Revenue attribution: Multi-touch attribution across marketing, sales, and customer systems
- π Data consistency auditing: Compare and validate data integrity across business systems
- π Cross-system KPI reporting: Unified executive dashboards combining all business data
- π High-performance caching: Source-specific intelligent caching with TTL support
- π Enterprise security: Read-only access with query validation and connection timeouts
- ποΈ Architecture detection: Automatic identification of star schemas and data warehouse patterns
- π§ Connection pooling: Efficient connection management across multiple business systems
- π Smithery deployment: Easy deployment with configuration UI on Smithery.ai
- MySQL 5.5+ compatible: Works with MySQL 5.5 and later versions
# Clone and install
git clone https://github.com/ttpears/mcp-mysql.git
cd mcp-mysql
npm install && npm run build
# Add to Claude Code with your MySQL credentials
# For server-wide access (recommended):
claude mcp add mysql-server npm start \
-e MYSQL_HOST=localhost \
-e MYSQL_USER=your_user \
-e MYSQL_PASSWORD=your_password
# For single database access:
claude mcp add mysql-server npm start \
-e MYSQL_HOST=localhost \
-e MYSQL_USER=your_user \
-e MYSQL_PASSWORD=your_password \
-e MYSQL_DATABASE=your_databaseVisit Smithery.ai MySQL MCP Server and click "Deploy" for easy setup with configuration UI.
Features when deployed on Smithery:
- ποΈ Configuration UI: Easy setup with form-based configuration
- π Auto-updates: Automatic updates when new versions are released
- β‘ High performance: Optimized deployment with caching enabled
- π Secure: Environment-based secret management
npm install mysql-mcp-server| Variable | Default | Description |
|---|---|---|
MYSQL_HOST |
localhost |
MySQL server hostname (default source) |
MYSQL_PORT |
3306 |
MySQL server port (default source) |
MYSQL_USER |
root |
MySQL username (default source) |
MYSQL_PASSWORD |
`` | MySQL password (required for default source) |
MYSQL_DATABASE |
(none) | MySQL database name (optional - server-wide access if omitted) |
MYSQL_SSL |
false |
Enable SSL connection (default source) |
For additional business system data sources, use pattern: MYSQL_HOST_<SOURCE>_*
| Pattern | Example | Description |
|---|---|---|
MYSQL_HOST_<SOURCE>_HOST |
MYSQL_HOST_CRM_HOST |
Hostname for the data source |
MYSQL_HOST_<SOURCE>_PORT |
MYSQL_HOST_CRM_PORT |
Port for the data source (default: 3306) |
MYSQL_HOST_<SOURCE>_USER |
MYSQL_HOST_CRM_USER |
Username for the data source (default: root) |
MYSQL_HOST_<SOURCE>_PASSWORD |
MYSQL_HOST_CRM_PASSWORD |
Password for the data source (required) |
MYSQL_HOST_<SOURCE>_DATABASE |
MYSQL_HOST_CRM_DATABASE |
Database name for the data source (optional) |
MYSQL_HOST_<SOURCE>_SSL |
MYSQL_HOST_CRM_SSL |
Enable SSL for the data source (default: false) |
Note: Each additional data source requires at least MYSQL_HOST_<SOURCE>_HOST and MYSQL_HOST_<SOURCE>_PASSWORD to be configured.
| Variable | Default | Description |
|---|---|---|
MCP_MYSQL_CACHE_ENABLED |
true |
Enable/disable intelligent caching system |
MCP_MYSQL_CACHE_DIR |
~/.mcp-mysql-cache |
Custom cache directory path |
MCP_MYSQL_CACHE_MAX_SIZE |
52428800 |
Maximum cache file size in bytes (50MB) |
MCP_MYSQL_CACHE_RETENTION_DAYS |
30 |
Days to retain cached files |
Enterprise data federation setup:
# Default data source (backward compatible)
export MYSQL_HOST=localhost
export MYSQL_PORT=3306
export MYSQL_USER=analytics_user
export MYSQL_PASSWORD=your_password
export MYSQL_SSL=true
export MCP_MYSQL_CACHE_ENABLED=true
# CRM System (Salesforce MySQL backend)
export MYSQL_HOST_CRM_HOST=crm-db.company.com
export MYSQL_HOST_CRM_USER=crm_readonly
export MYSQL_HOST_CRM_PASSWORD=crm_secret
export MYSQL_HOST_CRM_DATABASE=salesforce_sync
export MYSQL_HOST_CRM_SSL=true
# E-commerce Platform (Shopify/WooCommerce)
export MYSQL_HOST_ECOMMERCE_HOST=shop-db.company.com
export MYSQL_HOST_ECOMMERCE_USER=ecommerce_analytics
export MYSQL_HOST_ECOMMERCE_PASSWORD=shop_secret
export MYSQL_HOST_ECOMMERCE_DATABASE=store_analytics
# ERP System (SAP/Oracle MySQL interface)
export MYSQL_HOST_ERP_HOST=erp-mysql.company.com
export MYSQL_HOST_ERP_USER=erp_reporting
export MYSQL_HOST_ERP_PASSWORD=erp_secret
# Marketing & Support Systems
export MYSQL_HOST_MARKETING_HOST=marketing-db.company.com
export MYSQL_HOST_MARKETING_USER=marketing_readonly
export MYSQL_HOST_MARKETING_PASSWORD=marketing_secret
export MYSQL_HOST_SUPPORT_HOST=support-db.company.com
export MYSQL_HOST_SUPPORT_USER=support_analytics
export MYSQL_HOST_SUPPORT_PASSWORD=support_secretSingle database access (legacy mode):
export MYSQL_HOST=localhost
export MYSQL_PORT=3306
export MYSQL_USER=readonly_user
export MYSQL_PASSWORD=your_password
export MYSQL_DATABASE=your_database
export MYSQL_SSL=trueCustom caching configuration:
export MCP_MYSQL_CACHE_ENABLED=true
export MCP_MYSQL_CACHE_DIR=/custom/cache/path
export MCP_MYSQL_CACHE_MAX_SIZE=104857600 # 100MB
export MCP_MYSQL_CACHE_RETENTION_DAYS=7 # 1 weeknpm startπ’ START HERE - Get comprehensive inventory of all configured business systems and their databases.
Parameters:
refresh(boolean, optional): Force refresh of data source inventoryhost(string, optional): Get inventory for specific data source only
Examples:
// Get complete enterprise data source inventory
{}
// Refresh and get inventory for specific source
{
"host": "crm",
"refresh": true
}What you get:
- π’ Business system classification (CRM, E-commerce, ERP, Marketing, Support, etc.)
- π Database inventory with record counts and connection health
- π Federation capabilities and shared identifiers across systems
- π‘ Cross-system analysis recommendations
π ENTERPRISE POWER TOOL - Execute federated queries across multiple business systems.
Parameters:
queries(array, required): Array of queries to execute across different data sourceshost(string, required): Data source name to execute query ondatabase(string, optional): Database name within the data sourcequery(string, required): SQL query to executealias(string, optional): Alias for this query result
combine_strategy(string, optional): How to combine results ('separate', 'union', 'comparison', 'correlation')analysis_focus(string, optional): Focus area ('performance', 'data_consistency', 'user_behavior', 'business_metrics')
Example - 360Β° Customer Intelligence:
{
"queries": [
{
"host": "crm",
"query": "SELECT customer_id, email, lead_source FROM customers WHERE status = 'active'",
"alias": "crm_customers"
},
{
"host": "ecommerce",
"query": "SELECT customer_email as email, SUM(order_total) as lifetime_value FROM orders GROUP BY customer_email",
"alias": "purchase_history"
},
{
"host": "support",
"query": "SELECT requester_email as email, COUNT(*) as ticket_count FROM tickets GROUP BY requester_email",
"alias": "support_interactions"
}
],
"combine_strategy": "correlation",
"analysis_focus": "user_behavior"
}Execute read-only SQL queries against specific data sources.
Parameters:
query(string, required): SQL query to executeparams(array, optional): Parameters for prepared statementsdatabase(string, optional): Database name to connect tohost(string, optional): Data source name (defaults to 'default')
Examples:
// Query default data source
{
"query": "SELECT * FROM users WHERE status = ?",
"params": ["active"]
}
// Query specific business system
{
"host": "crm",
"database": "salesforce_sync",
"query": "SELECT COUNT(*) as total_leads FROM leads WHERE created_date >= '2024-01-01'"
}Get comprehensive schema information including relationships, constraints, and data patterns.
Parameters:
table(string, optional): Specific table name to analyzeinclude_relationships(boolean, default: true): Include foreign key relationshipsinclude_sample_data(boolean, default: false): Include sample data and statisticssample_size(number, default: 100, max: 1000): Number of sample rows to analyze
Examples:
// Get database overview with relationships
{}
// Get detailed table analysis with sample data
{
"table": "users",
"include_sample_data": true,
"sample_size": 50
}
// Get basic table schema without relationships
{
"table": "orders",
"include_relationships": false
}Analyze table relationships and suggest optimal query patterns for user behavior analysis.
Parameters:
tables(array, required): List of table names to analyzeanalysis_type(string, optional): Type of analysis ('relationships', 'user_behavior', 'data_flow')
Examples:
// Analyze table relationships
{
"tables": ["users", "orders", "products"],
"analysis_type": "relationships"
}
// Analyze for user behavior patterns
{
"tables": ["users", "events", "sessions"],
"analysis_type": "user_behavior"
}
// Trace data flow between tables
{
"tables": ["users", "orders", "order_items"],
"analysis_type": "data_flow"
}π START HERE - Intelligently discover and analyze your entire MySQL server with expert data analytics insights and intelligent caching.
Parameters:
databases(array, optional): List of databases to analyze (if not specified, discovers all accessible databases)focus_area(string, optional): Analytics focus ('user_behavior', 'sales_analytics', 'engagement', 'general')include_recommendations(boolean, default: true): Include expert query recommendationscross_database_analysis(boolean, default: true): Analyze relationships across databasesdetail_level(string, optional): Level of analysis ('summary', 'detailed', 'full')max_tables_per_db(number, default: 20): Maximum tables to analyze per databasepage(number, default: 1): Page number for paginationpage_size(number, default: 5): Number of databases per page
Examples:
// Discover entire MySQL server for user behavior analysis
{
"focus_area": "user_behavior",
"cross_database_analysis": true
}
// Analyze specific databases only
{
"databases": ["ecommerce", "analytics", "logs"],
"focus_area": "sales_analytics"
}
// Quick server overview
{
"focus_area": "general"
}What you get:
- π Complete multi-database server analysis with all executed SQL queries shown
- π§ Intelligent table classification across all databases (fact tables, dimension tables, user tables, event tables)
- π Cross-database relationship mapping and pattern detection
- π Expert analytics insights and performance recommendations per database
- π Ready-to-use SQL queries for cross-database analytics patterns
- π Data quality assessments and optimization suggestions
- ποΈ Architecture analysis (star schema detection, data warehouse patterns)
- β‘ High-performance caching: All results cached with TTL for faster subsequent queries
- π Pagination support: Handle large servers with configurable page sizes
The server includes a comprehensive caching system that dramatically improves performance for repeated operations:
- Query Results: 1-hour TTL -
~/.mcp-mysql-cache/queries/[date]/ - Schema Analysis: 1-2 hour TTL -
~/.mcp-mysql-cache/schema-snapshots/ - Discovery Reports: 4-hour TTL -
~/.mcp-mysql-cache/reports/discovery-reports/ - Relationship Analysis: Cached -
~/.mcp-mysql-cache/reports/relationship-analysis/
- Automatic TTL management: Expired cache automatically detected and refreshed
- Intelligent key generation: Complex queries cached with hash-based keys
- Size limits: Configurable maximum file size (default: 50MB)
- Storage organization: Organized by date and operation type
- Cache info: All responses include cache hit/miss information
- Cross-session: Cache persists across server restarts
- Faster repeated queries: Instant responses for cached operations
- Reduced database load: Less strain on your MySQL server
- Improved UX: Near-instantaneous results for complex analytics
- Development efficiency: Quick iterations during data exploration
- Query Validation: Only read-only operations allowed (SELECT, SHOW, DESCRIBE, EXPLAIN)
- Length Limits: Queries limited to 10,000 characters
- Prepared Statements: Parameterized queries to prevent SQL injection
- Connection Timeouts: Configurable timeouts to prevent hanging connections
- Error Handling: Comprehensive error catching and logging
For security, create a dedicated read-only MySQL user:
-- Create read-only user
CREATE USER 'readonly_user'@'%' IDENTIFIED BY 'secure_password';
-- Grant SELECT privileges
GRANT SELECT ON your_database.* TO 'readonly_user'@'%';
-- Grant SHOW privileges for schema inspection
GRANT SHOW VIEW ON your_database.* TO 'readonly_user'@'%';
-- Flush privileges
FLUSH PRIVILEGES;# Install dependencies
npm install
# Run in development mode
npm run dev
# Build for production
npm run build- MySQL 5.5+
- MariaDB 10.0+
- Node.js 18+
The server provides detailed error messages for:
- Connection failures
- Invalid queries
- Query execution errors
- Parameter validation errors
All errors are logged to stderr while maintaining MCP protocol compliance.
git add .
git commit -m "Initial release of intelligent MySQL MCP Server"
git push origin main- Ensure
mcp.jsonis properly configured - Push to GitHub repository
- Submit to Smithery.ai MCP Registry
- Include the
mcp.jsonfile for automatic discovery
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
This project is licensed under the MIT License - see the LICENSE file for details.
- π Issues: GitHub Issues
- π¬ Discussions: GitHub Discussions
- π Documentation: Full Documentation