@berthojoris/mcp-mysql-server 1.16.4 → 1.17.0

package/README.md

@@ -18,8 +18,9 @@
 
 ## TL;DR - Quick Setup
 
+Run directly with `npx`:
+
 ```bash
-# Run directly with npx (no installation needed)
 npx @berthojoris/mysql-mcp mysql://user:pass@localhost:3306/mydb "list,read,utility"
 ```
 
@@ -30,33 +31,18 @@ Add to your AI agent config (`.mcp.json`, `.cursor/mcp.json`, etc.):
   "mcpServers": {
     "mysql": {
       "command": "npx",
-      "args": ["-y", "@berthojoris/mysql-mcp", "mysql://user:pass@localhost:3306/mydb", "list,read,utility"]
+      "args": [
+        "-y",
+        "@berthojoris/mysql-mcp",
+        "mysql://user:pass@localhost:3306/mydb",
+        "list,read,utility"
+      ]
     }
   }
 }
 ```
 
----
-
-## Table of Contents
-
-- [Installation](#installation)
-- [Quick Start](#quick-start)
-- [AI Agent Configuration](#ai-agent-configuration)
-  - [Standard JSON Config](#standard-json-configuration)
-  - [OpenAI Codex (TOML)](#openai-codex-cli--vs-code-extension)
-  - [Zed IDE](#zed-ide)
-  - [Environment Variables](#environment-variables-configuration)
-  - [Local Development](#local-path-configuration)
-- [Permission System](#permission-system)
-- [Available Tools (145 total)](#available-tools)
-- [Documentation](DOCUMENTATIONS.md)
-- [Comparison: MCP vs Manual Access](#mysql-mcp-vs-manual-database-access)
-- [License](#license)
-
----
-| **Data Masking** | Protect PII/Secrets in responses with configurable profiles (soft/partial/strict) |
-| **TypeScript** | Fully typed with TypeScript definitions |
+For agent-specific examples (Codex TOML, Zed, local path, multi-DB), see **[DOCUMENTATIONS.md → Setup & Configuration](DOCUMENTATIONS.md#setup--configuration-extended)**.
 
 ---
 
@@ -125,20 +111,9 @@ Try asking your AI:
 
 ### Standard JSON Configuration
 
-Most AI agents use a similar JSON configuration format. Use the appropriate config file for your tool:
-
-| AI Agent | Config File Location |
-|----------|---------------------|
-| **Claude Code** | `.mcp.json` (project root) or `~/.mcp.json` (global) |
-| **Cursor** | `.cursor/mcp.json` |
-| **Windsurf** | `~/.codeium/windsurf/mcp_config.json` |
-| **Cline** | VS Code settings or Cline config file |
-| **Gemini CLI** | `~/.gemini/settings.json` |
-| **Kilo Code** | VS Code MCP settings |
-| **Roo Code** | VS Code MCP settings |
-| **Trae AI** | MCP configuration in settings |
-| **Qwen Code** | MCP configuration in settings |
-| **Droid CLI** | MCP configuration in settings |
+Most AI agents use a similar JSON configuration format (the file location varies by tool).
+
+If you want ready-to-copy snippets per client (Claude Code/Cursor/Windsurf/Cline/Codex/Zed), see **[DOCUMENTATIONS.md → Agent Configuration Examples](DOCUMENTATIONS.md#agent-configuration-examples)**.
 
 **Universal Configuration Template:**
 
@@ -152,7 +127,7 @@ Most AI agents use a similar JSON configuration format. Use the appropriate conf
         "-y",
         "@berthojoris/mysql-mcp",
         "mysql://user:password@localhost:3306/database",
-        "list,read,utility,create,update,ddl",
+        "list,read,utility,create,update,ddl"
       ]
     }
   }
@@ -179,141 +154,6 @@ Most AI agents use a similar JSON configuration format. Use the appropriate conf
 
 > **💡 Tip:** The dual-layer approach provides granular control. The 4th argument (permissions) controls broad access levels, while the 5th argument (categories) fine-tunes which specific tools are available.
 
-<details>
-<summary><strong>Multiple Database Configuration</strong></summary>
-
-```json
-{
-  "mcpServers": {
-    "mysql-prod": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@berthojoris/mysql-mcp",
-        "mysql://reader:pass@prod-server:3306/prod_db",
-        "list,read,utility"
-      ]
-    },
-    "mysql-dev": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@berthojoris/mysql-mcp",
-        "mysql://root:pass@localhost:3306/dev_db",
-        "list,read,create,update,delete,execute,ddl,utility"
-      ]
-    }
-  }
-}
-```
-
-</details>
-
----
-
-### OpenAI Codex CLI & VS Code Extension
-
-OpenAI Codex uses TOML format in `~/.codex/config.toml`.
-
-**Quick setup via CLI:**
-
-```bash
-codex mcp add mysql -- npx -y @berthojoris/mysql-mcp mysql://user:pass@localhost:3306/db list,read,utility
-```
-
-**Manual TOML configuration:**
-
-```toml
-[mcp_servers.mysql]
-command = "npx"
-args = ["-y", "@berthojoris/mysql-mcp", "mysql://user:pass@localhost:3306/db", "list,read,utility"]
-startup_timeout_sec = 20
-```
-
-<details>
-<summary><strong>Advanced Codex Configuration</strong></summary>
-
-**With environment variables:**
-
-```toml
-[mcp_servers.mysql]
-command = "npx"
-args = ["-y", "@berthojoris/mysql-mcp"]
-
-[mcp_servers.mysql.env]
-DB_HOST = "localhost"
-DB_PORT = "3306"
-DB_USER = "root"
-DB_PASSWORD = "your_password"
-DB_NAME = "your_database"
-MCP_PERMISSIONS = "list,read,utility"
-```
-
-**Multiple databases:**
-
-```toml
-# Production - Read Only
-[mcp_servers.mysql-prod]
-command = "npx"
-args = ["-y", "@berthojoris/mysql-mcp", "mysql://reader:pass@prod:3306/prod_db", "list,read,utility"]
-startup_timeout_sec = 30
-
-# Development - Full Access
-[mcp_servers.mysql-dev]
-command = "npx"
-args = ["-y", "@berthojoris/mysql-mcp", "mysql://root:pass@localhost:3306/dev_db", "list,read,create,update,delete,execute,ddl,utility"]
-```
-
-**Advanced options:**
-
-```toml
-[mcp_servers.mysql]
-command = "npx"
-args = ["-y", "@berthojoris/mysql-mcp", "mysql://user:pass@localhost:3306/db", "list,read,utility"]
-startup_timeout_sec = 20        # Server startup timeout (default: 10)
-tool_timeout_sec = 120          # Per-tool execution timeout (default: 60)
-enabled = true                  # Set false to disable without deleting
-# enabled_tools = ["list_tables", "read_records"]  # Optional: limit exposed tools
-# disabled_tools = ["drop_table", "delete_record"] # Optional: hide specific tools
-```
-
-**Codex management commands:**
-
-```bash
-codex mcp list          # List all configured MCP servers
-codex mcp list --json   # List with JSON output
-codex mcp remove mysql  # Remove an MCP server
-codex mcp get mysql     # Get details about a specific server
-```
-
-</details>
-
----
-
-### Zed IDE
-
-Zed IDE uses a different structure in `~/.config/zed/settings.json`:
-
-```json
-{
-  "context_servers": {
-    "mysql": {
-      "command": {
-        "path": "npx",
-        "args": [
-          "-y",
-          "@berthojoris/mysql-mcp",
-          "mysql://user:password@localhost:3306/database",
-          "list,read,utility"
-        ]
-      }
-    }
-  }
-}
-```
-
----
-
 ### Environment Variables Configuration
 
 Alternative approach using environment variables instead of connection string:
@@ -387,74 +227,7 @@ Alternative approach using environment variables instead of connection string:
 
 Add `MCP_PRESET` for the base bundle and optionally layer on `MCP_PERMISSIONS` / `MCP_CATEGORIES` for project-specific overrides.
 
-#### Connection Profiles (dev/stage/prod)
-New presets are available for environment-specific control:
-- `dev`: Full access to all tools (explicitly allows everything).
-- `stage`: Allows data modification but blocks destructive DDL (drop/truncate).
-- `prod`: Strict read-only mode, explicitly denying keys modification keys.
-
----
-
-### Local Path Configuration
-
-For development or when you need full control over the source code:
-
-```json
-{
-  "mcpServers": {
-    "mysql": {
-      "command": "node",
-      "args": [
-        "/path/to/mcp_mysql/bin/mcp-mysql.js",
-        "mysql://user:password@localhost:3306/database",
-        "list,read,utility"
-      ]
-    }
-  }
-}
-```
-
-<details>
-<summary><strong>When to Use Local Path</strong></summary>
-
-Use local path configuration when you:
-
-- Want full control over the version and source code
-- Need offline access without internet dependency
-- Want to modify the source for custom functionality
-- Need faster startup without package download
-- Are developing/debugging the MCP server
-- Have network restrictions or security policies
-
-| Feature | Local Path | NPX |
-|---------|------------|-----|
-| **Control** | Full control over code | Depends on npm registry |
-| **Offline** | Works completely offline | Requires internet |
-| **Speed** | Instant startup | Download time |
-| **Customization** | Can modify source | Limited to published version |
-| **Updates** | Manual updates | Automatic updates |
-| **Setup** | Requires building | Zero setup |
-
-**Setup requirements:**
-
-```bash
-cd /path/to/mcp_mysql
-npm install
-npm run build
-```
-
-**Available binaries:**
-
-- `bin/mcp-mysql.js` - CLI wrapper with argument parsing
-- `dist/mcp-server.js` - Direct server executable
-
-**Path tips:**
-
-- Windows: Use double backslashes `\\` in JSON
-- Cross-platform: Use forward slashes `/` if supported
-- Always use absolute paths for reliability
-
-</details>
+For more environment-variable patterns (presets/profiles, client-specific env blocks), see **[DOCUMENTATIONS.md → Setup & Configuration](DOCUMENTATIONS.md#setup--configuration-extended)**.
 
 ---
 
@@ -469,34 +242,19 @@ Control database access with a **dual-layer filtering system** that provides bot
 
 ### Documentation Categories (Recommended)
 
-Use these categories for fine-grained control that matches the tool organization:
-
-| Category | Tools Count | Description |
-|----------|-------------|-------------|
-| `database_discovery` | 4 | List databases, tables, schemas, relationships |
-| `crud_operations` | 4 | Basic Create, Read, Update, Delete operations |
-| `bulk_operations` | 3 | Bulk insert, update, delete with batching |
-| `custom_queries` | 2 | Run custom SELECT or execute SQL |
-| `schema_management` | 4 | CREATE/ALTER/DROP tables (DDL) |
-| `utilities` | 4 | Connection testing, diagnostics, CSV export |
-| `transaction_management` | 5 | BEGIN, COMMIT, ROLLBACK transactions |
-| `stored_procedures` | 6 | Create, execute, manage stored procedures |
-| `views_management` | 6 | Create, alter, drop views |
-| `triggers_management` | 5 | Create, drop triggers |
-| `functions_management` | 6 | Create, execute functions |
-| `index_management` | 5 | Create, drop, analyze indexes |
-| `constraint_management` | 7 | Foreign keys, unique, check constraints |
-| `table_maintenance` | 8 | Analyze, optimize, repair tables |
-| `server_management` | 9 | Process list, explain queries, server info |
-| `performance_monitoring` | 10 | Metrics, slow queries, health checks |
-| `cache_management` | 5 | Query cache stats and configuration |
-| `query_optimization` | 3 | Analyze queries, get optimization hints |
-| `backup_restore` | 5 | Backup/restore database and tables |
-| `import_export` | 5 | Import/export JSON, CSV, SQL |
-| `data_migration` | 5 | Copy, move, clone, sync table data |
-| `schema_migrations` | 9 | Version control for database schema |
-| `analysis` | 4 | AI context optimization and data analysis |
-| `ai_enhancement` | 11 | AI-powered query building, smart discovery, documentation, schema design, security audit, and index recommendations |
+Use documentation categories to fine-tune which tools are exposed (Layer 2):
+
+```text
+database_discovery,crud_operations,bulk_operations,custom_queries,
+schema_management,utilities,transaction_management,stored_procedures,
+views_management,triggers_management,functions_management,index_management,
+constraint_management,table_maintenance,server_management,
+performance_monitoring,cache_management,query_optimization,
+backup_restore,import_export,data_migration,schema_migrations,
+analysis,ai_enhancement
+```
+
+Full category → tool mapping (and examples) lives in **[DOCUMENTATIONS.md → Category Filtering System](DOCUMENTATIONS.md#🆕-category-filtering-system)**.
 
 ### Legacy Categories (Backward Compatible)
 
@@ -513,200 +271,20 @@ Use these categories for fine-grained control that matches the tool organization
 | `transaction` | BEGIN, COMMIT, ROLLBACK | ACID operations |
 | `utility` | Connection testing, diagnostics | Troubleshooting |
 
-### Common Category Sets
-
-#### Using Documentation Categories (Recommended)
-
-| Environment | Categories | Description |
-|-------------|------------|-------------|
-| **Production Read-Only** | `database_discovery,utilities` | Safe exploration only |
-| **Analytics & Reporting** | `database_discovery,crud_operations,custom_queries,performance_monitoring` | Read and analyze |
-| **Data Entry** | `database_discovery,crud_operations,utilities` | Basic CRUD operations |
-| **Data Management** | `database_discovery,crud_operations,bulk_operations,utilities` | CRUD + bulk operations |
-| **Application Backend** | `database_discovery,crud_operations,bulk_operations,custom_queries,transaction_management` | Full app support |
-| **Development & Testing** | `database_discovery,crud_operations,bulk_operations,custom_queries,schema_management,utilities,transaction_management` | Development access |
-| **DBA & DevOps** | `database_discovery,schema_management,table_maintenance,backup_restore,schema_migrations,performance_monitoring` | Admin tasks |
-| **Full Access** | *(leave empty)* | All 145 tools enabled |
-
-#### Using Legacy Categories (Backward Compatible)
-
-| Environment | Permissions | Description |
-|-------------|-------------|-------------|
-| **Production (Safe)** | `list,read,utility` | Read-only access |
-| **Data Entry** | `list,read,create,utility` | Can add records |
-| **Full Data Access** | `list,read,create,update,delete,utility` | All CRUD operations |
-| **With Transactions** | `list,read,create,update,delete,transaction,utility` | CRUD + ACID |
-| **Development** | `list,read,create,update,delete,execute,ddl,transaction,utility` | Full access |
-| **DBA Tasks** | `list,ddl,utility` | Schema management only |
-
-### Adaptive Permission Presets (ReadOnly/Analyst/DBA Lite)
-
-Use presets to bootstrap safe defaults. They **merge** with any explicit permissions/categories you pass via CLI args or env vars.
+Common presets, environment bundles, and multi-environment examples are documented in **[DOCUMENTATIONS.md → Category Filtering System](DOCUMENTATIONS.md#🆕-category-filtering-system)**.
 
-| Preset | Permissions | Categories | Ideal for |
-|--------|-------------|------------|-----------|
-| `readonly` | `list,read,utility` | `database_discovery,crud_operations,custom_queries,utilities,import_export,performance_monitoring,analysis` | Safe read-only data access + exports |
-| `analyst` | `list,read,utility` | `database_discovery,crud_operations,custom_queries,utilities,import_export,performance_monitoring,analysis,query_optimization,cache_management,server_management` | Analytics with plan insights and cache/perf visibility |
-| `dba-lite` | `list,read,utility,ddl,transaction,procedure` | `database_discovery,custom_queries,utilities,server_management,schema_management,table_maintenance,index_management,constraint_management,backup_restore,schema_migrations,performance_monitoring,views_management,triggers_management,functions_management,stored_procedures` | Admin-lite schema care, migrations, and maintenance |
-
-**Usage**
-
-- CLI: `mcp-mysql mysql://user:pass@host:3306/db --preset readonly`
-- CLI with overrides: `mcp-mysql mysql://... --preset analyst "list,read,utility" "performance_monitoring"`
-- Env: `MCP_PRESET=analyst` (or `MCP_PERMISSION_PRESET=analyst`) plus optional `MCP_PERMISSIONS` / `MCP_CATEGORIES` to extend
-
-If an unknown preset is requested without overrides, the server falls back to a safe read-only baseline instead of enabling everything.
-
-### Per-Project Configuration
-
-#### Single-Layer: Permissions Only (Backward Compatible)
-
-Use only the 2nd argument for broad permission-based filtering:
-
-```json
-{
-  "mcpServers": {
-    "mysql": {
-      "command": "node",
-      "args": [
-        "/path/to/bin/mcp-mysql.js",
-        "mysql://user:password@localhost:3306/db",
-        "list,read,utility"
-      ]
-    }
-  }
-}
-```
-
-**Result**: All tools within `list`, `read`, and `utility` permissions are enabled.
-
-#### Dual-Layer: Permissions + Categories (Recommended for Fine Control)
-
-Use both 2nd argument (permissions) and 3rd argument (categories):
-
-```json
-{
-  "mcpServers": {
-    "mysql-prod": {
-      "command": "node",
-      "args": [
-        "/path/to/bin/mcp-mysql.js",
-        "mysql://readonly:pass@prod:3306/app_db",
-        "list,read,utility",
-        "database_discovery,performance_monitoring"
-      ]
-    }
-  }
-}
-```
-
-**Result**: Only tools that have BOTH:
-- Permission: `list`, `read`, OR `utility` AND
-- Category: `database_discovery` OR `performance_monitoring`
-
-**Enabled**: `list_databases`, `list_tables`, `read_table_schema`, `get_table_relationships`, `get_performance_metrics`, `get_slow_queries`, etc.
-
-**Disabled**: `test_connection` (has `utility` permission but not in allowed categories), `read_records` (has `read` permission but category is `crud_operations`), etc.
+---
 
