Polarion MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 639 installs a week from npm. Last commit 6 Nov 2026.
Polarion ALM MCP server for requirements, LiveDocs, work items, traceability and test management.
What the code does
We read the source, 21 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
version = subprocess.check_output([node, "--version"], text=True).strip()
.filter(([, pdf]) => fs.existsSync(path.join(SDK_DIR, pdf.file)))
const zodSchema = eval(jsonSchemaToZod(oneOfAsAnyOf(nullableAttributes(makeNestedObjectsPermissive(jsonSchema)))));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add polarion-mcp -e 'API_BASE_URL=<API_BASE_URL>' -e 'BEARER_TOKEN=<BEARER_TOKEN>' -- npx -y polarion-mcp{
"mcpServers": {
"polarion-mcp": {
"command": "npx",
"args": [
"-y",
"polarion-mcp"
],
"env": {
"API_BASE_URL": "<API_BASE_URL>",
"BEARER_TOKEN": "<BEARER_TOKEN>"
}
}
}
}[mcp_servers.polarion-mcp]
command = "npx"
args = ["-y", "polarion-mcp"]
env = { API_BASE_URL = "<API_BASE_URL>", BEARER_TOKEN = "<BEARER_TOKEN>" }{
"mcpServers": {
"polarion-mcp": {
"command": "npx",
"args": [
"-y",
"polarion-mcp"
],
"env": {
"API_BASE_URL": "<API_BASE_URL>",
"BEARER_TOKEN": "<BEARER_TOKEN>"
}
}
}
}{
"servers": {
"polarion-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"polarion-mcp"
],
"env": {
"API_BASE_URL": "<API_BASE_URL>",
"BEARER_TOKEN": "<BEARER_TOKEN>"
}
}
}
}Put your own values in place of
<API_BASE_URL> (Base URL for the Polarion REST API, e.g. https://your-polarion-server.com/polarion/rest/v1), <BEARER_TOKEN> (Personal Access Token (PAT) for authenticating with the Polarion REST API).
The author’s registry entry marks them as required.
Alternatives to Polarion MCP
same job, measured the same wayManage functional-safety requirements and lifecycle traceability.
Spec-driven development for AI coding agents: live requirements, stories and traceability over MCP
MCP server for Runframe incident management covering incidents, on-call, postmortems, and more.
MCP server for Langfuse LLM observability — trace and observation analysis.
Audit trail and traceability for AI agents. MCP gate: evaluate, ingest, request approval.
Kibi requirements, traceability, and proof MCP. Install as a project dev dependency.
MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.
MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.
Polarion MCP — questions
Answers built from our own checks of this server.