What transports does Polarion MCP Servers support?
The remote server (PolarionRemoteMcpServer) supports Streamable HTTP and SSE. The local console server (PolarionMcpServer) uses stdio.
@peakflames
Basic information
MCP Server for Polarion
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"PolarionMcpServers": {
"command": "docker",
"args": [
"pull",
"peakflames/polarion-remote-mcp-server"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
/api/health).POLARION_PASSWORD).The remote server (PolarionRemoteMcpServer) supports Streamable HTTP and SSE. The local console server (PolarionMcpServer) uses stdio.
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.
The server runs on .NET and is typically deployed via Docker on a Linux server. Polarion server credentials and a project ID are required.
Do not run replica instances of the server, as the Polarion session connection is not shared between replicas.
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`.
MCP Toolbox for Databases is an open source MCP server for databases.
This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,
A curated list of references for MLOps
Painless E2E Automation for Mobile and Web
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
Comments