BI-Chart

The BI Chart MCP Server is a Python-based MCP server that provides endpoints and tooling for loading, processing, and visualizing BI chart data. It was migrated from a TypeScript prototype and is now maintained as a Python project under the mcp_bi_visualizer package. To start using it, run the server via the provided entry point or the dedicated launch script. The server exposes visualization components and data processing modules that you can interact with for loading data, rendering charts, and generating Vega-Lite based visualizations. Typical usage involves starting the server, sending appropriate API requests or using the included utilities to trigger data loading, processing, and rendering of BI charts.

Prerequisites:

• Python 3.8+ (recommended)
• Access to install dependencies (pip)

Installation steps:

1. Clone the repository: git clone <repository-url> cd <repository-directory>

2. (Optional) Create and activate a virtual environment: python -m venv .venv .venv\Scripts\activate # Windows source .venv/bin/activate # macOS/Linux

3. Install dependencies: pip install -r requirements.txt

4. Ensure project structure is in place (mcp_bi_visualizer, scripts, tests) and any configuration files are present (pyproject.toml, setup.py).

5. Run tests (optional): pytest

Notes and tips:

• The server is started via a Python module entry-point (mcp_bi_visualizer.server) or via the provided run_server.py script in scripts/. Ensure you have an active virtual environment when running.
• If you encounter import or module path issues, verify PYTHONPATH includes the project root or install in editable mode (pip install -e .).
• The server uses Vega-Lite based rendering components under visualization/ and relies on data loading/processing modules under data/ and loader/processor.py for data ingestion.
• You can customize configuration through environment variables or by editing project config files such as pyproject.toml or requirements.txt as needed.
• For Windows users, the activation command for the virtual environment differs; adjust accordingly with your shell (PowerShell, CMD, Git Bash).
• If you run into port or API binding issues, check for existing processes using the same port and ensure network/firewall settings allow local development access.