MCP Tools DirectoryAbout this integration
MCP server for QMetry Test Management for Jira (QTM4J): test cases, cycles, executions, plans.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- qtm4j-mcp-server
- Last compatibility test
- Not independently tested
Connect your agent
qtm4j-mcp-serverPublisher documentation describes a local Node.js stdio server that sends a required QMetry API key on requests. The tool set includes mutating and destructive operations as well as reads. Documentation was reviewed; the package and QMetry service were not executed or independently security-audited.
Capabilities: Search and manage QTM4J test cases, cycles, executions, and plans, Manage folders, comments, defects, and automation rules, Read QTM4J project metadata
Connected profiles
Additional details
io.github.salehrifai42/qtm4j-mcp-server
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17QTM4J_API_KEY
Source ↗ · Checked 2026-09-17qtm4j-mcp-server
Source ↗ · Checked 2026-09-190.2.2
Source ↗ · Checked 2026-09-19Publisher client configuration explicitly declares a local stdio server launched with npx. This is documented behavior, not a runtime test.
Source ↗ · Checked 2026-09-19QTM4J_API_KEY is required and sent as the apiKey header; QTM4J_REGION optionally selects the documented US or AU service origin.
Source ↗ · Checked 2026-09-19Configure an MCP client with type stdio, command npx, package qtm4j-mcp-server@^0.1, and the required QTM4J_API_KEY environment variable.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19