Zebrunner MCP Server

MCP开发工具

提供方 maksimsarychau

开发工具 未标注 Token 社区 / 第三方

Integrates with Zebrunner Test Case Management to help QA teams manage test cases, test suites, and test execution data through AI assistants. Features intelligent validation, automated test code generation, and comprehensive reporting capabilities.

一句话选型结论

按资料字段整理

Zebrunner MCP Server 属于开发工具类 MCP 服务器,传输方式未标注,Token,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权Token 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zebrunner MCP Server当前 未标注 未标注 支持远程部署 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方maksimsarychau上游标注的维护方 maksimsarychau
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

90.5 KB
来自项目仓库与上游目录的原文,未做删改

Advanced Zebrunner MCP Server

A Model Context Protocol (MCP) server that brings advanced analytics, reporting, failure forensics, and safe TCM mutations to Zebrunner. Designed to coexist with the official Zebrunner MCP (beta) — see the "Dual-MCP setup" section below.

> Tool naming: every tool on this server is registered under the canonical adv_ form (e.g. adv_create_test_case, adv_list_test_runs) so it never collides with the official Zebrunner MCP. The legacy names are kept as deprecated aliases so prompts/scripts that called the old names continue to work for now; aliases will be removed in the next major release.

> 🆕 v9.4.4 — Test-run metadata agent UX: post-mutation steering hints (discover env/config before update; import does not set badges); dual-MCP routing resource for environments vs Build/Platform; richer tool-intel for adv_manage_test_run. Builds on v9.4.3 env contract — see change-logs.md.
>
> v9.4.3 — adv_prepare_jira_automation_plan + /jira-automation-plan prompt: Zebrunner suite → structured Jira plan; adv_manage_test_run Public API environment as { name } / { id }. See change-logs.md, TEST_PROMPTS.md §20.
>
> v9.3.1 — TCM pagination fixes: correct get_all token walks, root_suite_id subtree scoping, honest bulk metadata. See PUBLIC_API_PAGINATION.md and change-logs.md.
>
> v9.3.0 — Multi-PR / period test impact: change_batches[], /test-impact-period, extended /test-impact. See TEST_IMPACT_WORKFLOW.md and TEST_IMPACT_PR_PERIOD_DESIGN.md.
>
> 🆕 v9.2.7 — New adv_scaffold_test_case wizard (hybrid form/conversational) to author test cases from best practices with an automatic warn-only similar-case check, plus optional projectAliases in zebrunner-config.json so tools accept short names as well as Zebrunner project keys. See release notes.
>
> 🆕 v9.2.5 — adv_get_test_authoring_trend (TAM template 7) completes 22/22 dashboard widget MCP coverage. Hub tools, pass-rate views, period modes. See TEST_PROMPTS.md §18 and change-logs.md.

> v9.2.1 — LLM-visible metrics (include_call_metrics, session breakdown), compact expansion (+19 tools), format/truncation bugfixes. See Token efficiency guide and change-logs.md.

> v9.2.0 — Opt-in token/cost optimizations: format:'compact', detail:'summary', adv_batch_get_test_cases, report inline:false. Defaults unchanged. See change-logs.md.

> v9.1.0 — Launch mutations: adv_rerun_launch_failures, adv_start_launch (Jenkins Build Now), plus /relaunch-regression-failures and /feature-scoped-launch prompts. See GitHub Release v9.1.0.
>
> 📖 Need help with installation? Check out our Step-by-Step Install Guide for detailed setup instructions.
>
> 🚀 Installing via npm? See our MCP NPM Installation Guide for Claude Desktop, Cursor, IntelliJ IDEA, and ChatGPT Desktop configuration.
>
> 📚 Test vs Test Case vs Launch? See Terminology & Glossary — definitions, counting rules, and how metrics are calculated.

🔥 Why This Server

