Zebrunner

You can connect your developer or QA workflow to Zebrunner through an MCP server that exposes test case, suite, and execution data to AI assistants. It lets you retrieve test assets, analyze coverage, generate test code, and surface quality insights directly from natural language prompts, streamlining collaboration between your Zebrunner data and your AI-enabled workflows.

How to use

You will run the MCP server in your environment and connect it to your AI assistant client. Start by choosing one of the available execution methods: run the server locally in development or production mode, or integrate directly into your Claude Desktop or Claude Code setup. Once running, you can request actions such as retrieving test cases, analyzing coverage, generating test code, and obtaining launch analyses. Use natural language prompts to drive the tools and workflows described in this guide.

How to install

Prerequisites: you need Node.js 18 or newer and npm. You also require access to a Zebrunner instance with API credentials.

# Step 1: Get the code
# Option A: Clone from repository (recommended)
git clone https://github.com/maksimsarychau/mcp-zebrunner.git
cd mcp-zebrunner

# Step 2: Install dependencies
npm install

# Step 3: Configure your Zebrunner connection
# Create a .env file in the project folder with your Zebrunner details

Create a .env file with these values (replace placeholders with your real data):

# 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

Additional setup and verification

Step 4: Build the project and verify the setup by checking the health endpoint.

npm run build
npm run test:health

Available tools

get_test_case_by_key

Get detailed test case information by key.

get_test_cases_advanced

Advanced filtering for test cases with automation states and dates.

get_test_cases_by_automation_state

Filter test cases by their automation state.

get_test_case_by_title

Search test cases by title with partial matching.

get_test_case_by_filter

Filter test cases by suite, dates, priority, and automation state.

get_automation_states

List available automation states.

get_automation_priorities

List available priorities with IDs.

get_all_tcm_test_cases_by_project

Get all test cases for a project with pagination.

get_all_tcm_test_cases_with_root_suite_id

Get all test cases with their root suite information.

list_test_suites

List test suites for a project with pagination.

get_suite_hierarchy

Show the hierarchical tree of test suites.

get_root_suites

Get top-level test suites for a project.

get_all_subsuites

Get all subsuites from a root suite.

get_tcm_suite_by_id

Find details for a specific test suite by ID.

get_tcm_test_suites_by_project

List all suites for a project with hierarchy.

get_root_id_by_suite_id

Find the root suite for a given suite ID.

get_test_coverage_by_test_case_steps_by_key

Analyze coverage for a test case against code steps.

get_enhanced_test_coverage_with_rules

Rules-based analysis for test coverage.

analyze_test_cases_duplicates

Find and group similar test cases by step similarity.

analyze_test_cases_duplicates_semantic

Semantic analysis with advanced step clustering.

generate_draft_test_by_key

Generate test code from a test case with framework detection.

validate_test_case

Quality validation with improvement suggestions.

improve_test_case

Provide targeted improvements for a test case.

get_launch_details

Get comprehensive information about a launch.

get_launch_summary

Provide a quick overview of a launch.

get_all_launches_for_project

List all launches for a project with pagination.

get_all_launches_with_filter

Filter launches by milestone or build.

generate_weekly_regression_stability_report

Weekly report on regression stability with detailed output.

analyze_test_failure

Deep forensic analysis of a failed test including logs and recommendations.

get_test_execution_history

Track execution trends across launches and compare with past runs.

detailed_analyze_launch_failures

Advanced analysis of launch failures with Jira-ready output.

download_test_screenshot

Download protected screenshots for a test from Zebrunner.

analyze_screenshot

Visual analysis of screenshots with OCR and UI detection.

get_platform_results_by_period

Get test results by platform and time period.

get_top_bugs

Identify the most frequent defects.

get_bug_review

Detailed review of bugs with failure details.

get_bug_failure_info

Failure information by hashcode.

get_project_milestones

List available milestones for a project.

get_available_projects

Discover all accessible projects.

test_reporting_connection

Test API connectivity to Zebrunner.

list_test_runs

Fetch and filter public API test runs.

get_test_run_by_id

Get detailed information for a specific test run.

list_test_run_test_cases

Show test cases within a specific run.

get_test_run_result_statuses

List configured result statuses for a project.

get_test_run_configuration_groups

Show configuration options for a project.

analyze_test_failure

Deep forensic analysis of failed tests with AI insights.