pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for mcp-server-polarion

Pod holds 17 of 20 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to mcp-server-polarion.

Most discussed

tools(test-records): evaluate attachment delete tool

Origin

PR #222, review round 1 (pipeline follow-up export)

Finding

Test record attachment DELETE returned 204 on the live testdrive project (2026-07-21) — unlike document attachments (405, REST-irreversible). The server ships no delete tools anywhere today, so uploads to test records are currently irreversible through this MCP server even though the API allows deletion. The create tool's docstring deliberately makes no irreversibility claim.

Suggested fix

Decide whether a delete

Read the thread · 2026-07-21 · closed · 2 comments

guard(comments): validate attachment refs in comment bodies

Origin

PR feat/attachment-ref-guard — user-decided scope exclusion at spec time.

Finding

Document and work item comment bodies accept HTML that can carry attachment:/workitemimg: refs. Comment write tools apply no attachment-ref validation, so dangling refs persist there exactly as they did in document/work-item bodies before the guard landed. Whether either scheme even resolves when rendered inside a comment is unverified.

Suggested fix

Live-probe scheme resolution in comme

Read the thread · 2026-07-20 · closed · 2 comments

guard(documents): probe copy_document attachment refs

Origin

PR feat/attachment-ref-guard — spec UNVERIFIED item, deferred out of scope.

Finding

copy_document copies body HTML containing attachment:{id} refs, but whether Polarion copies the attachments with the document (refs keep resolving in the target) or leaves the copied body dangling is unverified. If attachments are not copied, every copied body image is a silent broken ref — same ghost class the attachment-ref guard now blocks on update paths.

Suggested fix

Live-probe o

Read the thread · 2026-07-20 · closed · 2 comments

Recommendation to use polarion-rest-api-client

Problem

Hi devemberx,

I am deciding on using or developing an MCP server for Polarion and found this repository. It is impressive that evals and guardrails are developed as part of the MCP server!

devemberx/mcp-server-polarion currently implements its own httpx-based PolarionClient for interacting with the Polarion REST API instead of reusing the existing dbinfrago/polarion-rest-api-client.

This creates duplicated client-layer

Read the thread · 2026-07-09 · closed · external user · 2 comments

evals(harness): doc attachment/comment routes ignore page params

Origin

PR #240 review (merge round).

Finding

evals/harness/fake_polarion.py doc attachment route (and document comment route) ignore page[size]/page[number] entirely — full collection served on every page. Live rule: overshoot of non-empty collection = empty data + meta.totalCount (doc overshoot-only rule); fake can never reproduce that shape, and a model requesting page 2 gets page 1 again. Fidelity gap only — nothing consumes it today; out of #227 scope (WI/testrecord routes

Read the thread · 2026-07-29 · closed · 1 comment

refactor(tools): reuse test_record_path in record attachment create

Origin

PR #226, review round 2 (FOLLOW-UPS section).

Finding

