Advanced Zebrunner MCP Server

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.5 — Artifacts you can actually read: new read-only tools `adv_list_test_artifacts`, `adv_get_file_metadata`, `adv_download_artifact` (page source XML, logs, links attached by automation). Failure analysis (`adv_analyze_test_failure`, `adv_detailed_analyze_launch_failures`, `adv_analyze_test_execution_video`) now lists artifacts and reads the failure page source (crash/permission dialog, keyboard, locator present or missing) to refine the classification. adv_download_test_screenshot no longer fails on XML. Plus API gap fixes and a new npm run self-check regression safety net. See change-logs.md.

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](docs/TEST_PROMPTS.md#18-dashboard-widgets-22-templates--v925) 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](docs/TOKEN_EFFICIENCY.md) 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](INSTALL-GUIDE.md) for detailed setup instructions.

🚀 Installing via npm? See our [MCP NPM Installation Guide](MCP_NPM_INSTALLATION_GUIDE.md) for Claude Desktop, Cursor, IntelliJ IDEA, and ChatGPT Desktop configuration.

📚 Test vs Test Case vs Launch? See [Terminology & Glossary](docs/TERMINOLOGY.md) — 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](#-reporting--analytics) — dashboards, pass-rate trends, regression stability reports, runtime efficiency analysis, bug reviews, and weekly delta tracking
• [Test Coverage & Analysis](#-test-coverage--analysis) — coverage gaps, automation readiness scoring, and cross-suite analysis
• [Intelligent Rules System](#-intelligent-rules-system) — 3-tier quality rules with 100+ automated checkpoints for test case validation and improvement
• [Screenshot & Video Analysis](#-test-code-generation--validation) — OCR, image processing, and video analysis powered by sharp, ffmpeg, and tesseract
• [MCP Resources & Prompts](#-mcp-resources--prompts-new) — @ context injection and / workflow commands for streamlined daily operations
• [Multi-Transport & Multi-Auth](#-usage-methods) — 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

1. 📋 Prerequisites
2. 🚀 Quick Start Guide
3. 🔧 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 🚀

1. 🛠️ 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

1. 📎 MCP Resources & Prompts (NEW)

• 8.1. Resources — @ Context Injection
• 8.2. Prompts — / Workflow Commands

1. 🎭 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

1. 📖 Output Formats
2. ⚙️ Configuration Options
3. 🧪 Testing Your Setup
4. 🔍 Troubleshooting
5. 🎯 Example Workflows
6. 🔧 Advanced Features
7. 📚 Additional Documentation
8. 🤝 Contributing
9. 📄 License
10. 🎉 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

graph TD

A[Test Case] --> B[adv_validate_test_case] B --> C[test_case