MCP server for QMetry Test Management for Jira (QTM4J): test cases, cycles, executions, plans.
An MCP server with 87 tools for QMetry Test Management for Jira (QTM4J). Search and manage test cases, cycles, executions, plans, folders, comments, defects, automation rules, and project metadata from Claude Desktop, Claude Code, VS Code Copilot, Cursor, or any MCP-compatible client. You need a QMetry API key (QMetry → API Keys) and Node.js 18+. Edit your config file and restart Claude: Create…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 6 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
An MCP server with 87 tools for QMetry Test Management for Jira (QTM4J). Search and manage test cases, cycles, executions, plans, folders, comments, defects, automation rules, and project metadata from Claude Desktop, Claude Code, VS Code Copilot, Cursor, or any MCP-compatible client. You need a QMetry API key (QMetry → API Keys) and Node.js 18+. Edit your config file and restart Claude: Create in your workspace: Switch Copilot Chat to Agent mode and the tools appear automatically. Add to (or…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.