PolarionMcpServers

Polarion MCP Servers provide API endpoints and streaming access to Polarion ALM data. The servers expose a set of MCP tools that can fetch and enumerate Work Items, sections, documents, and various Polarion metadata. You can connect to the server via stream/http or SSE transports, and use the REST API for programmatic access to Polarion projects. Typical use cases include retrieving work item content, listing documents by space or title, examining custom fields and work item types, and obtaining revision history for work items. Each configured Polarion project is exposed under its own URL alias, allowing you to target a specific project configuration while using the same MCP server infrastructure. The repository documents both a Console-based server for local workstations and a Streamable HTTP/SSE server for deployments.

Prerequisites:\n- Docker installed on the host (recommended) or a compatible runtime for your chosen MCP server variant.\n- Access to a Polarion instance and credentials for a configured project.\n- Optional: an environment to manage appsettings.json and credentials securely.\n\nInstallation steps (Docker, as recommended):\n1) Pull the Docker image:\nbash\ndocker pull peakflames/polarion-remote-mcp-server\n\n2) Create a configuration directory on the host and prepare appsettings.json per your Polarion setup (see the example in the repository README).\n3) Run the container, mapping the configuration and exposing the MCP endpoints:\nbash\ndocker run -d \\n --name polarion-mcp-server \\n -p 8080:8080 \\n -v /path/to/your/appsettings.json:/app/appsettings.json \\n peakflames/polarion-remote-mcp-server\n\n4) Verify the server is running and exposed at the configured URLs (e.g., http://host:8080/{ProjectUrlAlias} for streamable HTTP or SSE).\n5) Access REST API, UI and health endpoints as described in the README.\n\nNotes:\n- Do not run replicas of the server if you rely on shared Polarion sessions; sessions are not shared across replicas.\n- If you use environment variables, consider placing them in a .env file and referencing them in appsettings.json as needed.

Tips and common issues:\n- Ensure your Polarion credentials in SessionConfig are valid and have the necessary permissions for the target ProjectId.\n- For REST API access, you must supply the X-API-Key header with a valid API key per the documentation.\n- When using multiple Polarion projects, configure a unique ProjectUrlAlias for each in appsettings.json.\n- If you modify appsettings.json, restart the container to apply changes.\n- Use the Health endpoint to monitor server status: http://<server-host>:8080/api/health.\n- The configuration supports overriding base settings with appsettings.Development.json and optional .env values.