@uarlouski/testrail-mcp-server 1.3.1 → 1.5.0

package/README.md

@@ -1,41 +1,103 @@
-# TestRail MCP Server
+<p align="center">
+  <h1 align="center">TestRail MCP Server</h1>
+  <p align="center">
+    A Model Context Protocol (MCP) server that connects AI assistants to TestRail test management — search, create, update, and execute test cases using natural language.
+  </p>
+</p>
+
+<p align="center">
+  <a href="https://www.npmjs.com/package/@uarlouski/testrail-mcp-server"><img src="https://badge.fury.io/js/@uarlouski%2Ftestrail-mcp-server.svg" alt="npm version"></a>
+  <a href="https://www.npmjs.com/package/@uarlouski/testrail-mcp-server"><img src="https://img.shields.io/npm/dm/@uarlouski/testrail-mcp-server.svg" alt="npm downloads"></a>
+  <a href="https://github.com/uarlouski/testrail-mcp-server/actions/workflows/ci.yml"><img src="https://github.com/uarlouski/testrail-mcp-server/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
+  <a href="https://opensource.org/licenses/Apache-2.0"><img src="https://img.shields.io/badge/License-Apache_2.0-blue.svg" alt="License"></a>
+  <a href="https://www.typescriptlang.org/"><img src="https://img.shields.io/badge/TypeScript-5.9-blue.svg" alt="TypeScript"></a>
+  <a href="https://github.com/uarlouski/testrail-mcp-server"><img src="https://img.shields.io/github/stars/uarlouski/testrail-mcp-server.svg?style=social&label=Star" alt="GitHub stars"></a>
+</p>
 
