What transports does Polarion MCP Servers support?
The remote server (PolarionRemoteMcpServer) supports Streamable HTTP and SSE. The local console server (PolarionMcpServer) uses stdio.
@peakflames
基本情報
MCP Server for Polarion
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"PolarionMcpServers": {
"command": "docker",
"args": [
"pull",
"peakflames/polarion-remote-mcp-server"
]
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
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`.

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.
A search tool helps dev to solve the naming things problem.
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
PickFu MCP is a Model Context Protocol (MCP) server that connects AI assistants, developers, marketers, product managers, and AI agents to PickFu's consumer research platform. It enables users to create surveys, conduct
Hindsight: Agent Memory That Learns
コメント