This is the Advanced Zebrunner MCP Server — built to go well beyond basic test case management and help QA teams work smarter and faster with AI. Compared to the official Zebrunner MCP (beta, ~70 tools spanning Public REST + Reporting/TAM/Launcher), this server provides 76 registered adv_* tools (70 inline-regression suite + 6 handler-module tools; see tools.json) and is safe to run side-by-side with the official server:

  • Reporting & Analytics — dashboards, pass-rate trends, regression stability reports, runtime efficiency analysis, bug reviews, and weekly delta tracking
  • Test Coverage & Analysis — coverage gaps, automation readiness scoring, and cross-suite analysis
  • Intelligent Rules System — 3-tier quality rules with 100+ automated checkpoints for test case validation and improvement
  • Screenshot & Video Analysis — OCR, image processing, and video analysis powered by sharp, ffmpeg, and tesseract
  • MCP Resources & Prompts — @ context injection and / workflow commands for streamlined daily operations
  • Multi-Transport & Multi-Auth — STDIO, Streamable HTTP, self-service OAuth, Okta SSO, and token exchange (Modes 1–5)

📑 Table of Contents

  1. 🔥 Why This Server
  2. 🎯 What is this tool?
  3. 🧠 Intelligent Rules System
    - 3.1. What Makes This Tool Special
    - 3.2. How the Rules Work Together
    - 3.3. Why This Matters
    - 3.4. Customizing Rules for Your Project
  4. 📋 Prerequisites
  5. 🚀 Quick Start Guide
  6. 🔧 Usage Methods
    - 6.1. Method 1: Use with Claude Desktop/Code
    - 6.2. Method 2: Run as standalone server
    - 6.3. Method 3: Smart URL-Based Analysis 🚀
  7. 🛠️ Available Tools
    - 7.1. 📋 Test Case Management
    - 7.2. 🌳 Test Suite Hierarchy & Organization
    - 7.3. 🔧 Mutation Tools
    - 7.4. 🔍 Test Coverage & Analysis
    - 7.5. 🧪 Test Code Generation & Validation
    - 7.6. 🚀 Launch & Execution Management
    - 7.7. 📊 Reporting & Analytics
    - 7.8. 🏃 Test Run Management
    - 7.9. 🎯 Management-Focused Quick Commands
  8. 📎 MCP Resources & Prompts (NEW)
    - 8.1. Resources — @ Context Injection
    - 8.2. Prompts — / Workflow Commands
  9. 🎭 Role-Specific Prompts & Workflows
    - 9.1. 👩‍💻 Manual QA Engineers
    • Daily Test Case Review
    • Test Case Creation & Improvement
    • Test Suite Organization
    • Coverage Analysis
    • 9.2. 🤖 Test Automation Engineers & SDETs
    • Automation Readiness Assessment
    • Test Code Generation
    • Coverage Analysis & Validation
    • Framework Integration
    • Batch Automation Analysis
    • 9.3. 👨‍💻 Developers
    • Test Case Understanding
    • Implementation Validation
    • Code Generation for Testing
    • Bug Analysis
    • 9.4. 👔 Test Managers & Team Leads
    • Team Quality Metrics
    • Test Suite Analysis
    • Team Performance & Planning
    • Process Improvement
    • Reporting & Stakeholder Communication
    • 9.5. 🏢 Project Owners & Product Managers
    • Project Health Overview
    • Feature Testing Status
    • Quality Assurance Metrics
    • Risk Assessment
    • Planning & Resource Allocation
  10. 📖 Output Formats
  11. ⚙️ Configuration Options
  12. 🧪 Testing Your Setup
  13. 🔍 Troubleshooting
  14. 🎯 Example Workflows
  15. 🔧 Advanced Features
  16. 📚 Additional Documentation
  17. 🤝 Contributing
  18. 📄 License
  19. 🎉 You're Ready!

🎯 What is this tool?

This tool allows you to:

  • Retrieve test cases and test suites from Zebrunner
  • Analyze test coverage and generate test code
  • Get test execution results and launch details
  • Validate test case quality with automated checks using intelligent rules
  • Generate reports and insights from your test data
  • Improve test cases with AI-powered suggestions and automated fixes