-[![npm version](https://badge.fury.io/js/@uarlouski%2Ftestrail-mcp-server.svg)](https://www.npmjs.com/package/@uarlouski/testrail-mcp-server)
-[![npm downloads](https://img.shields.io/npm/dm/@uarlouski/testrail-mcp-server.svg)](https://www.npmjs.com/package/@uarlouski/testrail-mcp-server)
-[![CI](https://github.com/uarlouski/testrail-mcp-server/actions/workflows/ci.yml/badge.svg)](https://github.com/uarlouski/testrail-mcp-server/actions/workflows/ci.yml)
-[![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
-[![TypeScript](https://img.shields.io/badge/TypeScript-5.9.3-blue.svg)](https://www.typescriptlang.org/)
-[![GitHub stars](https://img.shields.io/github/stars/uarlouski/testrail-mcp-server.svg?style=social&label=Star)](https://github.com/uarlouski/testrail-mcp-server)
+---
+
+## Why TestRail MCP Server?
+
+Managing test cases manually is tedious. With the TestRail MCP Server, your AI assistant (Claude, Cursor, Windsurf, or any MCP-compliant client) talks directly to TestRail. Ask it to find test cases, create new ones, kick off test runs, or report results — all through natural conversation.
+
+**No context switching. No copy-pasting. Just ask.**
+
+## ✨ Features
 
+| Category | Capabilities |
+|----------|-------------|
+| **🔍 Discovery** | Browse projects, suites, and sections to map your test organization |
+| **📋 Case Management** | Fetch, create, update, and bulk-edit test cases with full custom field support |
+| **▶️ Test Execution** | Create runs, record results, attach files, and track test statuses |
+| **🧠 Context-Aware** | Exposes templates, field definitions, priorities, and case types so LLMs generate valid, well-structured test cases |
 
-A powerful **Model Context Protocol (MCP)** server for seamless integration between **Large Language Models (LLMs)** and **TestRail** test case management.
+## 🚀 Quick Start
 
-This MCP server enables AI assistants like **Claude**, **Cursor**, **Windsurf**, and other MCP-compliant clients to interact directly with your TestRail instance. Streamline your QA workflows by allowing your AI to search, retrieve, create, and update test cases, plans, and runs.
+### 1. Get Your TestRail API Key
 
-## 🚀 Features
+Navigate to **My Settings → API Keys** in your TestRail instance and generate a new key.
 
-- **AI-Powered Test Management**: Bridge the gap between AI and your QA process.
-- **Smart Discovery**: List projects, suites, and sections to help LLMs understand your test organization.
-- **Comprehensive Case Operations**: Fetch, create, and update test cases with full support for custom fields.
-- **Context-Aware**: Designed to provide LLMs with the right context (templates, field options) for accurate test generation.
+### 2. Configure Your MCP Client
 
-## ⚙️ Usage
+Add the server to your MCP client configuration. Below are examples for popular clients.
+
+<details>
+<summary><strong>Claude Desktop</strong></summary>
+
+Edit your `claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "testrail": {
+      "command": "npx",
+      "args": ["-y", "@uarlouski/testrail-mcp-server@latest"],
+      "env": {
+        "TESTRAIL_INSTANCE_URL": "https://your-instance.testrail.io",
+        "TESTRAIL_USERNAME": "your@email.com",
+        "TESTRAIL_API_KEY": "your-api-key"
+      }
+    }
+  }
+}
+```
+
+</details>
+
+<details>
+<summary><strong>Cursor</strong></summary>
+
+Open **Settings → MCP** and add a new server:
+
+```json
+{
+  "mcpServers": {
+    "testrail": {
+      "command": "npx",
+      "args": ["-y", "@uarlouski/testrail-mcp-server@latest"],
+      "env": {
+        "TESTRAIL_INSTANCE_URL": "https://your-instance.testrail.io",
+        "TESTRAIL_USERNAME": "your@email.com",
+        "TESTRAIL_API_KEY": "your-api-key"
+      }
+    }
+  }
+}
+```
 
-Configure the server in your MCP client settings (e.g., `claude_desktop_config.json` or Cursor settings).
+</details>
 
-### Claude Desktop / General MCP Clients
+<details>
+<summary><strong>Windsurf</strong></summary>
 
-Add the following to your configuration file:
+Add to your Windsurf MCP configuration:
 
 ```json
 {
   "mcpServers": {
     "testrail": {
       "command": "npx",
-      "args": [
-        "-y",
-        "@uarlouski/testrail-mcp-server@latest"
-      ],
+      "args": ["-y", "@uarlouski/testrail-mcp-server@latest"],
       "env": {
         "TESTRAIL_INSTANCE_URL": "https://your-instance.testrail.io",
         "TESTRAIL_USERNAME": "your@email.com",
@@ -46,42 +108,110 @@ Add the following to your configuration file:
 }
 ```
 
-### Environment Variables
+</details>
+
+<details>
+<summary><strong>Other MCP Clients</strong></summary>
+
+Any MCP-compliant client can use this server. The configuration pattern is the same — point it at the `npx` command with the required environment variables.
+
+</details>
+
+### 3. Start Using It
+
+Once configured, ask your AI assistant things like:
+
+- *"List all projects in TestRail"*
+- *"Show me the test cases in suite 1 of project 3"*
+- *"Create a test case for login validation with steps"*
+- *"Start a new test run with cases from section 5"*
+- *"Mark test 42 as passed with a comment"*
+
+## ⚙️ Configuration
 
-| Variable | Description | Required |
-|----------|-------------|:--------:|
-| `TESTRAIL_INSTANCE_URL` | The URL of your TestRail instance (e.g., `https://example.testrail.io`) | Yes |
-| `TESTRAIL_USERNAME` | Your TestRail email address | Yes |
-| `TESTRAIL_API_KEY` | Your TestRail API key (generate in My Settings > API Keys) | Yes |
+| Environment Variable | Description | Required |
+|---------------------|-------------|:--------:|
+| `TESTRAIL_INSTANCE_URL` | Your TestRail instance URL (e.g., `https://example.testrail.io`) | ✅ |
+| `TESTRAIL_USERNAME` | Your TestRail email address | ✅ |
+| `TESTRAIL_API_KEY` | Your TestRail API key ([how to get one](https://support.testrail.com/hc/en-us/articles/7077039051412-Accessing-the-TestRail-API)) | ✅ |
 
 ## 🛠️ Available Tools
 
-This MCP server exposes the following tools to the LLM:
+### Discovery
 
 | Tool | Description |
 |------|-------------|
-| `get_projects` | **Discovery**: List all available projects in the TestRail instance to establish context. |
-| `get_suites` | **Discovery**: Retrieve test suites for a given project (if not in single-suite mode). |
-| `get_sections` | **Structure**: navigate the folder/section hierarchy of a test suite. |
-| `get_cases` | **Search**: Query test cases with filtering (priority, template, type, etc.) and pagination. |
-| `get_case` | **Detail**: Fetch comprehensive details of a specific test case, including steps and custom fields. |
-| `create_case` | **Authoring**: Create new test cases. *Tip: The model should check templates and fields first to ensure validity.* |
-| `update_case` | **Maintenance**: Modify existing test case fields, title, or steps. |
-| `update_cases` | **Bulk Edit**: Update multiple cases simultaneously for efficient refactoring. |
-| `add_run` | **Test Execution**: Create a new test run in TestRail. |
-| `get_tests` | **Test Execution**: Get tests for a test run, optionally filtered by status. |
-| `add_results` | **Test Execution**: Add one or more test results to a test run. |
-| `add_attachment_to_run` | **Test Execution**: Add an attachment (file or zipped folder) to a test run. |
-| `get_statuses` | **Metadata**: Get all available test statuses (e.g. Passed, Failed, Blocked). |
-| `get_case_fields` | **Metadata**: Retrieve definitions of custom fields to understand available inputs. |
-| `get_templates` | **Metadata**: List available case templates to ensure correct case creation structure. |
-| `get_priorities` | **Metadata**: List available priority levels. |
-| `get_case_types` | **Metadata**: List available case types (e.g., Automated, Manual). |
+| `get_projects` | List all available projects in your TestRail instance |
+| `get_sections` | Navigate the folder/section hierarchy of a test suite |
+
+### Test Case Management
+
+| Tool | Description |
+|------|-------------|
+| `get_cases` | Query test cases with filtering by priority, template, type, and more — supports pagination and recursive section fetching |
+| `get_case` | Fetch complete details of a specific test case including steps and custom fields |
+| `create_case` | Create a new test case with full custom field support |
+| `update_case` | Modify an existing test case's fields, title, or steps |
+| `update_cases` | Bulk-update multiple test cases simultaneously |
+
+### Test Execution
+
+| Tool | Description |
+|------|-------------|
+| `add_run` | Create a new test run in TestRail |
+| `get_tests` | Get tests for a run, optionally filtered by status |
+| `add_results` | Submit one or more test results to a run |
+| `add_attachment_to_run` | Attach a file or zipped folder to a test run |
+
+### Metadata
+
+| Tool | Description |
+|------|-------------|
+| `get_statuses` | List all available test statuses (Passed, Failed, Blocked, etc.) |
+| `get_case_fields` | Retrieve custom field definitions and dropdown options |
+| `get_templates` | List available case templates for correct case structure |
+
+## 🏗️ Development
+
+### Prerequisites
+
+- [Node.js](https://nodejs.org/) 18+
+- npm
+
+### Setup
+
+```bash
+git clone https://github.com/uarlouski/testrail-mcp-server.git
+cd testrail-mcp-server
+npm install
+```
+
+### Build
+
+```bash
+npm run build
+```
+
+### Run Tests
+
+```bash
+npm test
+```
+
+## 🤝 Contributing
+
+Contributions are welcome! Please feel free to open an [issue](https://github.com/uarlouski/testrail-mcp-server/issues) or submit a pull request.
 
 ## 📜 License
 
-This project is licensed under the Apache 2.0 License - see the [LICENSE](LICENSE) file for details.
+This project is licensed under the [Apache License 2.0](LICENSE).
 
 ---
 
-*Keywords: TestRail, MCP, Model Context Protocol, LLM, AI, Claude, Cursor, Windsurf, Test Management, QA, Automation, Testing, API*
+<p align="center">
+  <b>TestRail MCP Server</b> · Built with the <a href="https://modelcontextprotocol.io">Model Context Protocol</a>
+</p>
+
+<p align="center">
+  <sub>Keywords: TestRail MCP Server, Model Context Protocol, TestRail API integration, AI test management, LLM testing tools, Claude TestRail, Cursor TestRail, Windsurf TestRail, test case automation, QA AI assistant, MCP server for testing, TestRail plugin, test run management, AI-powered QA</sub>
+</p>

package/dist/client/testrail.js

@@ -23,6 +23,23 @@ export class TestRailClient {
     async getCase(caseId) {
         return this.get(`${API_BASE_V2}/get_case/${caseId}`);
     }
+    async getCasesRecursively(projectId, sectionId, filter, excludedSectionNames) {
+        const sections = await this.getSections(projectId);
+        const sectionIds = this.getSubSectionIds(sections, sectionId, excludedSectionNames);
+        sectionIds.push(sectionId);
+        const promises = sectionIds.map(id => this.getCases(projectId, id, filter));
+        const results = await Promise.all(promises);
+        return results.flat();
+    }
+    getSubSectionIds(sections, parentId, excludedSectionNames) {
+        const children = sections.filter(s => s.parent_id === parentId);
+        const validChildren = children.filter(s => !excludedSectionNames?.includes(s.name));
+        let ids = validChildren.map(s => s.id);
+        for (const child of validChildren) {
+            ids = ids.concat(this.getSubSectionIds(sections, child.id, excludedSectionNames));
+        }
+        return ids;
+    }
     async getCases(projectId, sectionId, filter) {
         let url = `${API_BASE_V2}/get_cases/${projectId}`;
         if (sectionId) {
@@ -73,10 +90,10 @@ export class TestRailClient {
         return this.statusesPromise;
     }
     async getTemplates(projectId) {
-        if (!this.templatesPromiseMap.has(projectId)) {
-            this.templatesPromiseMap.set(projectId, this.get(`${API_BASE_V2}/get_templates/${projectId}`));
+        if (!this.templatesPromiseMap.has(projectId.toString())) {
+            this.templatesPromiseMap.set(projectId.toString(), this.get(`${API_BASE_V2}/get_templates/${projectId}`));
         }
-        return this.templatesPromiseMap.get(projectId);
+        return this.templatesPromiseMap.get(projectId.toString());
     }
     async updateCase(caseId, fields) {
         return this.post(`${API_BASE_V2}/update_case/${caseId}`, fields);
@@ -155,13 +172,26 @@ export class TestRailClient {
             headers,
             body,
         };
-        const response = await fetch(url, params);
-        if (!response.ok) {
-            let errorMessage = `TestRail: ${response.status} ${response.statusText}`;
-            const errorText = await response.text();
-            errorMessage += ` - ${errorText}`;
-            throw new Error(errorMessage);
+        console.error(`[TestRailClient] Executing ${method} request to ${endpoint}`);
+        const startTime = Date.now();
+        try {
+            const response = await fetch(url, params);
+            const duration = Date.now() - startTime;
+            console.error(`[TestRailClient] Received ${response.status} ${response.statusText} from ${method} ${endpoint} in ${duration}ms`);
+            if (!response.ok) {
+                let errorMessage = `TestRail API Error: ${response.status} ${response.statusText}`;
+                const errorText = await response.text();
+                errorMessage += ` - ${errorText}`;
+                console.error(`[TestRailClient] Error Details: ${errorMessage}`);
+                throw new Error(errorMessage);
+            }
+            return await response.json();
+        }
+        catch (error) {
+            if (error instanceof Error && !error.message.startsWith('TestRail API Error')) {
+                console.error(`[TestRailClient] Request Failed: ${method} ${endpoint} - ${error.message}`);
+            }
+            throw error;
         }
-        return await response.json();
     }
 }

package/dist/index.js

@@ -27,7 +27,7 @@ if (!TESTRAIL_INSTANCE_URL || !TESTRAIL_USERNAME || !TESTRAIL_API_KEY) {
 }
 const server = new McpServer({
     name: "TestRail MCP Server",
-    version: "1.3.1",
+    version: "1.5.0",
 });
 const client = new TestRailClient(TESTRAIL_INSTANCE_URL, TESTRAIL_USERNAME, TESTRAIL_API_KEY);
 const tools = [

package/dist/tools/add_attachment_to_run.js

@@ -5,7 +5,7 @@ import * as path from "path";
 import * as os from "os";
 import archiver from "archiver";
 const parameters = {
-    run_id: z.string().describe("The ID of the test run to attach the file to"),
+    run_id: z.number().describe("The ID of the test run to attach the file to"),
     file_path: z.string().describe("The path to the file or directory to attach. Directories will be automatically zipped."),
 };
 export const addAttachmentToRunTool = {
@@ -40,7 +40,7 @@ export const addAttachmentToRunTool = {
             isTemporary = true;
         }
         try {
-            const result = await client.addAttachmentToRun(Number(run_id), uploadPath, filename);
+            const result = await client.addAttachmentToRun(run_id, uploadPath, filename);
             return AttachmentSchema.parse(result);
         }
         finally {

package/dist/tools/add_run.js

@@ -1,17 +1,17 @@
 import { z } from "zod";
 import { RunSchema } from "../types/testrail.js";
 const parameters = {
-    project_id: z.string().describe("The ID of the project. Use get_projects to find available projects"),
+    project_id: z.number().describe("The ID of the project. Use get_projects to find available projects"),
     name: z.string().optional().describe("The name of the test run"),
     description: z.string().optional().describe("The description of the test run"),
-    case_ids: z.array(z.number()).describe("Array of case IDs to include in the run. After creating the run, use get_tests with the returned run_id to retrieve test IDs for result submission")
+    case_ids: z.array(z.number()).min(1).describe("Array of case IDs to include in the run. After creating the run, use get_tests with the returned run_id to retrieve test IDs for result submission")
 };
 export const addRunTool = {
     name: "add_run",
     description: "Create a new test run in TestRail",
     parameters,
     handler: async ({ project_id, ...fields }, client) => {
-        const caseData = await client.getCase(String(fields.case_ids[0]));
+        const caseData = await client.getCase(fields.case_ids[0]);
         const params = { suite_id: caseData.suite_id, include_all: false, ...fields };
         const run = await client.addRun(project_id, params);
         return RunSchema.parse(run);

package/dist/tools/create_case.js

@@ -1,6 +1,6 @@
 import { z } from "zod";
 const parameters = {
-    section_id: z.string().describe("The ID of the section where the case should be created. Use get_sections to find available sections"),
+    section_id: z.number().describe("The ID of the section where the case should be created. Use get_sections to find available sections"),
     title: z.string().describe("The title of the test case"),
     fields: z.record(z.string(), z.any()).optional().describe("Optional fields for the test case. First use get_templates to discover available templates, then get_case_fields to see available fields for your template. Example: {\"priority_id\": 2, \"template_id\": 1, \"custom_automation_priority\": 1}"),
 };

package/dist/tools/get_case.js

@@ -1,5 +1,6 @@
 import { z } from "zod";
 import { processCustomFields } from "../utils/mapper.js";
+import { LabelSchema } from "../types/testrail.js";
 const parameters = {
     case_id: z.string().describe("The ID of the test case (e.g. '123' or 'C123')"),
 };
@@ -8,10 +9,11 @@ export const getCaseTool = {
     description: "Get detailed information about a test case including its custom fields",
     parameters,
     handler: async ({ case_id }, client) => {
-        const id = case_id.toUpperCase().startsWith("C") ? case_id.substring(1) : case_id;
+        const idString = case_id.toUpperCase().startsWith("C") ? case_id.substring(1) : case_id;
+        const id = Number(idString);
         const testCase = await client.getCase(id);
         const [section, caseTypes, priorities, caseFields] = await Promise.all([
-            client.getSection(testCase.section_id.toString()),
+            client.getSection(Number(testCase.section_id)),
             client.getCaseTypes(),
             client.getPriorities(),
             client.getCaseFields()
@@ -25,7 +27,7 @@ export const getCaseTool = {
             section: section.name,
             type: caseType ? caseType.name : "Unknown",
             priority: priority ? priority.name : "Unknown",
-            labels: testCase.labels || [],
+            labels: (testCase.labels || []).map((label) => LabelSchema.parse(label)),
             references: testCase.refs,
             updated_on: testCase.updated_on,
             ...customFields

package/dist/tools/get_cases.js

@@ -1,7 +1,11 @@
 import { z } from "zod";
 const parameters = {
-    project_id: z.string().describe("The ID of the project. Use get_projects to find available projects"),
-    section_id: z.string().optional().describe("Optional section ID to filter cases by section. Use get_sections to find available sections"),
+    project_id: z.number().describe("The ID of the project. Use get_projects to find available projects"),
+    section: z.object({
+        id: z.number(),
+        recursive: z.boolean().optional().default(false).describe("If true, fetches cases from the section and all its child sections"),
+        excludes: z.array(z.string()).optional().describe("List of section names to exclude from the recursive search"),
+    }).optional().describe("Section filter configuration. Use get_sections to find available sections"),
     filter: z.record(z.string(), z.string()).optional().describe("Optional API-side filters (more efficient for large datasets). Supported: priority_id, type_id, created_by, updated_by, milestone_id, refs, created_after, created_before, updated_after, updated_before. Use comma-separated values for IDs. Example: {\"priority_id\": \"1,2\", \"type_id\": \"3\"}"),
     where: z.record(z.string(), z.any()).optional().describe("Optional client-side filter for any field including custom fields (filters after fetching all cases). Supports exact value matching. Example: {\"custom_automation_status\": 1, \"priority_id\": 2}"),
     fields: z.array(z.string()).optional().describe("Additional fields to include in response beyond id, title, and suite_id. Use get_case_fields to see available fields. Example: [\"priority_id\", \"type_id\", \"custom_automation_status\"]"),
@@ -10,8 +14,14 @@ export const getCasesTool = {
     name: "get_cases",
     description: "Get all test cases for a project. Filter by section, API params (priority, type), or any field including custom fields via 'where'. Returns case IDs, titles, and any additional requested fields.",
     parameters,
-    handler: async ({ project_id, section_id, filter, where, fields }, client) => {
-        let cases = await client.getCases(project_id, section_id, filter);
+    handler: async ({ project_id, section, filter, where, fields }, client) => {
+        let cases;
+        if (section?.recursive) {
+            cases = await client.getCasesRecursively(project_id, section.id, filter, section.excludes);
+        }
+        else {
+            cases = await client.getCases(project_id, section?.id, filter);
+        }
         // Client-side filtering for custom fields and other unsupported API filters
         if (where) {
             cases = cases.filter(c => {

package/dist/tools/get_sections.js

@@ -1,7 +1,7 @@
 import { z } from "zod";
 import { SectionSchema } from "../types/testrail.js";
 const parameters = {
-    project_id: z.string().describe("The ID of the project. Use get_projects to find available projects"),
+    project_id: z.number().describe("The ID of the project. Use get_projects to find available projects"),
 };
 export const getSectionsTool = {
     name: "get_sections",

package/dist/tools/get_templates.js

@@ -1,7 +1,7 @@
 import { z } from "zod";
 import { TemplateSchema } from "../types/testrail.js";
 const parameters = {
-    project_id: z.string().describe("The ID of the project. Use get_projects to find available projects"),
+    project_id: z.number().describe("The ID of the project. Use get_projects to find available projects"),
 };
 export const getTemplatesTool = {
     name: "get_templates",

package/dist/tools/update_case.js

@@ -8,7 +8,8 @@ export const updateCaseTool = {
     description: "Update a test case in TestRail. Supports partial updates - only specify the fields you want to change",
     parameters,
     handler: async ({ case_id, fields }, client) => {
-        const id = case_id.toUpperCase().startsWith("C") ? case_id.substring(1) : case_id;
+        const idString = case_id.toUpperCase().startsWith("C") ? case_id.substring(1) : case_id;
+        const id = Number(idString);
         const updatedCase = await client.updateCase(id, fields);
         return {
             success: true,

package/dist/tools/update_cases.js

@@ -1,6 +1,6 @@
 import { z } from "zod";
 const parameters = {
-    case_ids: z.array(z.number()).describe("Array of case IDs to update (e.g. [123, 456, 789])"),
+    case_ids: z.array(z.number()).min(1).describe("Array of case IDs to update (e.g. [123, 456, 789])"),
     fields: z.record(z.string(), z.any()).describe("Object containing fields to update for ALL specified cases. Use get_case_fields to see available fields. Example: {\"priority_id\": 2, \"type_id\": 1}"),
 };
 export const updateCasesTool = {
@@ -8,7 +8,7 @@ export const updateCasesTool = {
     description: "Bulk update multiple test cases with the same field values. More efficient than calling update_case multiple times",
     parameters,
     handler: async ({ case_ids, fields }, client) => {
-        const caseData = await client.getCase(String(case_ids[0]));
+        const caseData = await client.getCase(case_ids[0]);
         const updatedCases = await client.updateCases(caseData.suite_id, case_ids, fields);
         return {
             success: true,

package/dist/types/testrail.js

@@ -18,6 +18,9 @@ export const CaseFieldSchema = z.object({
     include_all: z.boolean(),
     configs: z.array(CaseFieldConfigSchema),
 });
+export const LabelSchema = z.object({
+    title: z.string(),
+});
 export const CaseSchema = z.object({
     id: z.number(),
     title: z.string(),
@@ -31,7 +34,7 @@ export const CaseSchema = z.object({
     updated_on: z.number(),
     estimate: z.string().nullable(),
     suite_id: z.number(),
-    labels: z.array(z.any()),
+    labels: z.array(LabelSchema),
 }).loose();
 export const SectionSchema = z.object({
     id: z.number(),

package/dist/utils/sanitizer.js

@@ -1,5 +1,5 @@
 /**
- * Recursively ыtrips inline style attributes from HTML tags contained in string values
+ * Recursively strips inline style attributes from HTML tags contained in string values
  * in an object or array. Useful for cleaning up TestRail markdown content before sending
  * to LLMs.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uarlouski/testrail-mcp-server",
-  "version": "1.3.1",
+  "version": "1.5.0",
   "description": "Model Context Protocol (MCP) server for TestRail integration, enabling LLMs to fetch test cases and metadata.",
   "main": "dist/index.js",
   "bin": {