[QTM4J] Initial SmartBear MCP Integration for Test Case & Project Operations (#476)

* Merge pull request #430 from SmartBear/QFJV-16868

[QTM4J] QFJV-16868 : Project Setup Related Skills

* feat: implement QTM4J API client with authentication and field resolution tools

* feat: refactor CreateTestCase to use resolution-helper and improve field resolution logic

* feat: streamline field resolution logic in CreateTestCase by optimizing imports and function calls

* feat: update import paths for API client and related modules, add tests for field metadata fetcher and resolvers

* feat: implement resolver registry and multiple resolvers for field resolution, update project context handling, and enhance test case retrieval

* feat: rename SearchTestCases to GetTestCases and update related imports and tests

* feat: rename SearchTestCase schema to GetTestCase and update related imports

* feat: update import statement for GetTestCases and add CLAUDE.md for project guidance

* feat: add UpdateTestCase tool for updating existing test cases with auto-resolving fields

* fix: standardize folderId string quotes in create-test-case.ts

* test: update expectations for FIELD_CONFIG to include FOLDER entry

* feat: add QTM4J integration with environment variable setup and documentation

* feat: update documentation to include QTM4J integration and related configuration details

* fix: remove outdated example for retrieving test cases in getting-started documentation

* fix: update QTM4J documentation for clarity and consistency

* feat: enhance QTM4J integration documentation and update references

* fix: update Qtm4jClient and project context tests for improved handling of undefined values

* feat: add QTM4J API key and base URL configuration to local server setup

* feat: add QTM4J API methods for creating test cases and retrieving projects

* feat: update project schema to allow nullable avatarUrl and projectTypeKey

* feat: integrate cache service into QTM4J resolvers and client for improved data handling (#477)

* fix: remove unwanted QTM4J tools from CHANGELOG.md (#478)

---------

Co-authored-by: Jaydeep Kumbhani <jaydeep.kumbhani@smartbear.com>

Author: harsh-mehta-sb

CHANGELOG.md

@@ -13,6 +13,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - [Common] Add graceful shutdown on SIGTERM/SIGINT in HTTP mode: drains active sessions (closes Streamable HTTP and SSE transports, runs per-client `cleanupSession` hooks including Reflect WebSocket teardown), with a configurable deadline via `MCP_SHUTDOWN_TIMEOUT_MS` (default 25s) [#455](https://github.com/SmartBear/smartbear-mcp/pull/455)
 - [Common] Split health/readiness probes: `GET /health` is now liveness-only and always returns 200 when the process is responsive; `GET /ready` is the readiness probe and returns 503 during drain so load balancers stop routing new sessions to draining pods. Both probes set `Cache-Control: no-store`. [#455](https://github.com/SmartBear/smartbear-mcp/pull/455)
 - [Common] Add product prefix to registered resources and prompts [#458](https://github.com/SmartBear/smartbear-mcp/pull/458)
+- [QTM4J] Add QTM4J (QMetry Test Management for Jira) capabilities to MCP [#476](https://github.com/SmartBear/smartbear-mcp/pull/476)
 
 ### Fixed
 

README.md

@@ -18,7 +18,7 @@
 </div>
 <br />
 
-A Model Context Protocol (MCP) server which provides AI assistants with seamless access to SmartBear's suite of testing and monitoring tools, including [BugSnag](https://www.bugsnag.com/), [Reflect](https://reflect.run), [Swagger](https://www.smartbear.com/api-hub), [PactFlow](https://pactflow.io/), [Pact Broker](https://docs.pact.io/), [QMetry](https://www.qmetry.com/), [Zephyr](https://smartbear.com/test-management/zephyr/) and [Collaborator](https://smartbear.com/product/collaborator/).
+A Model Context Protocol (MCP) server which provides AI assistants with seamless access to SmartBear's suite of testing and monitoring tools, including [BugSnag](https://www.bugsnag.com/), [Reflect](https://reflect.run), [Swagger](https://www.smartbear.com/api-hub), [PactFlow](https://pactflow.io/), [Pact Broker](https://docs.pact.io/), [QMetry](https://www.qmetry.com/), [QTM4J](https://www.qmetry.com/qmetry-test-management-for-jira), [Zephyr](https://smartbear.com/test-management/zephyr/) and [Collaborator](https://smartbear.com/product/collaborator/).
 
 ## What is MCP?
 
@@ -37,6 +37,7 @@ See individual guides for suggested prompts and supported tools and resources:
 - [QMetry](https://developer.smartbear.com/smartbear-mcp/docs/qmetry-integration) - QMetry Test Management capabilities
 - [Zephyr](https://developer.smartbear.com/smartbear-mcp/docs/zephyr-integration) - Zephyr Test Management capabilities
 - [Collaborator](https://developer.smartbear.com/smartbear-mcp/docs/collaborator-integration) - Review and Remote System Configuration management capabilities
+- [QTM4J](https://developer.smartbear.com/smartbear-mcp/docs/qtm4j-integration) - QTM4J Test Management for Jira capabilities
 
 ## Remote MCP Servers
 
@@ -50,12 +51,12 @@ For BugSnag, Swagger, and Zephyr, SmartBear hosts Remote MCP Servers that you ca
 
 See the [Remote MCP Servers guide](https://developer.smartbear.com/smartbear-mcp/docs/remote-mcp-servers) for per-client setup instructions. You can connect to multiple remote servers at the same time.
 
-> **Need Reflect, QMetry, PactFlow, or Collaborator?** These products are only available via the local npm package below, which bundles all products into a single MCP server.
+> **Need Reflect, QMetry, QTM4J, PactFlow, or Collaborator?** These products are only available via the local npm package below, which bundles all products into a single MCP server.
 
 ## Prerequisites
 
 - Node.js 20+ and npm
-- Access to SmartBear products (BugSnag, Reflect, Swagger, QMetry, or Zephyr)
+- Access to SmartBear products (BugSnag, Reflect, Swagger, QMetry, QTM4J or Zephyr)
 - Valid API tokens for the products you want to integrate
 
 ## Local MCP Server Installation (npm)
@@ -101,7 +102,9 @@ Alternatively, you can use `npx` (or globally install) the `@smartbear/mcp` pack
         "ZEPHYR_BASE_URL": "${input:zephyr_base_url}",
         "COLLABORATOR_BASE_URL": "${input:collab_base_url}",
         "COLLABORATOR_USERNAME": "${input:collab_username}",
-        "COLLABORATOR_LOGIN_TICKET": "${input:collab_login_ticket}"
+        "COLLABORATOR_LOGIN_TICKET": "${input:collab_login_ticket}",
+        "QTM4J_API_KEY": "${input:qtm4j_api_key}",
+        "QTM4J_BASE_URL": "${input:qtm4j_base_url}"
       }
     }
   },
@@ -213,7 +216,19 @@ Alternatively, you can use `npx` (or globally install) the `@smartbear/mcp` pack
           "type": "promptString",
           "description": "Collab login ticket",
           "password": true
-      }
+      },
+      {
+          "id": "qtm4j_api_key",
+          "type": "promptString",
+          "description": "QTM4J API Key",
+          "password": true
+    },
+    {
+          "id": "qtm4j_base_url",
+          "type": "promptString",
+          "description": "US region (default): https://qtmcloud.qmetry.com. Australia region: https://syd-qtmcloud.qmetry.com.",
+          "password": false
+    }
   ]
 }
 ```
@@ -250,7 +265,9 @@ Add the following configuration to your `claude_desktop_config.json` to launch t
         "ZEPHYR_BASE_URL": "https://api.zephyrscale.smartbear.com/v2",
         "COLLABORATOR_BASE_URL": "your collab base url",
         "COLLABORATOR_USERNAME": "your collab user name",
-        "COLLABORATOR_LOGIN_TICKET": "your collab login ticket"
+        "COLLABORATOR_LOGIN_TICKET": "your collab login ticket",
+        "QTM4J_API_KEY": "your_qtm4j_key",
+        "QTM4J_BASE_URL": "https://qtmcloud.qmetry.com"
       }
     }
   }

docs/custom-words.txt

@@ -23,6 +23,8 @@ pacticipant
 pacticipants
 petstore
 qmetry
+qtm4j
+qtmcloud
 Reactnative
 reindexing
 SCIM

docs/products/SmartBear MCP Server/getting-started.md

@@ -2,13 +2,13 @@ The SmartBear MCP Server is available in two deployment modes: **remote hosted s
 
 ## Comparison
 
-| | [Remote MCP Servers](/smartbear-mcp/docs/remote-mcp-servers) | [Local MCP Server](/smartbear-mcp/docs/local-server) |
-|---|---|---|
-| **Products** | Swagger, BugSnag, Zephyr | All products (incl. Reflect, QMetry, PactFlow, Collaborator) |
-| **Setup** | None — add a URL to your MCP client | Install via npm (Node.js 20+) |
-| **Authentication** | OAuth browser flow | API tokens via environment variables |
-| **Configuration** | Headers and query string | Environment variables |
-| **Best for** | Quick setup for a single product | Multi-product workflows |
+| | [Remote MCP Servers](/smartbear-mcp/docs/remote-mcp-servers) | [Local MCP Server](/smartbear-mcp/docs/local-server)                |
+|---|---|---------------------------------------------------------------------|
+| **Products** | Swagger, BugSnag, Zephyr | All products (incl. Reflect, QMetry, QTM4J, PactFlow, Collaborator) |
+| **Setup** | None — add a URL to your MCP client | Install via npm (Node.js 20+)                                       |
+| **Authentication** | OAuth browser flow | API tokens via environment variables                                |
+| **Configuration** | Headers and query string | Environment variables                                               |
+| **Best for** | Quick setup for a single product | Multi-product workflows                                             |
 
 ## Which should I use?
 
@@ -18,7 +18,7 @@ The SmartBear MCP Server is available in two deployment modes: **remote hosted s
 - You prefer OAuth login over managing API tokens in environment variables
 
 **Use the Local MCP Server if:**
-- You need access to Reflect, QMetry, PactFlow, or Collaborator tools
+- You need access to Reflect, QMetry, QTM4J, PactFlow, or Collaborator tools
 - You want all SmartBear tools available in a single MCP server
 - You are using an MCP client that does not yet support HTTP/OAuth transport