All through natural language commands in AI assistants!

⬆️ Back to top

🧠 Intelligent Rules System

What Makes This Tool Special

Our MCP server includes a sophisticated 3-tier rules system that transforms how you work with test cases:

🎯 Test Case Review Rules (test_case_review_rules.md)

  • Purpose: Core quality standards and writing guidelines
  • What it does: Defines fundamental principles for writing high-quality test cases
  • Key areas: Independence, single responsibility, comprehensive preconditions, complete step coverage
  • Used by: adv_validate_test_case and adv_improve_test_case tools

✅ Test Case Analysis Checkpoints (test_case_analysis_checkpoints.md)

  • Purpose: Detailed validation checklist with 100+ checkpoints
  • What it does: Provides granular validation criteria for thorough test case analysis
  • Key areas: Structure validation, automation readiness, platform considerations, quality assurance
  • Used by: adv_validate_test_case for comprehensive scoring and issue detection

⚙️ MCP Zebrunner Rules (mcp-zebrunner-rules.md)

  • Purpose: Technical configuration for test generation and coverage analysis
  • What it does: Defines framework detection patterns, code templates, and coverage thresholds
  • Key areas: Framework detection, test generation templates, coverage thresholds, quality standards
  • Used by: adv_generate_draft_test_by_key and adv_get_enhanced_test_coverage_with_rules tools

How the Rules Work Together```mermaid

graph TD
A[Test Case] --> B[adv_validate_test_case]
B --> C[test_case_review_rules.md]
B --> D[test_case_analysis_checkpoints.md]
B --> E[Validation Result + Issues]

E --> F[adv_improve_test_case]
F --> G[AI-Powered Improvements]

A --> H[adv_generate_draft_test_by_key]
H --> I[mcp-zebrunner-rules.md]
H --> J[Generated Test Code]

A --> K[adv_get_enhanced_test_coverage_with_rules]
K --> I
K --> L[Coverage Analysis + Rules Validation]

### Why This Matters

1. **Consistency**: All team members follow the same quality standards
2. **Automation**: Reduce manual review time with automated validation
3. **Learning**: New team members learn best practices through AI feedback
4. **Customization**: Adapt rules to your project's specific needs
5. **Continuous Improvement**: AI suggests improvements based on proven patterns

### Customizing Rules for Your Project

You can customize any of the three rules files:```bash
# Copy default rules to customize
cp test_case_review_rules.md my-project-review-rules.md
cp test_case_analysis_checkpoints.md my-project-checkpoints.md
cp mcp-zebrunner-rules.md my-project-technical-rules.md

# Use custom rules in validation
"Validate test case PROJ-123 using custom rules from my-project-review-rules.md"

Example customizations:

  • Mobile projects: Add mobile-specific validation rules
  • API projects: Focus on API testing patterns and data validation
  • Different frameworks: Customize code generation templates
  • Company standards: Align with your organization's testing guidelines

⬆️ Back to top

📋 Prerequisites

What you need to know

  • Basic command line usage (opening terminal, running commands)
  • Your Zebrunner credentials (login and API token)
  • Basic understanding of test management (test cases, test suites)

Software requirements

  • Node.js 18 or newer - Download here
  • npm (comes with Node.js)
  • Access to a Zebrunner instance with API credentials

How to check if you have Node.js

Open your terminal/command prompt and run:```bash
node --version
npm --version


If you see version numbers, you're ready to go!

⬆️ Back to top

## 🚀 Quick Start Guide

> 💡 **Want more detailed instructions?** Check out our **More Detailed Step-by-step Install Guide** with troubleshooting tips and platform-specific instructions.

### Step 1: Get the code

Choose one of these methods:

#### Option A: Clone from repository (recommended)```bash
git clone https://github.com/maksimsarychau/mcp-zebrunner.git
cd mcp-zebrunner

Option B: Download and extract

Download the project files and extract them to a folder.

