What problem does it solve? Setting up and switching between multiple Redash instances (dev, staging, production) as MCP servers requires manual configuration of environment variables and MCP entries, which is error-prone and hard to track. ## Core Features & Use Cases - Single-environment setup: Connect one Redash instance by setting REDASH_URL and REDASH_API_KEY in the project .env file. - Multi-environment management: Add, list, inspect, and remove additional Redash MCP servers using suffix-based naming (e.g., redash-dev, redash-stg). - Configuration auditing: Check which environment variables are set and which MCP servers are active with /redash-list and /redash-status. - Use Case: A data analyst working across dev and production Redash instances runs /redash-add dev and /redash-add stg, sets the corresponding environment variables, and verifies everything with /redash-status before querying. ## Quick Start Set REDASH_URL and REDASH_API_KEY in your project .env file, then ask the AI to show the active Redash MCP configuration using the redash-status command.