Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable detailed logging | false |
| MAX_PAGE_SIZE | No | Maximum items per page | 100 |
| ZEBRUNNER_URL | Yes | Your Zebrunner instance URL (without trailing slash), e.g. https://your-company.zebrunner.com/api/public/v1 | |
| MCP_RULES_FILE | No | Custom technical rules file (optional) | |
| ZEBRUNNER_LOGIN | Yes | Your Zebrunner login (usually your email) | |
| ZEBRUNNER_TOKEN | Yes | Your Zebrunner API token (get this from your Zebrunner profile) | |
| DEFAULT_PAGE_SIZE | No | Default items per page | 100 |
| ENABLE_RULES_ENGINE | No | Enable intelligent rules system (auto-detected if rules file exists) | true |
| REQUIRE_UI_VALIDATION | No | Require UI validation in tests (optional) | |
| MIN_COVERAGE_THRESHOLD | No | Minimum coverage percentage (optional) | |
| REQUIRE_API_VALIDATION | No | Require API validation in tests (optional) |
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_test_suites | ๐ List test suites for a project (โ Verified Working) |
| get_test_case_by_key | ๐ Get detailed test case by key (โ Verified Working) |
| get_all_subsuites | ๐ Get all subsuites from a root suite as flat list with pagination |
| get_test_cases_advanced | ๐ 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_suite_hierarchy | ๐ณ Get hierarchical test suite tree with configurable depth |
| get_test_cases_by_automation_state | ๐ค Get test cases filtered by automation state (๐ก Use get_automation_states to see available states) |
| get_automation_states | ๐ง Get available automation states for a project (names and IDs) |
| get_test_coverage_by_test_case_steps_by_key | ๐ Analyze test case coverage against actual implementation with recommendations |
| generate_draft_test_by_key | ๐งช Generate draft test code from Zebrunner test case with intelligent framework detection |
| get_enhanced_test_coverage_with_rules | ๐ Enhanced test coverage analysis with configurable rules validation and quality scoring |
| get_tcm_test_suites_by_project | ๐ Get TCM test suites by project with pagination (Java methodology) |
| get_all_tcm_test_case_suites_by_project | ๐ Get ALL TCM test case suites by project using comprehensive pagination |
| get_root_suites | ๐ณ Get root suites (suites with no parent) from project |
| get_tcm_suite_by_id | ๐ Find TCM suite by ID with comprehensive search |
| get_all_tcm_test_cases_by_project | ๐ Get ALL TCM test cases by project using comprehensive pagination |
| get_all_tcm_test_cases_with_root_suite_id | ๐ณ Get ALL TCM test cases enriched with root suite ID information |
| get_root_id_by_suite_id | ๐ Get root suite ID for a specific suite ID |
| get_test_cases_by_suite_smart | ๐ง Smart test case retrieval by suite ID - automatically detects if suite is root suite and uses appropriate filtering with enhanced pagination |
| get_launch_details | ๐ Get comprehensive launch details including test sessions (uses new reporting API with enhanced authentication) |
| get_launch_summary | ๐ Get quick launch summary without detailed test sessions (uses new reporting API) |
| get_all_launches_for_project | ๐ Get all launches for a project with pagination (uses new reporting API) |
| get_all_launches_with_filter | ๐ Get launches with filtering by milestone, build number, or launch name (uses new reporting API) |
| test_reporting_connection | ๐ Test connection to Zebrunner Reporting API with new authentication |
| get_platform_results_by_period | ๐ Get test results by platform for a given period (SQL widget, templateId: 8) |
| get_top_bugs | ๐ Top N most frequent defects with optional issue links (SQL widget, templateId: 4) |
| get_project_milestones | ๐ฏ Get available milestones for a project with pagination and filtering |
| get_available_projects | ๐๏ธ Discover available projects with their keys and IDs for dynamic project selection |
| validate_test_case | ๐ Validate a test case against quality standards and best practices (Dynamic Rules Support + Improvement) |
| improve_test_case | ๐ง Analyze and improve a test case with detailed suggestions and optional automatic fixes |
| list_test_runs | ๐ List Test Runs from Public API with advanced filtering |
| get_test_run_by_id | ๐ Get detailed Test Run information by ID from Public API |
| list_test_run_test_cases | ๐ List all Test Cases in a Test Run from Public API |
| get_test_run_result_statuses | Get list of Result Statuses configured for a project. These statuses are used when assigning results to Test Cases. |
| get_test_run_configuration_groups | Get list of Configuration Groups and their Options for a project. These are used to configure Test Runs. |
| analyze_test_cases_duplicates | ๐ Analyze test cases for duplicates and group similar ones by step similarity (80-90%) |
| analyze_test_cases_duplicates_semantic | ๐ง Advanced semantic duplicate analysis using LLM-powered step clustering and two-phase analysis |