MCP Server Polarion logo

MCP Server Polarion

by devemberx

Connects AI agents to Polarion ALM for searching, reading, validating, and updating documents, work items, tests, links, comments, and attachments.

Install MCP Server Polarion

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "devemberx-mcp-server-polarion": {
      "command": "uvx",
      "args": [
        "mcp-server-polarion"
      ],
      "env": {
        "POLARION_URL": "YOUR_VALUE_HERE",
        "POLARION_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

devemberx/mcp-server-polarion connects MCP-compatible AI clients to Polarion ALM through read and write tools for projects, documents, work items, test runs, links, comments, and attachments. It can render documents and work items as Markdown, search with Lucene or SQL, inspect traceability, and manage document structure. Write operations support dry runs with validation of fields, enum values, and link targets before changes are committed. Reach for it when an agent needs to inspect or update Polarion data, and when the Polarion instance runs version 2506 or newer.

Use cases

  • Search Polarion work items with Lucene or SQL
  • Render requirements documents as Markdown
  • Inspect incoming and outgoing traceability links
  • Create and update work items with dry-run validation
  • Reorganize document structure and review comments

Key features

  • Polarion ALM project, document, work-item, and test-run access
  • Markdown rendering for documents and work items
  • Lucene and SQL work-item search
  • Traceability, comment, enum, and attachment inspection
  • Dry-run writes with field, enum, and link validation
  • Document creation, copying, updating, and reorganization

Tools46

What MCP Server Polarion lets your agent do. Expand a tool for its parameters.

Self-reported~849 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

19/19 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · mcp-server-polarion (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars17Stargazers on the source repository.
Last commit4d agoMost recent push to the default branch.
Tools exposed46Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server Polarion works

What devemberx/mcp-server-polarion does

devemberx/mcp-server-polarion exposes Polarion ALM through the Model Context Protocol. It covers project and document discovery, work-item lookup, test-run and test-record inspection, traceability links, comments, attachments, and selected write operations.

For reading, the server can return document metadata or render a complete document as Markdown. It can expose a document's structural parts together with embedded work-item metadata, return work-item bodies as raw HTML or Markdown, and inspect incoming or outgoing links. Search tools accept Lucene queries, while work-item searches can also use SQL. Recipe tools provide SQL examples and Polarion HTML templates for advanced queries or raw-body edits.

Write operations include creating and updating work items and documents, copying documents, and changing document structure by moving work items into or out of documents. The available interface also covers test runs and records, links, attachments, and comments as described by the repository tool listing.

How it works

devemberx/mcp-server-polarion runs as an MCP process and communicates with a configured Polarion instance. List operations use page_size and page_number pagination, with page sizes from 1 through 100. Document and work-item content can be requested in the representation suited to the task: rendered Markdown for agent-friendly reading or raw HTML where Polarion formatting needs to be preserved or edited.

Before a write reaches Polarion, the server can run it with dry_run. Its pre-write checks validate fields, enum values, and link targets. Enum lookup tools help an agent resolve valid identifiers before changing document or work-item fields.

Setup and configuration

The server requires Polarion 2506 or newer and uv. A typical launch uses uvx mcp-server-polarion with POLARION_URL set to the Polarion base URL and POLARION_TOKEN set to a personal access token.

Authentication and the target Polarion endpoint therefore depend on the URL and token settings documented above.

Tools and capabilities

  • Discover accessible projects, project documents, work items, and test runs.
  • Search work items with Lucene or SQL and retrieve SQL query recipes.
  • Read documents and work items as Markdown or raw HTML.
  • Inspect document structure, traceability links, comments, enum options, and attachments.
  • Examine test-run details, execution records, revisions, comments, and image attachments.
  • Create or update work items and documents, including metadata, body content, and workflow status.
  • Copy documents and reorganize work items within document structure.
  • Use dry-run validation before supported writes.

Limitations and notes

The Polarion version requirement is 2506 or later. The server operates on data available to the configured Polarion account, so accessible projects and writable resources depend on that account's permissions. Raw HTML editing requires preserving Polarion's expected formatting, for which the server supplies HTML recipes.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server Polarion

devemberx/mcp-server-polarion is an MCP server that connects AI clients to Polarion ALM. Its main tools list and search projects, documents, work items, test runs, links, comments, and attachments, read content as Markdown or HTML, and create or update documents and work items with dry-run validation.

Install it with `uvx mcp-server-polarion` after installing `uv`. Configure `POLARION_URL` with the Polarion address and `POLARION_TOKEN` with a personal access token. The connected Polarion instance must run version 2506 or newer.

Configure the MCP server with the Polarion URL and personal access token, then launch it through `uvx mcp-server-polarion`.

Yes, supported write tools accept `dry_run` and perform pre-write checks. The documented checks cover fields, enum values, and link targets before changes are committed to Polarion.

Yes, its document-reading tools can render a document end-to-end as Markdown. Separate tools can return document metadata, raw body HTML, structural parts, embedded work-item metadata, and attachments.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server Polarion AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/devemberx-mcp-server-polarion?style=directory)](https://allmcps.com/mcp/devemberx-mcp-server-polarion)
HTML Embed
<a href="https://allmcps.com/mcp/devemberx-mcp-server-polarion"><img src="https://allmcps.com/api/badge/devemberx-mcp-server-polarion?style=directory" alt="MCP Server Polarion on AllMCPs" /></a>