src/mcp_server_polarion/tools/attachments.py:881 — create_test_record_attachments (landed via #222) hand-builds the .../testrecords/{tc_project}/{tc_id}/{iteration} path inline while PR #226 extracted the shared test_record_path helper now used by get_test_record and list_test_record_attachments. Byte-identical output today, no bug — drift risk only.

Suggested fix

`path = test_record_path(project_id, test_run

Read the thread · 2026-07-21 · closed · 1 comment

evals(harness): match live totalCount omission on workitem attachments

Origin

PR feat/list-work-item-attachments — pipeline review round 1 LOW finding.

Finding

fake_polarion workitem-attachments route always emits meta.totalCount (single-item seed -> totalCount: 1, empty collection -> 0), while live testdrive (verified 2026-07-19, MCPT-556) omits totalCount for single-page and empty collections and serves it on every page only when the collection spans multiple pages. test_workitem_attachments_meta_total_count_always_present pins the divergent

Read the thread · 2026-07-19 · closed · 1 comment

evals(harness): model meta.totalCount omission in fake route

Origin

PR #193, review round 1

Finding

evals/harness/fake_polarion.py:579 -- LOW. Two related problems.

  1. The spec and the CLAUDE.md-adjacent notes state that meta.totalCount is emitted only when a further page exists. The live page_number=2 run in PR #193 returned total_count=1 on an out-of-range page, so meta is present there too. The rule as written is not the whole story.
  2. The fake attachments route always emits meta, so the harness never reproduces the no-meta s

Read the thread · 2026-07-18 · closed · 1 comment

Most recent

follow-up: renderingLayouts order re-points document part layout index

Origin

PR #252, live probing of document parts on a test instance

Finding

A document part of type workitem carries a layout attribute holding an integer:

{"id": "workitem_XXXX-758", "type": "workitem", "level": 0, "layout": 0}

The value indexes into the document's renderingLayouts array — the document probed had a single entry, and its work item part pointed at index 0.

update_document(rendering_layout_types=[...]) PATCHes renderingLayouts as a whole array (Po

Read the thread · 2026-08-12 · open · 0 comments

follow-up: mirror portal label/properties on rendering layouts

Origin

PR #252, live probing of portal-created documents

Finding

src/mcp_server_polarion/tools/documents.py:100 — _rendering_layouts_attribute writes {"type": <id>, "layouter": "paragraph"} and nothing else. Documents created through the Polarion portal carry two more members on every layout entry:

{"type": "testcase", "label": "Test Case", "layouter": "paragraph",
 "properties": [{"key": "fieldsAtStart", "value": "id"},
                {"key": "fieldsAtEnd", "value": "

[Read the thread](https://github.com/devemberx/mcp-server-polarion/issues/253) · 2026-08-12 · closed · 0 comments

### docs(tools): note heading WI comments hidden in portal

### Origin

Spun off #225 during PR #239 review. The #225 live probe (2026-07-21) found the portal hides not only the Attachments section but also comments on heading-type work items; #239 documented only the attachment side on `create_work_item_attachments`.

### Finding

Posting comments to a heading-type work item succeeds over REST and the API round-trip works, but the portal hides the comments section on heading-type items — such comments are reachable only through the API, same pattern as 

[Read the thread](https://github.com/devemberx/mcp-server-polarion/issues/242) · 2026-07-29 · open · 0 comments

### evals(harness): emit totalCount on overshoot in attachment routes

### Origin

PR #226, review round 1 (FOLLOW-UPS section).

### Finding

evals/harness/fake_polarion.py:598 — testrecord + work-item attachment routes emit `meta.totalCount` only when the collection spans more than one page. Live rule also serves it on overshoot of a non-empty collection (page past end, empty `data`). Never consumed by tools (`compute_has_more` works without), so no test is falsely green — fidelity gap only.

### Suggested fix

Add `or (page_number > 1 and data == [] and resource

[Read the thread](https://github.com/devemberx/mcp-server-polarion/issues/227) · 2026-07-21 · closed · 0 comments

### docs(tools): note heading-type work item attachments hidden in portal

### Origin

Live probe for #214 (2026-07-21) — attachment was planted on a heading-type work item and turned out to be invisible in the portal.

### Finding

Uploading attachments to a heading-type work item succeeds over REST, and the full API round-trip works (upload 201, list, content download). The portal, however, hides the Attachments section (and comments) on heading-type items, so portal users cannot see or manage such uploads — effectively API-only data.

### Suggested fix

No hard guar

[Read the thread](https://github.com/devemberx/mcp-server-polarion/issues/225) · 2026-07-21 · closed · 0 comments

### tools(test-records): add attachment list/get-content tools

### Origin

PR #222, review round 1 (pipeline follow-up export)

### Finding

Test record attachments are create-only on the MCP surface. Collection GET with a fields param was verified working on the live testdrive project (2026-07-21), so list and content-read tools are implementable now. The create tool's duplicate-name prevention hint currently points at list_test_records because no attachment list tool exists — an honest but indirect verification path.

### Suggested fix

Add list_test_reco

[Read the thread](https://github.com/devemberx/mcp-server-polarion/issues/223) · 2026-07-21 · closed · 0 comments

### hooks: fix validate_pr body extraction on inner double quotes

### Origin

PR #210 creation, 2026-07-21 — first `gh pr create` attempt was blocked with a false "The ## Changes section must contain exactly 2" error although the body had exactly two compliant bullets.

### Finding

`.claude/hooks/validate_pr.py:131` (`extract_body`) re-parses the Bash command string with `shlex.split` and takes the token after `--body`. With the common `--body "$(cat <<'EOF' ... EOF)"` form, shlex understands neither command substitution nor heredocs — the first double quote 

[Read the thread](https://github.com/devemberx/mcp-server-polarion/issues/211) · 2026-07-20 · closed · 0 comments

### tools(shared): guard created-id count mismatch on create echoes

### Origin

PR for create_document_attachments — review round 2 FOLLOW-UP (out of spec scope, cross-cutting).

### Finding

Create tools parse 201 echoes via `extract_created_short_ids` and only guard the empty case (`if not ids`). A 201 body echoing fewer entries than submitted would return a silently-short id list. Applies to `create_document_attachments` and the sibling `create_document_comments` (identical shape); non-actionable today because verified server behavior is batch-atomic (all-or-

[Read the thread](https://github.com/devemberx/mcp-server-polarion/issues/208) · 2026-07-20 · closed · 0 comments

### evals(cases): pin arg-threading for get_document_attachment_content

### Origin

PR feat/doc-attachment-content — pipeline review round 1 FOLLOW-UPS (get_document_attachment_content).

### Finding

No eval asserts the spec'd call args for `get_document_attachment_content` — the trigger case checks routing only, matching all 25 sibling trigger cases. Arg-threading (project_id/space_id/document_name/attachment_id) is unpinned at eval level.

### Suggested fix

Add an efficiency/orchestration case with `match={project_id, space_id, document_name, attachment_id}` on 

[Read the thread](https://github.com/devemberx/mcp-server-polarion/issues/202) · 2026-07-19 · closed · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/devemberx/mcp-server-polarion/issues).