Skip to main content
Glama
Jira QMetry MCP Server

Jira QMetry MCP Server

by albertor03

Jira QMetry MCP Server

🌐 Language: English | Español

MCP (Model Context Protocol) server to interact with the QMetry for Jira API. Allows large language models (LLMs) and client applications to access QMetry test management functionalities through well-defined tools.

πŸ“‹ Project Description

This project implements a server based on the Model Context Protocol (MCP) that provides a complete interface to manage test cases, test cycles, test plans, and their associated configurations in QMetry. The server is built with TypeScript and uses the official MCP SDK.

Key Features

  • βœ… Complete Test Case Management: Create, search, edit, move, and copy test cases

  • βœ… Test Steps Management: Create, update, delete, and retrieve test steps

  • βœ… Folder Organization: Manage folders for test cases, test cycles, and test plans

  • βœ… Status Configuration: Manage custom statuses for test cases, test cycles, and test plans

  • βœ… Priority Management: Full CRUD of priorities with custom colors

  • βœ… Label System: Create, update, and delete labels for organization

  • βœ… Linked Requirements: Link and unlink requirements (Jira issues) with test cases

  • βœ… Custom Fields: Support for custom fields in test cases, test cycles, test plans, and test executions

  • βœ… Robust Architecture: Logging system, error handling, and schema validation with Zod

Related MCP server: Zephyr Scale MCP Server

πŸ—οΈ Project Structure

jira-qmetry-mcp/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ api/                          # QMetry API call functions
β”‚   β”‚   β”œβ”€β”€ qmetry-projects.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-case.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-case-folders.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-case-status.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-cycle-folders.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-cycle-status.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-plan-folders.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-plan-status.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-steps.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-priorities.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-labels.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-components.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-linked-requirements.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-custom-fields.ts
β”‚   β”‚   └── qmetry-test-cycle-executions.ts
β”‚   β”œβ”€β”€ interfaces/                   # TypeScript type definitions
β”‚   β”‚   β”œβ”€β”€ qmetry-projects.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-cases.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-case-folders.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-cycle-folders.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-plan-folders.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-steps.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-priorities.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-labels.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-status.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-linked-requirements.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-custom-fields.ts
β”‚   β”‚   β”œβ”€β”€ qmetry-test-cycle-executions.ts
β”‚   β”‚   β”œβ”€β”€ toolDefinition.ts
β”‚   β”‚   └── index.ts
β”‚   β”œβ”€β”€ tools/                        # MCP tool definitions
β”‚   β”‚   β”œβ”€β”€ project-tools.ts
β”‚   β”‚   β”œβ”€β”€ test-cases-tools.ts
β”‚   β”‚   β”œβ”€β”€ test-case-folder-tools.ts
β”‚   β”‚   β”œβ”€β”€ test-cases-status-tools.ts
β”‚   β”‚   β”œβ”€β”€ test-cycle-folder-tools.ts
β”‚   β”‚   β”œβ”€β”€ test-cycle-status-tools.ts
β”‚   β”‚   β”œβ”€β”€ test-plan-folder-tools.ts
β”‚   β”‚   β”œβ”€β”€ test-plan-status-tools.ts
β”‚   β”‚   β”œβ”€β”€ test-step-tools.ts
β”‚   β”‚   β”œβ”€β”€ priority-tools.ts
β”‚   β”‚   β”œβ”€β”€ label-tools.ts
β”‚   β”‚   β”œβ”€β”€ linked-requirements-tools.ts
β”‚   β”‚   β”œβ”€β”€ custom-field-tools.ts
β”‚   β”‚   └── test-cycle-execution-tools.ts
β”‚   β”œβ”€β”€ utils/                        # Utilities and helpers
β”‚   β”‚   β”œβ”€β”€ logger.ts
β”‚   β”‚   β”œβ”€β”€ object.utils.ts
β”‚   β”‚   └── index.ts
β”‚   β”œβ”€β”€ main.ts                       # MCP server entry point (stdio)
β”‚   β”œβ”€β”€ http-server.ts                # HTTP server with Streamable HTTP transport
β”‚   └── config.json                   # API configuration
β”œβ”€β”€ package.json
β”œβ”€β”€ tsconfig.json
β”œβ”€β”€ eslint.config.js
β”œβ”€β”€ LICENSE
β”œβ”€β”€ NOTICE
β”œβ”€β”€ CONTRIBUTING.md
└── README.md

