Mcp Zebrunner
Query and manage Zebrunner test cases, suites, coverage, and launchers from the agent during release prep.
Overview
MCP Zebrunner is a MCP server for the Ship phase that exposes Zebrunner TCM operations—test cases, suites, coverage, and launchers—to your coding agent.
What is this MCP server?
- Unified Zebrunner MCP server mcp-zebrunner v5.15.0 over stdio npm
- Tools for test cases, suites, coverage analysis, and launchers in one integration
- Configurable ZEBRUNNER_URL, LOGIN, TOKEN plus TIMEOUT and retry env vars
- Default API timeout 30000 ms and RETRY_ATTEMPTS default 3 per server schema
- Self-hosted Zebrunner instance—bring your own test management URL
- Server version 5.15.0
- Default TIMEOUT 30000 ms; default RETRY_ATTEMPTS 3
- Six documented environment variables including optional RETRY_DELAY
Community signal: 3 GitHub stars.
What problem does it solve?
Jumping between the agent and Zebrunner’s UI slows release testing when you are the only person owning quality.
Who is it for?
Teams already on self-hosted Zebrunner who want agent-assisted test management during shipping.
Skip if: Builders with no Zebrunner deployment, pure local pytest workflows, or invoice and finance automation needs.
What do I get? / Deliverables
After install, your agent can read and drive Zebrunner test assets on your instance using configured credentials.
- Agent-driven queries and actions against Zebrunner cases, suites, coverage, and launchers
- Configurable retry and timeout behavior for API calls
Recommended MCP Servers
Journey fit
Test case management and launch orchestration belong to Ship when you harden the product before production cutover. Testing is the canonical shelf for TCM APIs—suites, coverage analysis, and launcher config are pre-release quality work.
How it compares
Zebrunner TCM API MCP bridge, not a test generator skill or CI YAML editor.
Common Questions / FAQ
Who is mcp-zebrunner for?
Developers and solo leads using Zebrunner for test case and launch management who want MCP access from Claude Code or Cursor.
When should I use mcp-zebrunner?
Use it in Ship while reviewing suites, analyzing coverage, or configuring launchers ahead of a production release.
How do I add mcp-zebrunner to my agent?
Install mcp-zebrunner from npm, set ZEBRUNNER_URL, ZEBRUNNER_LOGIN, and ZEBRUNNER_TOKEN, enable stdio in your MCP config, and restart the client.