Zebrunner MCP Server

📋 List test suites for a project (✅ Verified Working)

🔍 Get detailed test case by key (✅ Verified Working)

📋 Get all subsuites from a root suite as flat list with pagination

📊 Advanced test case retrieval with filtering and pagination (✨ Enhanced with automation state and date filtering) ⚠️ IMPORTANT: Use 'suite_id' for direct parent suites, 'root_suite_id' for root suites that contain sub-suites. 💡 TIP: Use 'get_test_cases_by_suite_smart' for automatic suite type detection!

🌳 Get hierarchical test suite tree with configurable depth

🤖 Get test cases filtered by automation state (💡 Use get_automation_states to see available states)

🔧 Get available automation states for a project (names and IDs)

🔍 Get test cases by title using partial match search with pagination support

🔍 Get test cases using advanced filtering options with exact matching

🎯 Get available priorities for a project (names and IDs)

🔍 Analyze test case coverage against actual implementation with recommendations

🧪 Generate draft test code from Zebrunner test case with intelligent framework detection

🔍 Enhanced test coverage analysis with configurable rules validation and quality scoring

📋 Get TCM test suites by project with pagination (Java methodology)

📋 Get ALL TCM test case suites by project using comprehensive pagination

🌳 Get root suites (suites with no parent) from project

🔍 Find TCM suite by ID with comprehensive search

📋 Get ALL TCM test cases by project using comprehensive pagination

🌳 Get ALL TCM test cases enriched with root suite ID information

🔍 Get root suite ID for a specific suite ID

🧠 Smart test case retrieval by suite ID - automatically detects if suite is root suite and uses appropriate filtering with enhanced pagination

🚀 Get comprehensive launch details including test sessions (uses new reporting API with enhanced authentication)

📊 Get lightweight launch test summary with statistics (auto-paginated, token-optimized)

📋 Get quick launch summary without detailed test sessions (uses new reporting API)

🔍 Deep forensic analysis of failed test including logs, screenshots, error classification, and similar failures. 💡 NEW: Compare with last passed execution to see what changed! 💡 TIP: Can be auto-invoked from Zebrunner test URLs like: https://workspace.zebrunner.com/projects/PROJECT/automation-launches/LAUNCH_ID/tests/TEST_ID

📊 Get execution history for a test across multiple launches - shows pass/fail history, last passed execution, and pass rate

📸 Download test screenshot with authentication from Zebrunner

🔍 Analyze test screenshot with OCR and visual analysis - returns image to Claude Vision for detailed analysis

🎬 Download and analyze test execution video with Claude Vision - extracts frames, compares with test case, and predicts if failure is bug or test issue. NEW: Analysis depth modes (quick/standard/detailed), parallel frame extraction, similar failures search, and historical trends analysis!

🚀 Analyze failed tests WITHOUT linked issues in a launch with grouping, statistics, and recommendations. Automatically analyzes all tests if ≤10, otherwise first 10 (use offset/limit for more). Use filterType: 'all' to include tests with issues. Supports pagination and screenshot analysis. NEW: Jira format with smart grouping - creates combined tickets for similar errors! 💡 TIP: Can be auto-invoked from Zebrunner launch URLs like: https://workspace.zebrunner.com/projects/PROJECT/automation-launches/LAUNCH_ID

📋 Get all launches for a project with pagination (uses new reporting API)

🔍 Get launches with filtering by milestone, build number, or launch name (uses new reporting API)

🔌 Test connection to Zebrunner Reporting API with new authentication

📊 Get test results by platform for a given period (SQL widget, templateId: 8)

🐞 Top N most frequent defects with optional issue links (SQL widget, templateId: 4)

🔍 Get detailed bug review with failures, defects, reproduction dates, and optional automatic failure detail fetching (SQL widget, templateId: 9)

🔬 Get comprehensive failure information including failure summary and detailed test runs (SQL widgets, templateId: 6 & 10)

🎯 Get available milestones for a project with pagination and filtering

🏗️ Discover available projects with their keys and IDs for dynamic project selection

🔍 Validate a test case against quality standards and best practices (Dynamic Rules Support + Improvement)

🔧 Analyze and improve a test case with detailed suggestions and optional automatic fixes

🏃 List Test Runs from Public API with advanced filtering

🔍 Get detailed Test Run information by ID from Public API

📝 List all Test Cases in a Test Run from Public API

Get list of Result Statuses configured for a project. These statuses are used when assigning results to Test Cases.

Get list of Configuration Groups and their Options for a project. These are used to configure Test Runs.

🔍 Analyze test cases for duplicates and group similar ones by step similarity (80-90%)

🧠 Advanced semantic duplicate analysis using LLM-powered step clustering and two-phase analysis

🔍 Find ALL test cases related to a specific feature across the project. Searches in title, description, preconditions, and test steps (case-insensitive, partial match). Groups results by Root Suite and Feature Suite, avoiding duplicates. Output formats: detailed (full hierarchy), short (summary), dto (JSON), test_run_rules (for automation tags)