πŸ”§ Setup

1. Install Dependencies

pnpm install

2. Environment Variable

Configure your QMetry API key:

export QMETRY_API_KEY="your-api-key-here"

πŸ’‘ Note: The API key is generated from the Jira interface: QMetry > Configuration > Open API > Generate

3. Run the Server

Option A: Local Development

pnpm start

To use the MCP inspector:

pnpm run:inspector

Option B: Docker Deployment

The project includes a simple Dockerfile that works with any platform (Railway, Dokploy, Render, etc.).

Using Docker directly:

# Build the image
docker build -t jira-qmetry-mcp .

# Run the container (port is configurable)
docker run -d \
  --name jira-qmetry-mcp \
  -p 3000:3000 \
  -e PORT=3000 \
  -e QMETRY_API_KEY="your-api-key-here" \
  jira-qmetry-mcp

# View logs
docker logs -f jira-qmetry-mcp

Using Docker Compose (for local development):

# Create .env file with your configuration
cp .env.example .env
# Edit .env and add your QMETRY_API_KEY

# Start the service
docker-compose up -d

# View logs
docker-compose logs -f

Deploying to Railway/Dokploy/Render:

These platforms will automatically detect the Dockerfile. Just set the environment variables:

  • PORT - Will be set automatically by the platform (or use 3000)

  • QMETRY_API_KEY - Your QMetry API key (required)

  • NODE_ENV - Set to production (optional, defaults to production)

πŸ› οΈ Available Tools

πŸ“ Projects

Tool: list-qmetry-projects

  • Get projects: List all QMetry-enabled projects with filtering and pagination


πŸ“ Test Cases

Tools: get-qmetry-test-cases, create-qmetry-test-case, move-qmetry-test-case, copy-qmetry-test-case, update-qmetry-test-case

  • Get: Search test cases with advanced filters (assignee, status, labels, etc.)

  • Create: Create new test cases with steps, descriptions, and configurations

  • Move: Move test cases between folders

  • Copy: Copy test cases to different locations

  • Update: Update test case information


πŸ”„ Test Case Versions

Tools: get-test-case-version-details, add-test-case-version, delete-test-case-version, get-test-case-versions-list

  • Get version details: Retrieve specific version information

  • Add version: Create new version from existing version

  • Delete version: Remove a specific version

  • Get versions list: View all versions of a test case


πŸ“¦ Test Case Lifecycle

Tools: archive-qmetry-test-case, unarchive-qmetry-test-case, clone-qmetry-test-case, get-test-case-test-cycles

  • Archive: Archive a test case

  • Unarchive: Restore archived test case

  • Clone: Duplicate test case with options

  • Get linked cycles: View test cycles linked to a test case


πŸ“‚ Test Case Folders

Tools: get-qmetry-test-case-folders, create-qmetry-test-case-folder, edit-qmetry-test-case-folder, copy-qmetry-test-case-folder, move-qmetry-test-case-folder, search-qmetry-test-case-folders

  • Get: List all test case folders in a project

  • Create: Create new folders with parent-child hierarchy

  • Edit: Modify name and description of existing folders

  • Copy: Copy folders to new locations

  • Move: Move folders to different parent folders

  • Search: Search folders by name (strict or relative mode)


🎯 Test Case Status

Tools: get-qmetry-test-case-statuses, create-qmetry-test-case-status, update-qmetry-test-case-status, delete-qmetry-test-case-status, get-test-case-status-ref-count

  • Get: List all test case statuses (active/archived)

  • Create: Create custom statuses with colors

  • Update: Modify existing statuses

  • Delete: Remove statuses from project

  • Reference count: Check how many cases use a specific status


πŸ”„ Test Cycles

Tools: search-qmetry-test-cycles, create-qmetry-test-cycle, update-qmetry-test-cycle, move-qmetry-test-cycle, link-test-case-to-test-cycle, unlink-test-case-from-test-cycle, get-test-cycle-test-plans, link-requirements-to-test-cycle, unlink-requirements-from-test-cycle, archive-qmetry-test-cycle, unarchive-qmetry-test-cycle

  • Search: Search and filter test cycles with advanced criteria

  • Create: Create new test cycles with configuration

  • Update: Modify existing test cycles

  • Move: Move test cycles to different folders

  • Link/Unlink test cases: Associate or remove test cases from a cycle

  • Get linked test plans: View test plans linked to a test cycle

  • Link/Unlink requirements: Manage Jira requirements linked to cycles

  • Archive: Archive or unarchive test cycles