-#### Multiple Environments Example
+## Available Tools
 
-```json
-{
-  "mcpServers": {
-    "mysql-prod-readonly": {
-      "command": "node",
-      "args": [
-        "/path/to/bin/mcp-mysql.js",
-        "mysql://readonly:pass@prod:3306/app_db",
-        "list,read,utility",
-        "database_discovery,performance_monitoring"
-      ]
-    },
-    "mysql-dev-full": {
-      "command": "node",
-      "args": [
-        "/path/to/bin/mcp-mysql.js",
-        "mysql://dev:pass@localhost:3306/dev_db",
-        "list,read,create,update,delete,ddl,transaction,utility"
-      ]
-    },
-    "mysql-dba": {
-      "command": "node",
-      "args": [
-        "/path/to/bin/mcp-mysql.js",
-        "mysql://dba:pass@server:3306/app_db",
-        "list,ddl,utility",
-        "database_discovery,schema_management,table_maintenance,backup_restore,index_management"
-      ]
-    }
-  }
-}
-```
+The server exposes **150 tools** organized into categories (CRUD, schema, backups, migrations, perf/monitoring, and AI enhancement).
 
----
+- Complete list of tools: **[DOCUMENTATIONS.md → Complete Tools Reference](DOCUMENTATIONS.md#🔧-complete-tools-reference)**
+- AI enhancement tools overview: **[DOCUMENTATIONS.md → AI Enhancement Tools](DOCUMENTATIONS.md#🤖-ai-enhancement-tools)**
 
-## Available Tools
+### 🤖 AI Enhancement Tools
 
-The MCP server provides **145 powerful tools** organized into 23 categories:
-
-### Quick Reference
-
-**145 Tools Available** - Organized into 23 categories
-
-| Category | Count | Key Tools |
-|----------|-------|-----------|
-| Database Discovery | 4 | `list_databases`, `list_tables`, `read_table_schema` |
-| CRUD Operations | 4 | `create_record`, `read_records`, `update_record`, `delete_record` |
-| Bulk Operations | 3 | `bulk_insert`, `bulk_update`, `bulk_delete` |
-| Custom Queries | 2 | `run_query`, `execute_sql` |
-| Schema Management | 4 | `create_table`, `alter_table`, `drop_table` |
-| Transactions | 5 | `begin_transaction`, `commit_transaction`, `rollback_transaction` |
-| Stored Procedures | 6 | `create_stored_procedure`, `execute_stored_procedure` |
-| Views | 6 | `create_view`, `alter_view`, `drop_view` |
-| Triggers | 5 | `create_trigger`, `drop_trigger` |
-| Functions | 6 | `create_function`, `execute_function` |
-| Indexes | 5 | `create_index`, `drop_index`, `analyze_index` |
-| Constraints | 7 | `add_foreign_key`, `add_unique_constraint` |
-| Table Maintenance | 8 | `analyze_table`, `optimize_table`, `repair_table` |
-| Server Management | 9 | `show_process_list`, `explain_query` |
-| Performance Monitoring | 10 | `get_performance_metrics`, `get_database_health_check` |
-| Cache | 5 | `get_cache_stats`, `clear_cache` |
-| Query Optimization | 3 | `analyze_query`, `get_optimization_hints`, `repair_query` |
-| Backup & Restore | 5 | `backup_database`, `restore_from_sql` |
-| Import/Export | 6 | `safe_export_table`, `export_table_to_json`, `import_from_csv` |
-| Data Migration | 5 | `copy_table_data`, `sync_table_data` |
-| Schema Migrations | 9 | `create_migration`, `apply_migrations` |
-| Utilities | 4 | `test_connection`, `export_table_to_csv` |
-| Analysis | 4 | `get_column_statistics`, `get_database_summary`, `get_schema_erd` |
-| **AI Enhancement** | 11 | `build_query_from_intent`, `suggest_query_improvements`, `smart_search`, `find_similar_columns`, `discover_data_patterns`, `generate_documentation`, `generate_data_dictionary`, `generate_business_glossary`, `design_schema_from_requirements`, `audit_database_security`, `recommend_indexes` |
-
-### 🤖 AI Enhancement Tools (Phase 1-2 - Implemented)
-
-The MySQL MCP server includes advanced AI-powered productivity tools:
-
-#### **Intelligent Query Assistant** 
-- **`build_query_from_intent`** - Converts natural language to optimized SQL queries
-- **`suggest_query_improvements`** - AI-powered query optimization suggestions
-- *Use case: "Show me active users from last month" → Automatically generates SQL*
-
-#### **Smart Data Discovery Agent**
-- **`smart_search`** - Semantic search for tables, columns, and data patterns  
-- **`find_similar_columns`** - Discover columns with similar names or data patterns
-- **`discover_data_patterns`** - Automatic identification of data patterns and relationships
-- *Use case: Find all customer-related columns across hundreds of tables*
-
-#### **AI-Powered Documentation Generator**
-- **`generate_documentation`** - Automatic database documentation with business glossary
-- **`generate_data_dictionary`** - Interactive data dictionaries with examples
-- **`generate_business_glossary`** - Business terminology mapping to technical fields
-- *Use case: Generate complete documentation for a new database in seconds*
-
-#### **Schema + Security + Indexing (Phase 2)**
-- **`design_schema_from_requirements`** - Generate proposed tables, relationships, and DDL from business requirements
-- **`audit_database_security`** - Best-effort MySQL security audit with prioritized findings
-- **`recommend_indexes`** - Concrete index recommendations from observed query patterns (performance_schema)
-
-> **📖 For detailed tool descriptions, parameters, and examples, see [DOCUMENTATIONS.md](DOCUMENTATIONS.md#🔧-complete-tools-reference)**
+The full **Phase 1–3 (implemented)** overview, examples, and per-tool documentation lives in **[DOCUMENTATIONS.md](DOCUMENTATIONS.md#🤖-ai-enhancement-tools)**.
 
 ---
 
@@ -722,7 +300,7 @@ For comprehensive documentation, see **[DOCUMENTATIONS.md](DOCUMENTATIONS.md)**:
 - **Schema Versioning** - Version control for database schema changes
 - **Transaction Management** - ACID transactions
 - **Stored Procedures** - Create and execute with IN/OUT/INOUT parameters
-- **🤖 AI Enhancement** - Natural language to SQL, smart data discovery, schema design, security audit, and index recommendations (Phase 1-2)
+- **🤖 AI Enhancement** - Natural language to SQL, smart data discovery, schema design, security audit, index recommendations, data generation, visualization, and forecasting (Phase 1-3)
 - **Query Logging** - See all SQL queries executed automatically
 - **Security Features** - Built-in security and best practices
 - **Bulk Operations** - High-performance batch processing

package/dist/config/featureConfig.js

@@ -325,6 +325,12 @@ exports.toolCategoryMap = {
     designSchemaFromRequirements: ToolCategory.UTILITY,
     auditDatabaseSecurity: ToolCategory.UTILITY,
     recommendIndexes: ToolCategory.UTILITY,
+    // Phase 3: AI Enhancement Tools
+    generateTestData: ToolCategory.UTILITY,
+    analyzeSchemaPatterns: ToolCategory.UTILITY,
+    visualizeQuery: ToolCategory.UTILITY,
+    predictQueryPerformance: ToolCategory.UTILITY,
+    forecastDatabaseGrowth: ToolCategory.UTILITY,
 };
 /**
  * Map of tool names to their documentation categories (New Enhanced System)
@@ -491,6 +497,12 @@ exports.toolDocCategoryMap = {
     designSchemaFromRequirements: DocCategory.AI_ENHANCEMENT,
     auditDatabaseSecurity: DocCategory.AI_ENHANCEMENT,
     recommendIndexes: DocCategory.AI_ENHANCEMENT,
+    // Phase 3: AI Enhancement
+    generateTestData: DocCategory.AI_ENHANCEMENT,
+    analyzeSchemaPatterns: DocCategory.AI_ENHANCEMENT,
+    visualizeQuery: DocCategory.AI_ENHANCEMENT,
+    predictQueryPerformance: DocCategory.AI_ENHANCEMENT,
+    forecastDatabaseGrowth: DocCategory.AI_ENHANCEMENT,
 };
 /**
  * Mapping between legacy categories and documentation categories

package/dist/index.d.ts

@@ -31,6 +31,10 @@ export declare class MySQLMCP {
     private schemaDesignTools;
     private securityAuditTools;
     private indexRecommendationTools;
+    private testDataTools;
+    private schemaPatternTools;
+    private queryVisualizationTools;
+    private forecastingTools;
     private security;
     private featureConfig;
     constructor(permissionsConfig?: string, categoriesConfig?: string, presetName?: string);
@@ -1512,5 +1516,55 @@ export declare class MySQLMCP {
         };
         error?: string;
     }>;
+    generateTestData(params: {
+        table_name: string;
+        row_count: number;
+        batch_size?: number;
+        include_nulls?: boolean;
+        database?: string;
+    }): Promise<{
+        status: string;
+        data?: any;
+        error?: string;
+    }>;
+    analyzeSchemaPatterns(params?: {
+        scope?: "database" | "table";
+        table_name?: string;
+        database?: string;
+    }): Promise<{
+        status: string;
+        data?: any;
+        error?: string;
+    }>;
+    visualizeQuery(params: {
+        query: string;
+        include_explain_json?: boolean;
+        format?: "mermaid" | "json" | "both";
+    }): Promise<{
+        status: string;
+        data?: any;
+        error?: string;
+    }>;
+    predictQueryPerformance(params: {
+        query: string;
+        row_growth_multiplier?: number;
+        per_table_row_growth?: Record<string, number>;
+        include_explain_json?: boolean;
+    }): Promise<{
+        status: string;
+        data?: any;
+        error?: string;
+    }>;
+    forecastDatabaseGrowth(params?: {
+        horizon_days?: number;
+        growth_rate_percent_per_day?: number;
+        growth_rate_percent_per_month?: number;
+        per_table_growth_rate_percent_per_day?: Record<string, number>;
+        database?: string;
+    }): Promise<{
+        status: string;
+        data?: any;
+        error?: string;
+    }>;
 }
 export default MySQLMCP;