This MCP server provides a server-side rendering service for generating a variety of charts using MinIO as the object storage backend. It supports 22+ chart types including line, area, column, bar, pie, radar, sankey, treemap, and more, with server-side rendering for fast image generation. The service exposes RESTful endpoints and a documented API, and can store generated chart assets in MinIO and return accessible URLs. To run, you can either use Docker Compose for a complete deployment or run the Node.js application locally for development. Typical usage involves starting the server, then sending JSON payloads to generate charts (e.g., line, pie) via the API endpoints described in the API docs. The setup also includes a MinIO instance for storage, with a web console at / (MinIO default port 9001).

Prerequisites:

• Node.js v18+ (and npm or yarn)
• Docker and Docker Compose (optional for Docker deployment)
• Git

Install and run locally (development):

1. Clone the repository: git clone <repository-url> cd mcp-server-chart-minio
2. Install dependencies: npm install
3. Start MinIO service (optional if you already have MinIO): npm run docker:up:minio

   or via Docker Compose

   docker compose -f docker-compose.minio.yml up -d
4. Create or edit your local environment file (.env) with MinIO and API settings as needed.
5. Run the development server: npm run start:dev

Run in Docker (production-like):

1. Ensure you have a docker-compose.minio.yml and .env or .env.production configured.
2. Start all services: docker compose --env-file .env.docker up -d
3. Access API at http://localhost:3000 (or as configured in PUBLIC_API_URL). API docs at http://localhost:3000/api/docs.

Notes and tips:

• The project relies on MinIO for object storage; configure MINIO_ROOT_USER/MINIO_ROOT_PASSWORD and MINIO_BUCKET_NAME for your environment.
• Multiple .env files are used for different environments (.env for local, .env.docker for Docker, .env.production for production). Ensure the correct file is loaded or explicitly set environment variables.
• If you modify ports, adjust PUBLIC_API_URL and any external endpoint values accordingly.
• For server-side rendering, ensure the system has the required canvas and rendering dependencies installed (as described for local development).
• The API endpoints and request payloads are documented in the API docs URL. Use the provided examples as references for chart-generating requests.