πŸ”„ Test Cycle Execution

Tools: get-qmetry-test-cycle-linked-test-cases, get-qmetry-test-cycle-linked-defects

  • Get linked test cases: Retrieve all test cases linked to a specific test cycle with advanced filtering

    • Filter by: searchText, status, priority, testCaseKey, environment, executionResult, build, removeDuplicates, linkedBetweenDates, executionLevel

    • Supports pagination, field selection, and sorting

  • Get linked defects: Retrieve all defects linked to test cycle executions

    • Filter by: searchText, status, priority, testCaseKey, environment, executionResult, build, removeDuplicates, linkedBetweenDates, executionLevel

    • Supports pagination, field selection, and sorting


πŸ”„ Test Cycle Status

Tools: get-qmetry-test-cycle-statuses, create-qmetry-test-cycle-status, update-qmetry-test-cycle-status, delete-qmetry-test-cycle-status, get-test-cycle-status-ref-count

  • Get: List test cycle statuses

  • Create: Create custom statuses for cycles

  • Update: Modify existing statuses

  • Delete: Remove unused statuses

  • Reference count: Check status usage


πŸ“‹ Test Plans

Tools: search-qmetry-test-plans, get-qmetry-test-plan, create-qmetry-test-plan, update-qmetry-test-plan, move-qmetry-test-plans, get-test-plan-test-cycles, link-test-cycles-to-test-plan, unlink-test-cycles-from-test-plan, archive-qmetry-test-plan, unarchive-qmetry-test-plan

  • Search: Search and filter test plans

  • Get: Retrieve specific test plan details

  • Create: Create new test plans

  • Update: Modify existing test plans

  • Move: Move test plans to different folders

  • Get linked test cycles: View test cycles linked to a plan

  • Link/Unlink test cycles: Associate or remove test cycles from plans

  • Archive: Archive or unarchive test plans


πŸ“‹ Test Plan Status

Tools: get-qmetry-test-plan-statuses, create-qmetry-test-plan-status, update-qmetry-test-plan-status, delete-qmetry-test-plan-status, get-test-plan-status-ref-count

  • Get: List test plan statuses

  • Create: Create custom statuses

  • Update: Modify existing statuses

  • Delete: Remove statuses from project

  • Reference count: View status usage


πŸͺœ Test Steps

Tools: get-qmetry-test-steps, create-qmetry-test-step, update-qmetry-test-step, delete-qmetry-test-step

  • Get: List all steps of a test case with pagination

  • Create: Create multiple steps with details, test data, and expected results

  • Update: Modify existing steps

  • Delete: Remove steps from a test case


⚑ Priorities

Tools: get-qmetry-priorities, create-qmetry-priority, update-qmetry-priority, delete-qmetry-priority, search-qmetry-priorities

  • Get: List all project priorities

  • Create: Create custom priorities with hexadecimal colors

  • Update: Modify existing priorities

  • Delete: Remove unused priorities

  • Search: Locate priorities by name


🏷️ Labels

Tools: get-qmetry-labels, create-qmetry-label, update-qmetry-label, delete-qmetry-label, get-qmetry-label-reference-count

  • Get: List all project labels

  • Create: Create new labels for categorization

  • Update: Modify label names

  • Delete: Remove labels from project

  • Reference count: See how many items use a label


πŸ”— Linked Requirements

Tools: get-qmetry-linked-requirements, link-qmetry-requirements, unlink-qmetry-requirements

  • Get: List all requirements (Jira issues) linked to a test case

  • Link: Associate one or more Jira issues with a test case

  • Unlink: Remove association between requirements and test cases


🏷️ Custom Fields

Tools: get-qmetry-custom-field-types, get-qmetry-test-case-custom-fields, get-tc-custom-field-ref-count, get-qmetry-test-cycle-custom-fields, get-tcy-custom-field-ref-count, get-qmetry-test-plan-custom-fields, get-tp-custom-field-ref-count, get-qmetry-te-custom-fields, get-te-custom-field-ref-count

