Jira QMetry MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server (default 3000) | 3000 |
| NODE_ENV | No | Environment mode (default production) | production |
| QMETRY_API_KEY | Yes | Your QMetry API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-qmetry-projectsD | Get all Qmetry projects |
| get-qmetry-test-case-foldersB | Get all Qmetry test case folders for a given project key |
| create-qmetry-test-case-folderB | Create a Qmetry test case folder for a given project key |
| edit-qmetry-test-case-folderC | Edit a Qmetry test case folder for a given project key |
| copy-qmetry-test-case-folderC | Copy a Qmetry test case folder and optionally its contents to another location |
| move-qmetry-test-case-folderC | Move a Qmetry test case folder to a new parent folder |
| search-qmetry-test-case-foldersB | Search a Qmetry test case folder for a given project |
| get-qmetry-test-cycle-foldersC | Get Qmetry test cycle folders for a given project |
| create-qmetry-test-cycle-folderC | Create a Qmetry test cycle folder for a given project |
| edit-qmetry-test-cycle-folderB | Edit a Qmetry test cycle folder for a given project |
| move-qmetry-test-cycle-folderB | Move a Qmetry test cycle folder to a new parent folder |
| search-qmetry-test-cycle-folderC | Search a Qmetry test cycle folder for a given project |
| get-qmetry-test-plan-foldersB | Get Qmetry test plan folders for a given project |
| create-qmetry-test-plan-folderB | Create a Qmetry test plan folder for a given project |
| edit-qmetry-test-plan-folderC | Edit a Qmetry test plan folder for a given project |
| move-qmetry-test-plan-folderB | Move a Qmetry test plan folder to a new parent folder |
| search-qmetry-test-plan-folderC | Search a Qmetry test plan folder for a given project |
| search-qmetry-test-casesC | Search and list test cases according to filters |
| create-qmetry-test-caseC | Create a Qmetry test case |
| move-qmetry-test-caseC | Move a Qmetry test case from one folder to another folder |
| copy-qmetry-test-caseC | Copy a Qmetry test case from one folder to another folder |
| update-qmetry-test-caseC | Update a Qmetry test case |
| get-test-case-version-detailsB | Get details of a specific test case version |
| add-test-case-versionB | Create a new version of an existing test case |
| delete-test-case-versionB | Delete a specific test case version |
| archive-qmetry-test-caseC | Archive a test case |
| unarchive-qmetry-test-caseC | Unarchive a test case |
| clone-qmetry-test-caseC | Clone a test case with optional configurations |
| get-test-case-test-cyclesC | Get test cycles linked to a test case |
| get-test-case-versions-listA | Get list of all versions of a test case |
| search-qmetry-test-cyclesB | Search and list test cycles according to filters |
| create-qmetry-test-cycleC | Create a new test cycle |
| update-qmetry-test-cycleC | Update an existing test cycle |
| move-qmetry-test-cycleB | Move test cycles from one folder to another folder |
| link-test-case-to-test-cycleD | Link test cases to a test cycle |
| unlink-test-case-from-test-cycleC | Unlink test cases from a test cycle |
| get-test-cycle-test-plansB | Get all test plans linked to a test cycle |
| get-test-cycle-requirementsA | Get all requirements (stories) linked to a test cycle |
| link-requirements-to-test-cycleB | Link requirements (stories) to a test cycle. If any requirement cannot be linked then it will come under warningMessages obj of response. |
| unlink-requirements-from-test-cycleA | Unlink requirements (stories) from a test cycle. If any requirement cannot be unlinked then it will come under warningMessages obj of response. |
| archive-qmetry-test-cycleC | Archive a test cycle |
| unarchive-qmetry-test-cycleC | Unarchive a test cycle |
| get-qmetry-test-cycleC | Get details of a specific test cycle |
| search-qmetry-test-plansC | Search and list test plans according to filters |
| get-qmetry-test-planB | Get details of a specific test plan by ID or Key |
| create-qmetry-test-planC | Create a new test plan |
| update-qmetry-test-planC | Update an existing test plan |
| move-qmetry-test-plansC | Move test plans to another folder |
| get-test-plan-test-cyclesC | Get test cycles linked to a test plan |
| link-test-cycles-to-test-planC | Link test cycles to a test plan |
| unlink-test-cycles-from-test-planC | Unlink test cycles from a test plan |
| archive-qmetry-test-planC | Archive a test plan |
| unarchive-qmetry-test-planC | Unarchive a test plan |
| get-qmetry-test-stepsB | Get Qmetry test steps for a given test case |
| create-qmetry-test-stepB | Create a Qmetry test step for a given test case |
| update-qmetry-test-stepC | Update a Qmetry test step for a given test case |
| delete-qmetry-test-stepC | Delete a Qmetry test step for a given test case |
| get-qmetry-prioritiesB | Get Qmetry priorities for a given project |
| get-qmetry-priority-reference-countB | Get Qmetry priority reference count for a given project |
| get-qmetry-labelsC | Get Qmetry labels for a given project with optional filtering and pagination |
| create-qmetry-labelB | Create a new label in a Qmetry project |
| update-qmetry-labelB | Update an existing label in a Qmetry project |
| delete-qmetry-labelB | Delete a label from a Qmetry project |
| get-qmetry-label-reference-countC | Get Qmetry label reference count for a given project |
| get-qmetry-test-case-statusesC | Get Qmetry test case statuses for a given project with optional filtering and pagination |
| create-qmetry-test-case-statusB | Create a new test case status in QMetry |
| update-qmetry-test-case-statusC | Update an existing test case status in QMetry |
| delete-qmetry-test-case-statusB | Delete a test case status from QMetry |
| get-test-case-status-ref-countC | Get the reference count of a test case status in QMetry |
| get-qmetry-test-cycle-statusesC | Get Qmetry test cycle statuses for a given project with optional filtering |
| create-qmetry-test-cycle-statusB | Create a new test cycle status in QMetry |
| update-qmetry-test-cycle-statusB | Update an existing test cycle status in QMetry |
| delete-qmetry-test-cycle-statusB | Delete a test cycle status from QMetry |
| get-test-cycle-status-ref-countB | Get the reference count of a test cycle status in QMetry |
| get-qmetry-test-plan-statusesB | Get Qmetry test plan statuses for a given project with optional filtering |
| create-qmetry-test-plan-statusB | Create a new test plan status in QMetry |
| update-qmetry-test-plan-statusB | Update an existing test plan status in QMetry |
| delete-qmetry-test-plan-statusB | Delete a test plan status from QMetry |
| get-test-plan-status-ref-countB | Get the reference count of a test plan status in QMetry |
| get-qmetry-linked-test-casesB | Get all test cases linked to a specific requirement (Jira issue) in Qmetry |
| link-qmetry-requirementsB | Link one or more requirements (Jira issues) to a specific test case in Qmetry |
| unlink-qmetry-requirementsA | Unlink one or more requirements (Jira issues) from a specific test case in Qmetry |
| get-qmetry-custom-field-typesA | Get all custom field types supported in QMetry |
| get-qmetry-test-case-custom-fieldsB | Get all test case custom field details |
| get-tc-custom-field-ref-countC | Get reference count for a particular test case custom field |
| get-qmetry-test-cycle-custom-fieldsB | Get all existing test cycle custom field details |
| get-tcy-custom-field-ref-countC | Get test cycle references for a particular custom field |
| get-qmetry-test-plan-custom-fieldsB | Get custom field details for Test Plan Module |
| get-tp-custom-field-ref-countB | Get test plan reference count for a particular custom field |
| get-qmetry-te-custom-fieldsC | Get all test execution custom field details |
| get-te-custom-field-ref-countA | Get test execution reference count for a particular custom field |
| get-qmetry-test-cycle-linked-test-casesB | Get test cases that are linked to a specific test cycle with pagination and filtering support |
| get-qmetry-test-cycle-linked-defectsC | Get all defects linked to test cycle executions with pagination and filtering support |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/albertor03/jira-qmetry-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server