Step 2: Install dependencies```bash

npm install


### Step 3: Configure your Zebrunner connection

Create a `.env` file in the project folder with your Zebrunner details:```env
# Your Zebrunner instance URL (without trailing slash)
ZEBRUNNER_URL=https://your-company.zebrunner.com/api/public/v1

# Your Zebrunner login (usually your email)
ZEBRUNNER_LOGIN=your.email@company.com

# Your Zebrunner API token (get this from your Zebrunner profile)
ZEBRUNNER_TOKEN=your_api_token_here

# Optional: Enable debug logging (default: false)
DEBUG=false

# Optional: Enable intelligent rules system (auto-detected if rules file exists)
ENABLE_RULES_ENGINE=true

How to get your Zebrunner API token:

  1. Log into your Zebrunner instance
  2. Go to your profile settings
  3. Find the "API Access" section
  4. Generate a new API token
  5. Copy the token to your .env file

Step 4: Build the project```bash

npm run build


### Step 5: Test your connection```bash
npm run test:health

If you see "✅ Health check completed", you're ready to go!

🔄 Updating to New Version

Check current version```bash

Check your current version

npm run version

or manually check package.json

cat package.json | grep '"version"'


### Update steps```bash
# 1. Pull latest changes from master branch
git pull origin master

# 2. Install any new dependencies
npm install

# 3. Rebuild the project
npm run build

# 4. Test your connection (requires valid .env file)
npm run test:health

Important Notes:

  • ✅ Your .env file must be properly configured for the health check to work
  • ✅ Restart Claude Desktop/Code after updating to reload the MCP server
  • ✅ Check release notes for any breaking changes before updating

If the health check fails, verify your .env configuration and Zebrunner credentials.

⬆️ Back to top

🔧 Usage Methods

Method 1: Use with Claude Desktop/Code (Recommended)

Add this configuration to your Claude Desktop or Claude Code settings. Important: You must use the full absolute path to your project folder.```json
{
"mcpServers": {
"mcp-zebrunner": {
"command": "node",
"args": ["/full/absolute/path/to/mcp-zebrunner/dist/server.js"],
"env": {
"ZEBRUNNER_URL": "https://your-company.zebrunner.com/api/public/v1",
"ZEBRUNNER_LOGIN": "your.email@company.com",
"ZEBRUNNER_TOKEN": "your_api_token_here",
"DEBUG": "false",
"ENABLE_RULES_ENGINE": "true",
"DEFAULT_PAGE_SIZE": "100",
"MAX_PAGE_SIZE": "100"
}
}
}
}


**Example paths:**

- **Windows:** `C:\\Users\\YourName\\Projects\\mcp-zebrunner\\dist\\server.js`
- **macOS/Linux:** `/Users/YourName/Projects/mcp-zebrunner/dist/server.js`

### Alternative: Command Line Integration (Claude Code)

You can also add the server using the command line:```bash
claude mcp add mcp-zebrunner \
  --env ZEBRUNNER_URL="https://your-company.zebrunner.com/api/public/v1" \
  --env ZEBRUNNER_LOGIN="your.email@company.com" \
  --env ZEBRUNNER_TOKEN="your_api_token_here" \
  --env DEBUG="false" \
  --env ENABLE_RULES_ENGINE="true" \
  -- node /full/absolute/path/to/mcp-zebrunner/dist/server.js

Important: Replace /full/absolute/path/to/mcp-zebrunner/ with the actual full path to your project folder.

Method 2: Run as standalone server

Development mode (with auto-reload)```bash

npm run dev


#### Production mode```bash
npm start

Method 3: Smart URL-Based Analysis 🚀

NEW in v5.4.1+: Claude can automatically detect Zebrunner URLs and analyze them with optimal settings!

Just paste a Zebrunner URL in your conversation, and Claude will automatically:

  • Parse the URL to extract project, launch, and test IDs
  • Call the appropriate analysis tool
  • Use recommended settings (videos, screenshots, AI analysis enabled)