Custom Fields in Test Cases, Cycles & Plans:

  • Add/filter by custom fields when: creating, updating, searching test cases, test cycles, and test plans

  • Custom fields structure: [{ id: string; value: string }]

Get Custom Field Types: List all available custom field types in QMetry

Get Custom Fields by Module:

  • Test Case: get-qmetry-test-case-custom-fields - Get all test case custom field details

  • Test Cycle: get-qmetry-test-cycle-custom-fields - Get all test cycle custom field details

  • Test Plan: get-qmetry-test-plan-custom-fields - Get all test plan custom field details

  • Test Execution: get-qmetry-te-custom-fields - Get all test execution custom field details

Reference Counts: Check how many items reference each custom field:

  • get-tc-custom-field-ref-count - Test case references

  • get-tcy-custom-field-ref-count - Test cycle references

  • get-tp-custom-field-ref-count - Test plan references

  • get-te-custom-field-ref-count - Test execution references

🚨 Troubleshooting

Error: QMETRY_API_KEY not configured

export QMETRY_API_KEY="your-api-key"

πŸ“š Resources

πŸ“„ License

This project is licensed under Apache License 2.0. See the LICENSE file for details.

Why Apache License 2.0?

  • βœ… Patent protection: Explicit grant of patent rights

  • βœ… Trademark control: Protection over trademark usage

  • βœ… Change declaration: Requires documenting modifications

  • βœ… Enterprise use: Widely accepted in corporate environments

  • βœ… Compatible: With most open source licenses

Important Notices

This software integrates with QMetry and Jira through their public APIs. QMetry is a registered trademark of Zoho Corporation and Jira is a registered trademark of Atlassian Pty Ltd. This project is not affiliated with, endorsed by, or sponsored by these companies.

See the NOTICE file for complete information about attributions and legal notices.

πŸ‘₯ Contributing

To contribute to the project:

  1. Fork & Pull Request: Fork the project and submit your changes via pull requests

  2. Clean code: Keep code clean using ESLint and Prettier (pnpm lint:fix)

  3. Logging: Use the provided logging system (never console.log)

  4. Documentation: Document all functions with JSDoc

  5. Patterns: Follow established patterns in the project

  6. Testing: Test your changes with MCP Inspector (pnpm run:inspector)

  7. License: By contributing, you agree that your code will be licensed under Apache License 2.0

  8. Changes: Clearly document what changes you made and why

License Header

Add this header at the beginning of new TypeScript files:

/**
 * Copyright 2025 Alberto Zapata
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

For detailed contribution guidelines, see CONTRIBUTING.md.

πŸ”„ Version

v1.8.3 - Current MCP server version

Release Notes

  • βœ… v1.8.3 - Fix SDK compatibility: Downgrade to SDK 1.22.0 to resolve Zod v4 literal extraction bug

Available Tools

93 tools
add-test-case-versionAdd Test Case versionB

Create a new version of an existing test case

Inputs: id (required), copyFromVersion (required), fields.

archive-qmetry-test-caseArchive Test CaseC

Archive a test case

Inputs: id (required).

archive-qmetry-test-cycleArchive a Qmetry test cycleC

Archive a test cycle

Inputs: idOrKey (required).

archive-qmetry-test-planArchive a Qmetry test planC

Archive a test plan

Inputs: idOrKey (required).

clone-qmetry-test-caseClone Test CaseC

Clone a test case with optional configurations

Inputs: id (required), summary (required), version, folderId, +4 more.

copy-qmetry-test-caseCopy a Qmetry test case to a different folderC

Copy a Qmetry test case from one folder to another folder

Inputs: projectId (required), testcaseIds (required), targetFolderId (required), selectedFolderId (required).

copy-qmetry-test-case-folderCopy a Qmetry test case folderC

Copy a Qmetry test case folder and optionally its contents to another location

Inputs: folderId (required), projectId (required), newParentId (required).

create-qmetry-labelCreate Qmetry labelB

Create a new label in a Qmetry project

Inputs: name (required), projectId (required).

create-qmetry-test-caseCreate a Qmetry test caseC

Create a Qmetry test case

Inputs: steps (required), summary (required), folderId (required), projectId (required), +13 more.

create-qmetry-test-case-folderCreate a Qmetry test case folderB

Create a Qmetry test case folder for a given project key

Inputs: parentId (required), projectId (required), folderName (required), description.

create-qmetry-test-case-statusCreate Qmetry test case statusB

Create a new test case status in QMetry

Inputs: name (required), color (required), projectId (required), description.

create-qmetry-test-cycleCreate a Qmetry test cycleC

Create a new test cycle

Inputs: summary (required), projectId (required), labels, status, +11 more.

create-qmetry-test-cycle-folderCreate a Qmetry test cycle folderC

Create a Qmetry test cycle folder for a given project

Inputs: parentId (required), projectId (required), folderName (required), description.

create-qmetry-test-cycle-statusCreate Qmetry test cycle statusB

Create a new test cycle status in QMetry

Inputs: name (required), color (required), projectId (required), description.

create-qmetry-test-planCreate a Qmetry test planC

Create a new test plan

Inputs: summary (required), projectId (required), labels, status, +6 more.

create-qmetry-test-plan-folderCreate a Qmetry test plan folderB

Create a Qmetry test plan folder for a given project

Inputs: parentId (required), projectId (required), folderName (required), description.

create-qmetry-test-plan-statusCreate Qmetry test plan statusB

Create a new test plan status in QMetry

Inputs: name (required), color (required), projectId (required), description.

create-qmetry-test-stepCreate a Qmetry test stepB

Create a Qmetry test step for a given test case

Inputs: id (required), no (required), steps (required).

delete-qmetry-labelDelete Qmetry labelB

Delete a label from a Qmetry project

Inputs: labelId (required), projectId (required).

delete-qmetry-test-case-statusDelete Qmetry test case statusB

Delete a test case status from QMetry

Inputs: statusId (required), projectId (required).

delete-qmetry-test-cycle-statusDelete Qmetry test cycle statusB

Delete a test cycle status from QMetry

Inputs: statusId (required), projectId (required).

delete-qmetry-test-plan-statusDelete Qmetry test plan statusB

Delete a test plan status from QMetry

Inputs: statusId (required), projectId (required).

delete-qmetry-test-stepDelete a Qmetry test stepC

Delete a Qmetry test step for a given test case

Inputs: id (required), no (required), stepIds (required).

delete-test-case-versionDelete Test Case versionB

Delete a specific test case version

Inputs: id (required), no (required).

edit-qmetry-test-case-folderEdit a Qmetry test case folderC

Edit a Qmetry test case folder for a given project key

Inputs: folderId (required), projectId (required), folderName (required), description.

edit-qmetry-test-cycle-folderEdit a Qmetry test cycle folderB

Edit a Qmetry test cycle folder for a given project

Inputs: folderId (required), projectId (required), folderName (required), description.

edit-qmetry-test-plan-folderEdit a Qmetry test plan folderC

Edit a Qmetry test plan folder for a given project

Inputs: folderId (required), projectId (required), folderName (required), description.

get-qmetry-custom-field-typesGet Custom Field TypesA

Get all custom field types supported in QMetry

Inputs: no named parameters.

get-qmetry-label-reference-countGet Qmetry label reference countC

Get Qmetry label reference count for a given project

Inputs: labelId (required), projectId (required).

get-qmetry-labelsGet Qmetry labelsC

Get Qmetry labels for a given project with optional filtering and pagination

Inputs: projectId (required).

get-qmetry-linked-test-casesGet linked test cases for a requirementB

Get all test cases linked to a specific requirement (Jira issue) in Qmetry

Inputs: id (required), sort, fields, filter, +2 more.

get-qmetry-prioritiesGet Qmetry prioritiesB

Get Qmetry priorities for a given project

Inputs: projectId (required), status.

get-qmetry-priority-reference-countGet Qmetry priority reference countB

Get Qmetry priority reference count for a given project

Inputs: projectId (required), priorityId (required).

get-qmetry-projectsGet all Qmetry projectsD

Get all Qmetry projects

Inputs: projectName (required), startAt, maxResults.

get-qmetry-te-custom-fieldsGet Test Execution Custom FieldsC

Get all test execution custom field details

Inputs: projectId (required).

get-qmetry-test-case-custom-fieldsGet Test Case Custom FieldsB

Get all test case custom field details

Inputs: projectId (required).

get-qmetry-test-case-foldersGet all Qmetry test case folders for a projectB

Get all Qmetry test case folders for a given project key

Inputs: projectId (required), short, withCount.

get-qmetry-test-case-statusesGet Qmetry test case statusesC

Get Qmetry test case statuses for a given project with optional filtering and pagination

Inputs: projectId (required), status.

get-qmetry-test-cycleGet Test CycleC

Get details of a specific test cycle

Inputs: idOrKey (required), fields.

get-qmetry-test-cycle-custom-fieldsGet Test Cycle Custom FieldsB

Get all existing test cycle custom field details

Inputs: projectId (required).

get-qmetry-test-cycle-foldersGet Qmetry test cycle foldersC

Get Qmetry test cycle folders for a given project

Inputs: projectId (required), sort, withCount.

get-qmetry-test-cycle-linked-defectsGet Defects linked on Test Cycle executionsC

Get all defects linked to test cycle executions with pagination and filtering support

Inputs: id (required), sort, fields, filter, +2 more.

get-qmetry-test-cycle-linked-test-casesGet linked Test Cases of Test CycleB

Get test cases that are linked to a specific test cycle with pagination and filtering support

Inputs: id (required), sort, fields, filter, +2 more.

get-qmetry-test-cycle-statusesGet Qmetry test cycle statusesC

Get Qmetry test cycle statuses for a given project with optional filtering

Inputs: projectId (required), status.

get-qmetry-test-planGet a Qmetry test planB

Get details of a specific test plan by ID or Key

Inputs: idOrKey (required), fields.

get-qmetry-test-plan-custom-fieldsGet Test Plan Custom FieldsB

Get custom field details for Test Plan Module

Inputs: projectId (required).

get-qmetry-test-plan-foldersGet Qmetry test plan foldersB

Get Qmetry test plan folders for a given project

Inputs: projectId (required), sort, withCount.

get-qmetry-test-plan-statusesGet Qmetry test plan statusesB

Get Qmetry test plan statuses for a given project with optional filtering

Inputs: projectId (required), status.

get-qmetry-test-stepsGet Qmetry test stepsB

Get Qmetry test steps for a given test case

Inputs: id (required), no (required), sort, startAt, +1 more.

get-tc-custom-field-ref-countGet Test Case Custom Field Reference CountC

Get reference count for a particular test case custom field

Inputs: id (required), projectId (required).

get-tcy-custom-field-ref-countGet Test Cycle Custom Field Reference CountC

Get test cycle references for a particular custom field

Inputs: id (required), projectId (required).

get-te-custom-field-ref-countGet Test Execution Custom Field Reference CountA

Get test execution reference count for a particular custom field

Inputs: id (required), projectId (required).

get-test-case-status-ref-countGet Qmetry test case status reference countC

Get the reference count of a test case status in QMetry

Inputs: statusId (required), projectId (required).

get-test-case-test-cyclesGet Linked Test CyclesC

Get test cycles linked to a test case

Inputs: id (required), tcVersionNo (required), sort, fields, +2 more.

get-test-case-version-detailsGet Test Case version detailsB

Get details of a specific test case version

Inputs: id (required), no (required), fields.

get-test-case-versions-listGet Test Case versions listA

Get list of all versions of a test case

Inputs: id (required).

get-test-cycle-requirementsGet linked requirements for a test cycleA

Get all requirements (stories) linked to a test cycle

Inputs: id (required), sort, startAt, maxResults.

get-test-cycle-status-ref-countGet Qmetry test cycle status reference countB

Get the reference count of a test cycle status in QMetry

Inputs: statusId (required), projectId (required).

get-test-cycle-test-plansGet linked test plans for a test cycleB

Get all test plans linked to a test cycle

Inputs: id (required), sort, fields, startAt, +1 more.

get-test-plan-status-ref-countGet Qmetry test plan status reference countB

Get the reference count of a test plan status in QMetry

Inputs: statusId (required), projectId (required).

get-test-plan-test-cyclesGet linked test cycles from a test planC

Get test cycles linked to a test plan

Inputs: id (required), sort, fields, startAt, +1 more.

get-tp-custom-field-ref-countGet Test Plan Custom Field Reference CountB

Get test plan reference count for a particular custom field

Inputs: id (required), projectId (required).

move-qmetry-test-caseMove a Qmetry test case to a different folderC

Move a Qmetry test case from one folder to another folder

Inputs: projectId (required), testcaseIds (required), targetFolderId (required), selectedFolderId (required).

move-qmetry-test-case-folderMove a Qmetry test case folderC

Move a Qmetry test case folder to a new parent folder

Inputs: folderId (required), projectId (required), newParentId (required).

move-qmetry-test-cycleMove Qmetry test cycles to a different folderB

Move test cycles from one folder to another folder

Inputs: projectId (required), testcycleIds (required), targetFolderId (required).

move-qmetry-test-cycle-folderMove a Qmetry test cycle folderB

Move a Qmetry test cycle folder to a new parent folder

Inputs: folderId (required), projectId (required), newParentId (required).

move-qmetry-test-plan-folderMove a Qmetry test plan folderB

Move a Qmetry test plan folder to a new parent folder

Inputs: folderId (required), projectId (required), newParentId (required).

move-qmetry-test-plansMove Qmetry test plansC

Move test plans to another folder

Inputs: projectId (required), testplanIds (required), targetFolderId (required).

search-qmetry-test-case-foldersSearch a Qmetry test case folderB

Search a Qmetry test case folder for a given project

Inputs: projectId (required), folderName (required), mode.

search-qmetry-test-casesSearch Qmetry test casesC

Search and list test cases according to filters

Inputs: filter (required), sort, fields, startAt, +1 more.

search-qmetry-test-cycle-folderSearch a Qmetry test cycle folderC

Search a Qmetry test cycle folder for a given project

Inputs: projectId (required), folderName (required), mode.

search-qmetry-test-cyclesSearch Qmetry test cyclesB

Search and list test cycles according to filters

Inputs: filter (required), sort, fields, startAt, +1 more.

search-qmetry-test-plan-folderSearch a Qmetry test plan folderC

Search a Qmetry test plan folder for a given project

Inputs: projectId (required), folderName (required), mode.

search-qmetry-test-plansSearch Qmetry test plansC

Search and list test plans according to filters

Inputs: filter (required), sort, fields, startAt, +1 more.

unarchive-qmetry-test-caseUnarchive Test CaseC

Unarchive a test case

Inputs: id (required).

unarchive-qmetry-test-cycleUnarchive a Qmetry test cycleC

Unarchive a test cycle

Inputs: idOrKey (required).

unarchive-qmetry-test-planUnarchive a Qmetry test planC

Unarchive a test plan

Inputs: idOrKey (required).

update-qmetry-labelUpdate Qmetry labelB

Update an existing label in a Qmetry project

Inputs: name (required), labelId (required), projectId (required).

update-qmetry-test-caseUpdate a Qmetry test caseC

Update a Qmetry test case

Inputs: id (required), no (required), labels, sprint, +10 more.

update-qmetry-test-case-statusUpdate Qmetry test case statusC

Update an existing test case status in QMetry

Inputs: name (required), color (required), statusId (required), projectId (required), +1 more.

update-qmetry-test-cycleUpdate a Qmetry test cycleC

Update an existing test cycle

Inputs: id (required), summary (required), projectId (required), labels, +12 more.

update-qmetry-test-cycle-statusUpdate Qmetry test cycle statusB

Update an existing test cycle status in QMetry

Inputs: name (required), color (required), statusId (required), projectId (required), +1 more.

update-qmetry-test-planUpdate a Qmetry test planC

Update an existing test plan

Inputs: id (required), labels, status, summary, +5 more.

update-qmetry-test-plan-statusUpdate Qmetry test plan statusB

Update an existing test plan status in QMetry

Inputs: name (required), color (required), statusId (required), projectId (required), +1 more.

update-qmetry-test-stepUpdate a Qmetry test stepC

Update a Qmetry test step for a given test case

Inputs: no (required), steps (required), testCaseId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 93 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs (e.g., test case vs test cycle). However, the high number of similar patterns (e.g., multiple 'get-custom-field' variants) may cause occasional confusion, though descriptions help.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create-qmetry-test-case, get-qmetry-test-cycle). Even abbreviations like 'tc' and 'tcy' are used consistently across similar operations.

    Tool Count2/5

    93 tools is excessively high for a test management server. An agent would need to navigate an overwhelming list, making selection error-prone. A more focused set (20-40) would be appropriate.

    Completeness5/5

    The surface covers all major lifecycle operations for test cases, cycles, plans, folders, statuses, labels, steps, versions, linking, and custom fields. No obvious gaps are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers