Polarion MCP Servers

What is Polarion MCP Servers?

Polarion MCP Servers are Model Context Protocol (MCP) server implementations for integrating with Polarion Application Lifecycle Management (ALM). They provide tools to query work items, documents, spaces, and revisions from Polarion projects. The servers are intended for developers and teams using Polarion who want to connect AI assistants or other MCP-compatible clients to their Polarion data.

How to use Polarion MCP Servers?

Configure one or more Polarion project connections in appsettings.json using PolarionProjects, SessionConfig, and optional PolarionWorkItemTypes. Deploy the remote server via Docker or run the console server locally. MCP clients connect using SSE or Streamable HTTP URLs (e.g., http://<server-ip>:8080/{ProjectUrlAlias}/sse). A REST API is also available, authenticated via API key.

Key features of Polarion MCP Servers

• Provides 13+ MCP tools for work items and documents.
• Supports multiple Polarion projects via URL aliases.
• Offers Streamable HTTP, SSE, and stdio transports.
• Includes REST API alignment with Polarion’s official specification.
• API key authentication for REST endpoints (MCP endpoints unauthenticated).
• Health check endpoint (/api/health).
• Environment variable override for passwords (POLARION_PASSWORD).

Use cases of Polarion MCP Servers

• Query work item details (status, assignee, custom fields) from an AI assistant.
• Search for work items within a document by text criteria.
• Retrieve revision history and content for a given work item.
• List available custom fields or work item types in a Polarion project.

FAQ from Polarion MCP Servers

What transports does Polarion MCP Servers support?

The remote server (PolarionRemoteMcpServer) supports Streamable HTTP and SSE. The local console server (PolarionMcpServer) uses stdio.

How are passwords stored and secured?

Passwords can be placed in appsettings.json, but it is strongly recommended to use the POLARION_PASSWORD environment variable or a more secure method like User Secrets or Azure Key Vault.

What are the runtime requirements?

The server runs on .NET and is typically deployed via Docker on a Linux server. Polarion server credentials and a project ID are required.

Are there any known limitations?

Do not run replica instances of the server, as the Polarion session connection is not shared between replicas.

How does authentication work?

MCP endpoints (tools, health check, API documentation) do not require authentication. REST API endpoints require an API key passed via the X-API-Key header, configured in the ApiConsumers section of appsettings.json.