📋 Supported URL Patterns

1. Test Analysis URLs```
https://your-workspace.zebrunner.com/projects/PROJECT/automation-launches/LAUNCH_ID/tests/TEST_ID


**What happens:**

- Claude automatically calls `adv_analyze_test_failure`
- Extracts: `projectKey`, `testRunId` (launch ID), `testId`
- Enables: `includeVideo: true`, `analyzeScreenshotsWithAI: true`, all diagnostics

**Example:**```
User: "Analyze https://your-workspace.zebrunner.com/projects/MCP/automation-launches/120911/tests/5455386"

Claude automatically calls:
{
  projectKey: "MCP",
  testRunId: 120911,
  testId: 5455386,
  includeVideo: true,
  analyzeScreenshotsWithAI: true,
  includeLogs: true,
  includeScreenshots: true,
  analyzeSimilarFailures: true,
  screenshotAnalysisType: "detailed",
  format: "detailed"
}

2. Launch Analysis URLs```
https://your-workspace.zebrunner.com/projects/PROJECT/automation-launches/LAUNCH_ID


**What happens:**

- Claude automatically calls `adv_detailed_analyze_launch_failures`
- Extracts: `projectKey`, `testRunId` (launch ID)
- Enables: `includeScreenshotAnalysis: true`, comprehensive analysis

**Example:**```
User: "Analyze https://your-workspace.zebrunner.com/projects/MCP/automation-launches/120911"

Claude automatically calls:
{
  projectKey: "MCP",
  testRunId: 120911,
  filterType: "without_issues",
  includeScreenshotAnalysis: true,
  screenshotAnalysisType: "detailed",
  format: "summary",
  executionMode: "sequential"
}

✨ Advanced Usage

Override Default Settings

Claude understands natural language overrides:```
User: "Analyze https://...url... but without screenshots"
→ Claude sets: analyzeScreenshotsWithAI: false

User: "Analyze https://...url... in jira format"
→ Claude sets: format: "jira"

User: "Quick analysis of https://...url..."
→ Claude sets: format: "summary", screenshotAnalysisType: "basic"


**Multiple URLs**

Analyze multiple tests/launches in one request:```
User: "Compare these failures:
https://your-workspace.zebrunner.com/projects/MCP/automation-launches/120911/tests/5455386
https://your-workspace.zebrunner.com/projects/MCP/automation-launches/120911/tests/5455390"

→ Claude analyzes both sequentially and compares results

Cross-Workspace Support

⚠️ URLs from different workspaces will show a warning but still attempt analysis:```
User: "Analyze https://other-workspace.zebrunner.com/..."
→ Claude warns: "URL is from 'other-workspace.zebrunner.com' but configured workspace is 'your-workspace.zebrunner.com'"
→ Proceeds with analysis using available credentials


#### 📖 URL Pattern Reference

| Component   | Example                        | Extracted As    | Used In Tool                    |
| ----------- | ------------------------------ | --------------- | ------------------------------- |
| Workspace   | `your-workspace.zebrunner.com` | Validation only | N/A                             |
| Project Key | `MCP`                          | `projectKey`    | All tools                       |
| Launch ID   | `120911`                       | `testRunId`     | All tools                       |
| Test ID     | `5455386`                      | `testId`        | `adv_analyze_test_failure` only |

#### 🎯 Why Use URL-Based Analysis?

✅ **Faster**: No need to manually specify IDs
✅ **Convenient**: Copy-paste URLs directly from Zebrunner UI
✅ **Optimized**: Automatic use of recommended settings
✅ **Smart**: Claude detects intent and adjusts parameters
✅ **Flexible**: Natural language overrides work seamlessly

#### 💡 Pro Tips

1. **Direct from Zebrunner**: Copy URL directly from your browser while viewing a test/launch
2. **Batch Analysis**: Paste multiple URLs separated by newlines
3. **Custom Settings**: Add natural language instructions to override defaults
4. **Quick Checks**: URLs work great for quick "what happened here?" questions
5. **Reports**: Combine with format requests: "Generate JIRA ticket for https://...url..."

⬆️ Back to top

## 🤝 Dual-MCP setup (official `zebrunner` + Advanced)

Zebrunner now offers an **official hosted MCP** (beta) at
`https://{workspace}.zebrunner.com/api/mcp`. It is safe to run **both** servers
in the same Cursor / Claude session: every tool on this server is exposed under
the `adv_` prefix, so it never collides with the official tools.

Example `.cursor/mcp.json`:```json
{
  "mcpServers": {
    "zebrunner": {
      "url": "https://your-workspace.zebrunner.com/api/mcp",
      "headers": {
        "X-Zebrunner-Username": "your.name@company.com",
        "X-Zebrunner-Api-Token": "<your-zebrunner-api-token>"
      }
    },
    "mcp-zebrunner": {
      "command": "npx",
      "args": ["-y", "mcp-zebrunner"],
      "env": {
        "ZEBRUNNER_URL": "https://your-workspace.zebrunner.com/api/public/v1",
        "ZEBRUNNER_LOGIN": "your.name@company.com",
        "ZEBRUNNER_TOKEN": "<your-zebrunner-api-token>"
      }
    }
  }
}

Rule of thumb when both are connected:

Use zebrunner (official) for Use mcp-zebrunner (Advanced) for
list_projects, shared steps, test run replace/close, custom field create Failure forensics, runtime + flakiness analytics
Server-side filter DSL; file upload + screenshot content in triage Reporting, dashboards, regression analyzers
Bulk launch/test comments, issue linking, launcher/preset CRUD, launch_tests Preview/confirm TCM mutations; Jenkins Build Now / rerun failures

Inside chat, ask adv_about_mcp_tools with mode: "routing" or open the
zebrunner://mcp-routing resource for the full live-generated diff and routing table.

🛠️ Available Tools

Once connected, you can use these tools through natural language in your AI assistant. This section highlights all 76 adv_* tools (see tools.json) organized by category. For the complete catalog with natural-language examples for every tool, see TOOLS_CATALOG.md.

Dashboard widgets: All 22 Zebrunner dashboard templates have MCP coverage (v9.2.5). See docs/TEST_PROMPTS.md §18 for example prompts and npm run test:api verification.

Token-efficient reads

Large TCM exports can consume significant context. Use these opt-in parameters (defaults stay backward-compatible). Full guide: docs/TOKEN_EFFICIENCY.md.

Technique Example When to use
format: 'compact' adv_get_all_tcm_test_cases_by_project with format:'compact' Minified JSON (~22% smaller than pretty json)
detail: 'summary' adv_get_test_cases_by_suite_smart with detail:'summary' After filtering — returns id, key, title, priority, automationState, webUrl only
adv_batch_get_test_cases { case_keys: ["MCP-1","MCP-2"], detail:"summary", format:"compact" } Fetch a shortlist without N round-trips
adv_generate_report inline: false Writes HTML/PNG to disk, returns paths Huge dashboards in chat clients
count_only: true Any bulk TCM/suite read Metrics without payload
Env flags (off) MCP_COMPACT_DEFAULTS=true, MCP_SUMMARY_DEFAULTS=true Server-wide default flips after eval passes

Workflow: list/filter with detail:'summary' + format:'compact' → adv_get_test_case_by_key for full body (steps, preconditions) before create/update.

Example prompts for your assistant:

  • "List test cases in project MCP with summary detail and compact JSON."
  • "Fetch MCP-1 and MCP-2 in one batch call with summary and compact format."
  • "Generate a quality dashboard for MCP with inline false — save to disk."

> Tool naming: All tools are exposed as adv_ (e.g. adv_get_test_case_by_key). Use these names in prompts, scripts, and when both the official and Advanced MCP are connected. Legacy short names (get_test_case_by_key, etc.) are deprecated and only registered when ZEBRUNNER_REGISTER_LEGACY_ALIASES=true.

📋 Test Case Management

Core Test Case Tools

Tool Description Example Usage Best For
adv_get_test_case_by_key Get detailed test case information "Get test case MCP-123 details" All roles
adv_batch_get_test_cases Fetch multiple cases by key (partial success) "Get MCP-1 and MCP-2 with summary detail" All roles
adv_get_test_cases_advanced Advanced filtering with automation states, dates "Get test cases created after 2025-01-01 with automation state 'Manual'" QA, SDETs
adv_get_test_cases_by_automation_state Filter by specific automation states "Show me all 'Not Automated' test cases in project MCP" SDETs, Managers
adv_get_test_case_by_title Search test cases by title (partial match) "Find test cases with title containing 'login functionality'" All roles
adv_get_test_case_by_filter Advanced filtering by suite, dates, priority, automation state "Get test cases from suite 491 created after 2025-01-01 with high priority" QA, Managers
adv_get_automation_states List available automation states "What automation states are available for project MCP?" All roles
adv_get_automation_priorities List available priorities with IDs "Show me all priority levels for project MCP" All roles

Batch Test Case Operations

Tool Description Example Usage Best For
adv_get_all_tcm_test_cases_by_project Get ALL test cases (handles pagination) "Get all test cases for project MCP" Managers, Leads
adv_get_all_tcm_test_cases_with_root_suite_id All test cases with hierarchy info "Get all test cases with their root suite information" Analysts
adv_get_test_cases_by_suite_smart Smart suite test case retrieval with root/child auto-detection "Get test cases from suite 18824 in project MCP using smart mode" QA, Analysts

Test Case Change History

Most test case tools support optional change history enrichment — fetching the audit log of modifications for each test case. This is useful for understanding when steps were changed, when automation state transitioned, or when a test case was deprecated.

Parameter · Type · Default · Description
include_history · boolean · false · Attach a history array of parsed change entries to each test case
history_filter · steps_only · events_only · all · steps_only · Filter: step/precondition diffs only, lifecycle events only, or all changes
history_limit · number (1–100) · 20 · Max history entries per test case

Supported on: adv_get_test_case_by_key, adv_get_test_cases_advanced, adv_get_test_cases_by_automation_state, adv_get_test_case_by_title, adv_get_test_case_by_filter, adv_get_all_tcm_test_cases_by_project, adv_get_test_cases_by_suite_smart

Example prompts:

  • "Get test case MCP-29 with change history" → sets include_history=true
  • "Show me MCP-29 history, events only" → sets include_history=true, history_filter='events_only'
  • "Get all automated test cases with their last 5 changes" → sets include_history=true, history_limit=5

Detected events: became_automated, became_manual, became_deprecated, became_undeprecated, steps_changed, preconditions_changed, postconditions_changed, and dynamically generated became_ for any project-specific automation state.

🌳 Test Suite Hierarchy & Organization

Suite Management

Tool Description Example Usage Best For
adv_list_test_suites List suites with pagination "List test suites for project MCP" All roles
adv_get_suite_hierarchy Hierarchical tree view "Show me the hierarchy of test suites with depth 3" Managers, QA
adv_get_root_suites Get top-level suites "Show me all root suites for project MCP" Managers
adv_get_all_subsuites Get all child suites "Get all subsuites from root suite 18697" QA, Analysts

Suite Analysis Tools

Tool Description Example Usage Best For
adv_get_tcm_suite_by_id Get suite by ID (simple: fast direct API, full: hierarchy-enriched) "Show me suite 20421 in project MCP" All roles

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Zebrunner MCP Server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Zebrunner MCP Server 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zebrunner MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zebrunner MCP Server 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Zebrunner MCP Server 能提供哪些能力?

资料显示能力标签包括 Token认证、开发工具、命令行工具。具体工具清单以官方文档为准。

Zebrunner MCP Server 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Zebrunner MCP Server 是本地还是远程?

它是远程端点,连服务地址即可。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。