MCP server for QMetry Test Management for Jira (QTM4J) Open API.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-denis-platonov-qtm4j": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for QMetry Test Management for Jira (QTM4J) Open API.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
An open-source AI agent that brings the power of Gemini directly into your terminal.
MCP Security Weekly
Get CVE alerts and security updates for io.github.denis-platonov/qtm4j and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for QTM4J (QMetry Test Management for Jira) Open API at qtmcloud.qmetry.com/rest/api/latest.
Published package: @denis-platonov/qtm4j-mcp-server
MCP Registry name: io.github.denis-platonov/qtm4j
| Client | Status | Notes |
|---|---|---|
| Cursor | Supported | Configure with npx in ~/.cursor/mcp.json |
| JetBrains IDEs | Supported | Configure in AI Assistant MCP settings |
| VS Code | Supported | Configure in .vscode/mcp.json or user profile mcp.json |
| Antigravity | Supported | Configure in mcp_config.json via raw config |
| Tool | Description |
|---|---|
create_test_cycle | Create a new test cycle (run) |
search_test_case | Search for a test case by key (e.g. PE26-TC-2) |
search_test_cases | Search test cases with pagination and optional summary filters |
list_all_project_test_cases | Fetch and merge paginated test case results across a project |
create_test_case | Create a new test case, optionally placing it in folders |
list_cycle_test_cases | List all test cases in a cycle |
add_test_case_to_cycle | Add a test case to a cycle |
update_execution_status | Update execution result (Pass/Fail) |
close_test_cycle | Close a test cycle |
get_attachment_url | Get presigned URL for attachment upload |
add_test_case_steps | Add one or more steps to a test case version |
add_test_case_to_folders | Add a test case version to one or more folders |
create_test_case_folder | Create a test case folder in a project |
get_test_case | Fetch a test case by ID or key |
get_test_case_details | Fetch full details for a specific test case version |
get_test_case_steps | List or search steps on a test case version |
list_test_case_folders | List project test case folders with flat paths |
remove_test_case_from_folders | Remove a test case version from folders |
update_test_case_description | Update a test case version description |
update_test_case_step | Update an existing test step |
update_test_case_summary | Update a test case version summary |
The full set of tools (including search_test_cases with startAt, list_all_project_test_cases, folder and step helpers) is defined in src/tools.ts. After npm run build, run npm run list-tools to print every registered tool name — use this to confirm Cursor is using this build (you should see list_all_project_test_cases).
npx @denis-platonov/qtm4j-mcp-server may be an older npm release. To guarantee tools such as list_all_project_test_cases and correct startAt handling:
npm install && npm run build.cursor-mcp.example.json into your user Cursor config ~/.cursor/mcp.json (Windows: %USERPROFILE%\.cursor\mcp.json). Adjust the args path to your absolute dist/index.js.npm run list-tools and confirm the tool count matches expectations.If you use Cursor’s workspace mcps/<server>/tools/*.json hints for the agent, keep those JSON schemas in sync with src/tools.ts (same parameter names as the Zod definitions). Rebuild and restart MCP after changing tools.