mcp-zebrunner MCP Server

What the mcp-zebrunner MCP server does

How models use it and what it is built for.

Unified Zebrunner MCP server for TCM test cases, suites, coverage analysis, launchers, etc.

Connect to mcp-zebrunner

Hosted endpoint — paste into any MCP client.

Environment variables

Configuration this server reads at startup.

• ZEBRUNNER_URLRequired

  Base URL for your Zebrunner instance (e.g., https://your-instance.zebrunner.com)

• ZEBRUNNER_LOGINRequired

  Your Zebrunner username/login

• ZEBRUNNER_TOKENRequiredSecret

  Your Zebrunner API authentication token

• TIMEOUT

  API request timeout in milliseconds (default: 30000)

• RETRY_ATTEMPTS

  Number of retry attempts for failed API requests (default: 3)

• RETRY_DELAY

  Delay between retry attempts in milliseconds (default: 1000)

• MAX_PAGE_SIZE

  Maximum page size for paginated API requests (default: 100, max: 1000)

• DEFAULT_PAGE_SIZE

  Default page size for paginated API requests (default: 10)

• DEBUG

  Enable debug logging (default: false)

• ENABLE_RULES_ENGINE

  Enable the rules engine for test case validation (default: auto-detected from mcp-zebrunner-rules.md file)

• STRICT_URL_VALIDATION

  Enable strict URL validation for security (default: true)

• SKIP_URL_VALIDATION_ON_ERROR

  Skip URL validation if it fails (less secure, more permissive) (default: false)

• ENABLE_RATE_LIMITING

  Enable rate limiting for API calls (default: true)

• MAX_REQUESTS_PER_SECOND

  Maximum API requests per second (default: 5, max: 100)

• RATE_LIMITING_BURST

  Allow burst of API requests (default: 10, max: 200)

Resources

Where to find authoritative docs and source for mcp-zebrunner.

• Source repository