9 Commits (db5f1ea498f736d4ff733bbd41ec649d073cf932)

Author	SHA1	Message	Date
Rene Cannao	3daaa5c592	feat: Implement RAG (Retrieval-Augmented Generation) subsystem ... Adds a complete RAG subsystem to ProxySQL with: - RAG_Tool_Handler implementing all MCP tools for retrieval operations - Database schema with FTS and vector support - FTS, vector, and hybrid search capabilities - Fetch and refetch tools for document/chunk retrieval - Admin tools for monitoring - Configuration variables for RAG parameters - Comprehensive documentation and test scripts Implements v0 deliverables from RAG blueprint: - SQLite schema initialization - Source registry management - MCP tools: search_fts, search_vector, search_hybrid, get_chunks, get_docs, fetch_from_source, admin.stats - Unit/integration tests and examples	3 months ago
Rene Cannao	aced263367	docs: Update MCP documentation to reflect current implementation ... This commit completes a comprehensive review and update of all MCP-related documentation: - Remove deprecated FastAPI POC files - Update Architecture.md to reflect implemented multi-endpoint architecture - Update VARIABLES.md with new AI endpoint authentication - Update Tool_Discovery_Guide.md with discovery and LLM tools - Update FTS_Implementation_Plan.md to reflect implemented status - Update Vector_Embeddings_Implementation_Plan.md to show planned status - Update Database_Discovery_Agent.md to clarify conceptual design status - Update scripts/mcp/README.md with current multi-handler architecture - Update STDIO_BRIDGE_README.md with complete tool list All documentation now accurately reflects the current ProxySQL MCP implementation with 6 dedicated tool handlers and two-phase discovery.	3 months ago
Rene Cannao	35b0b224ff	refactor: Remove mcp-catalog_path variable and hardcode catalog path ... Remove the mcp-catalog_path configuration variable and hardcode the catalog database path to datadir/mcp_catalog.db for stability. Rationale: The catalog database is session state, not user configuration. Runtime swapping of the catalog could cause tables to be missed and the catalog to fail even if it was succeeding a second earlier. Changes: - Removed catalog_path from mcp_thread_variables_names array - Removed mcp_catalog_path from MCP_Thread variables struct - Removed getter/setter logic for catalog_path - Hardcoded catalog path to GloVars.datadir/mcp_catalog.db in: - ProxySQL_MCP_Server.cpp (Query_Tool_Handler initialization) - Admin_FlushVariables.cpp (MySQL_Tool_Handler reinitialization) - Updated VARIABLES.md to document the hardcoded path - Updated configure_mcp.sh to remove catalog_path configuration - Updated MCP README to remove catalog_path references	3 months ago
Rene Cannao	28742554b5	Use relative catalog path instead of absolute path ... - Change mcp-catalog_path default from /var/lib/proxysql/mcp_catalog.db to mcp_catalog.db - SQLite accepts relative paths, which are resolved relative to the process working directory - ProxySQL's working directory is its datadir, so the catalog will be stored there - Update configure_mcp.sh to set mcp-catalog_path='mcp_catalog.db' - Update lib/MCP_Thread.cpp default to "mcp_catalog.db" - Update README.md to document relative path behavior	3 months ago
Rene Cannao	c53b28e42a	Add comprehensive documentation to MCP README ... - Add architecture overview with ASCII diagram showing all components - Add detailed component explanations (ProxySQL MCP Module, Connection Pool, Catalog, Test Scripts) - Add testing flow diagram with 4-step process - Add Quick Start section with copy/paste commands for native and Docker modes - Add detailed documentation for each script explaining what they do and why - Add troubleshooting section for common issues - Add default configuration reference table - Add environment variables reference This allows users to understand the architecture and run tests without needing to understand implementation details.	3 months ago
Rene Cannao	b3646b4798	Fix argument parsing and documentation in setup_test_db.sh ... Fixed critical issues with argument parsing that prevented the script from working correctly: 1. Fixed argument order - script now supports both: - ./setup_test_db.sh <command> [options] - ./setup_test_db.sh [options] <command> 2. Fixed --help option - now shows help instead of running commands 3. Updated README.md examples with correct syntax: - OLD: ./setup_test_db.sh --mode native start (wrong) - NEW: ./setup_test_db.sh start --mode native (correct) The script now properly: - Parses -h/--help anywhere and shows usage - Handles options before or after the command - Auto-detects mode when not specified - Shows helpful connection info after setup All examples in README.md updated with correct command syntax.	3 months ago
Rene Cannao	3d827144e8	Add required environment variables section to README ... Added comprehensive environment variable documentation to the README Prerequisites section to make it clear what needs to be configured before running the test scripts. Changes: - Added "Required Environment Variables" subsection under Prerequisites - Listed all ProxySQL Admin, MySQL, and MCP server environment variables - Added quick setup example for adding variables to ~/.bashrc - Made it clear that PROXYSQL_ADMIN_PASSWORD and MYSQL_PASSWORD need to be set Users now have clear guidance on required configuration before testing.	3 months ago
Rene Cannao	ad2e2a24d1	Add native MySQL mode support to test database setup ... Updated setup_test_db.sh to support both Docker and native MySQL modes. Changes: - Added --mode option: docker, native, or auto (default: auto-detect) - Auto-detect: tries Docker first, then falls back to native MySQL - Native mode functions: start_native, status_native, connect_native, reset_native - Native mode connects to existing MySQL server (no Docker required) - Added --host, --port, --user, --password, --database options - Environment variable support: MYSQL_HOST, MYSQL_PORT, MYSQL_USER, MYSQL_PASSWORD Updated README.md with: - Native mode quick start guide - Docker mode quick start guide - Auto-detect mode documentation - Comprehensive setup_test_db.sh usage examples - Environment variable documentation Usage examples: # Auto-detect mode ./setup_test_db.sh start # Native MySQL mode ./setup_test_db.sh --mode native --host localhost --port 3306 start # Docker mode ./setup_test_db.sh --mode docker start	3 months ago
Rene Cannao	e9a6dd0b3e	Add comprehensive MCP testing suite in scripts/mcp/ ... Created a complete testing suite for the MCP module with MySQL connection pool and exploration tools. Files added: - README.md: Comprehensive testing documentation - setup_test_db.sh: Docker-based test MySQL database setup - Start/stop/status/connect commands - Creates sample schema (customers, orders, products, order_items) - Includes views and stored procedures for testing - configure_mcp.sh: ProxySQL MCP module configuration - Configures MySQL connection parameters - Enables/disables MCP server - Shows current configuration status - test_mcp_tools.sh: Main MCP tools test suite - Tests all 15 MCP tools (list_schemas, list_tables, etc.) - Includes catalog tests (upsert, get, search, delete) - Reports pass/fail statistics - stress_test.sh: Concurrent connection stress testing - Configurable number of concurrent requests - Response time measurement - Success rate calculation - test_catalog.sh: Catalog/LLM memory specific tests - 12 catalog operation tests - FTS search testing - CRUD verification All scripts are executable and include: - Command-line argument parsing - Colored output for readability - Error handling and validation - Usage/help documentation - Environment variable support	3 months ago