No user-submitted related servers found.
Scored across 293 tools
The set has many near-neighbor families—single vs. batch, project vs. global, relationship vs. linked-item, and several page/document scope variants. The descriptions do give explicit selection guidance, but with 293 tools an agent still faces substantial overlap and selection risk.
Most resource tools follow a predictable camelCase verb-prefix pattern such as getWorkItem, patchTestRun, and postDocumentParts. However, several operational tools use snake_case (get_document_outline, search_work_items, run_job_and_wait), creating a mixed convention across the set.
293 tools is far beyond an appropriate surface for a single MCP server and creates severe discoverability and selection burden. While Polarion is a broad ALM system, this many narrowly separated tools is an extreme mismatch for practical agent use.
The surface is extremely comprehensive, covering projects, work items, documents, pages, test runs/records/steps, attachments, comments, approvals, relationships, licensing, jobs, metadata, and AI operations. CRUD and lifecycle operations are broadly represented with few obvious dead ends.