@gojitsu/qmetry-mcp

MCP (Model Context Protocol) server for QMetry Cloud (qtmcloud.qmetry.com). Allows Claude Code to interact with QMetry test cases, test cycles, test plans, folders, executions, and more via natural language.

Requirements

• Node.js >= 18
• QMetry Cloud project API key
• Jira personal access token

Installation

Add to your Claude Code .mcp.json:

{
  "mcpServers": {
    "qmetry": {
      "command": "npx",
      "args": ["-y", "@gojitsu/qmetry-mcp"],
      "env": {
        "QMETRY_API_KEY": "your-qmetry-project-api-key",
        "JIRA_API_TOKEN": "your-jira-personal-access-token",
        "JIRA_EMAIL": "[email protected]",
        "QMETRY_AUTOMATION_TOKEN": "your-qmetry-automation-token"
      }
    }
  }
}

Credentials

| Env var | Required | Where to get it | |---|---|---| | QMETRY_API_KEY | Yes | QMetry → Project Settings → API Keys | | JIRA_API_TOKEN | Yes | https://id.atlassian.com/manage-profile/security/api-tokens | | JIRA_EMAIL | Yes | Your Jira account email | | QMETRY_AUTOMATION_TOKEN | Only for import_result | QMetry → Project Settings → Automation |

Run the authentication_info tool in Claude Code to see these instructions inline.

Available Tools

Project

| Tool | Description | |---|---| | proj_list | List QMetry-enabled Jira projects | | proj_settings | Get project settings | | proj_builds | Get builds | | proj_environments | Get environments | | proj_components | Get components | | proj_labels | Get labels | | proj_tc_statuses | Get test case statuses | | proj_cycle_statuses | Get test cycle statuses | | proj_plan_statuses | Get test plan statuses | | proj_execution_results | Get execution result types (Pass/Fail/Blocked…) | | proj_priorities | Get priorities |

Test Case Folders

| Tool | Description | |---|---| | tc_folders | List full folder tree | | tc_folder_search | Search folders by name | | tc_folder_create | Create folder | | tc_folder_update | Rename folder | | tc_folder_delete | Delete folder | | tc_folder_move | Move folder |

Test Cases

| Tool | Description | |---|---| | tc_search | Search test cases | | tc_get | Get test case details | | tc_create | Create test case | | tc_update | Update test case | | tc_delete | Delete test case | | tc_clone | Clone test case | | tc_archive / tc_unarchive | Archive/unarchive | | tc_move | Move to folder | | tc_bulk_update | Bulk update | | tc_bulk_delete | Bulk delete | | tc_bulk_archive / tc_bulk_unarchive | Bulk archive/unarchive | | tc_add_version / tc_delete_version | Manage versions |

Test Steps

| Tool | Description | |---|---| | tc_steps | Get steps | | tc_create_steps | Create steps | | tc_update_steps | Update steps | | tc_delete_steps | Delete steps |

Test Case — Links & History

| Tool | Description | |---|---| | tc_requirements | Get linked requirements | | tc_link_requirement / tc_unlink_requirement | Link/unlink requirements | | tc_linked_cycles | Get linked cycles | | tc_executions | Get execution history | | tc_comments | Get comments | | tc_add_comment / tc_update_comment / tc_delete_comment | Manage comments |

Test Cycle Folders

| Tool | Description | |---|---| | cycle_folders | List full folder tree | | cycle_folder_create / cycle_folder_update / cycle_folder_delete / cycle_folder_move | Manage folders |

Test Cycles

| Tool | Description | |---|---| | cycle_search | Search test cycles | | cycle_get | Get cycle details | | cycle_create | Create cycle | | cycle_update | Update cycle | | cycle_delete | Delete cycle | | cycle_clone | Clone cycle | | cycle_archive / cycle_unarchive | Archive/unarchive |

Test Cycle — Executions

| Tool | Description | |---|---| | cycle_testcases | List test cases in cycle | | cycle_link_testcases / cycle_unlink_testcases | Link/unlink test cases | | cycle_tc_folders | Get folder structure within cycle | | cycle_bulk_update_executions | Bulk update execution results | | cycle_update_execution | Update single execution | | cycle_delete_execution | Delete execution | | cycle_execution_steps | Get step-level execution results | | cycle_execution_defects / cycle_link_execution_defects | Manage execution defects |

Test Cycle — Links & Comments

| Tool | Description | |---|---| | cycle_requirements / cycle_link_requirement | Linked requirements | | cycle_defects | Linked defects | | cycle_comments / cycle_add_comment / cycle_update_comment / cycle_delete_comment | Comments |

Test Plan Folders

| Tool | Description | |---|---| | plan_folders | List full folder tree | | plan_folder_create / plan_folder_update / plan_folder_delete / plan_folder_move | Manage folders |

Test Plans

| Tool | Description | |---|---| | plan_search | Search test plans | | plan_get | Get plan details |

Requirements

| Tool | Description | |---|---| | req_linked_testcases | Get test cases linked to a requirement | | req_link_testcases / req_unlink_testcases | Link/unlink test cases |

Utilities

| Tool | Description | |---|---| | authentication_info | Show where to obtain API credentials | | task_get | Get background task status | | import_result | Import automation test results (CI/CD) |

Publishing

# Bump version first
npm version patch   # or minor / major

# Build + publish to npmjs.com
npm publish

Requires JITSU_NPM_API_TOKEN env var set (npmjs.com automation token).