icecast

Icecast MCP is a server that analyzes Icecast XML configurations and provides security, performance, and capacity recommendations. It exposes an MCP-compliant interface over stdio so clients like Claude Desktop or MCP Inspectors can send analysis requests and receive structured feedback. Core tools available include analyze_icecast_config for parsing and auditing Icecast config files, and get_icecast_best_practices for deployment-specific guidance. Use cases generally involve auditing security settings (like authentication configuration and admin credentials), optimizing listener capacity, and receiving best-practice improvements for stability and reliability across small, medium, and large deployments. When interacting via Claude Desktop, you can point to the built server binary or run the server inside Docker, and Claude will translate natural language requests into MCP commands and analyses.

Prerequisites:

• Node.js (LTS version) installed on your system
• Git available to clone the repository
• Optional: Docker installed if you prefer running the server in a container

Installation steps:

1. Clone the repository: git clone https://github.com/splinesreticulating/icecast-mcp.git
2. Install dependencies: cd icecast-mcp npm install
3. Build the TypeScript sources (if applicable): npm run build
4. Run the MCP server locally (example): npm run start
5. (Optional) Build and run with Docker: docker build -t icecast-mcp . docker run -i --rm icecast-mcp
6. If you use Claude Desktop, configure the MCP server entry to point to the Node command with the built index.js path, as shown in the usage examples.

Tips and considerations:

• The server communicates over stdio and adheres to the MCP specification; ensure your client is configured to interact via stdio channels.
• When using Docker, mount your Icecast configuration or pass in paths as needed to enable accurate analysis (e.g., /path/to/icecast/config).
• Common issues include mismatched build paths after npm install; always point to the correct build/index.js if you are using a prebuilt distribution.
• Environment variables can be used to customize logging or feature flags if the MCP server exposes them; consult the project docs for available options.
• For best results, provide realistic expectedListener counts when using analyze_icecast_config to obtain meaningful capacity recommendations.