
QTM4J
Let your coding agent read and update QMetry test cases, cycles, and results in Jira without leaving the chat.
Overview
QTM4J MCP is a MCP server for the Ship phase that connects coding agents to QMetry Test Management for Jira via the Open API.
What is this MCP server?
- Stdio MCP server (@denis-platonov/qtm4j-mcp-server) wired to QTM4J Open API v1.1.0
- Configurable base URL, default project ID, and API-key auth via environment variables
- Optional NODE_TLS_REJECT_UNAUTHORIZED for self-signed TLS in on-prem or lab setups
- Fits teams already on QMetry + Jira who want agent-driven test lookups and updates
- Server version 1.1.0
- Default API base: https://qtmcloud.qmetry.com/rest/api/latest
- Transport: stdio via @denis-platonov/qtm4j-mcp-server
What problem does it solve?
Switching between your IDE and QMetry/Jira to check tests and update cycles breaks flow when you are trying to ship on a deadline.
Who is it for?
Indie teams on Jira + QMetry who want agent-assisted test management during release prep.
Skip if: Builders without QMetry/Jira or anyone who only needs local unit tests with no ALM integration.
What do I get? / Deliverables
After you register the server, your agent can query and act on QTM4J test data using your API key and default project settings.
- Agent-callable tools backed by QTM4J Open API
- Project-scoped test management queries and updates from the IDE
Recommended MCP Servers
Journey fit
How it compares
Jira test-management API bridge, not a generic Playwright or pytest runner skill.
Common Questions / FAQ
Who is QTM4J MCP for?
Solo builders and small teams using QMetry Test Management for Jira who want their AI coding agent to access test data through MCP.
When should I use QTM4J MCP?
Use it in the ship/testing phase when you need agents to read or update QTM4J entities while you implement fixes or prepare a release.
How do I add QTM4J MCP to my agent?
Install @denis-platonov/qtm4j-mcp-server, set QTM4J_API_KEY (and optional QTM4J_BASE_URL, QTM4J_PROJECT_ID), then add the stdio MCP entry in Claude Code, Cursor, or another MCP-capable client.