The MCP server integrates with Zebrunner Test Case Management to assist QA teams in managing test cases, test suites, and test execution data using AI assistants.
From the registry: Unified Zebrunner MCP server for TCM test cases, suites, coverage analysis, launchers, etc.
Please install the `mcp-zebrunner` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Clone and build** — git clone https://github.com/maksimsarychau/mcp-zebrunner and run 'npm install && npm run build'
- **Zebrunner credentials** — Zebrunner URL, login email, and API token
Canonical MCP server config (stdio transport):
- command: `node`
- args: ["/full/absolute/path/to/mcp-zebrunner/dist/server.js"]
- required environment variables:
- `ZEBRUNNER_URL`: Zebrunner API URL (example: `https://your-company.zebrunner.com/api/public/v1`)
- `ZEBRUNNER_LOGIN`: Zebrunner account email (example: `<your-email>`)
- `ZEBRUNNER_TOKEN`: Zebrunner API token (example: `<your-api-token>`)
- optional environment variables:
- `DEBUG`: Enable debug logging (example: `false`)
- `ENABLE_RULES_ENGINE`: Enable intelligent rules engine (example: `true`)
- `DEFAULT_PAGE_SIZE`: Default page size (example: `100`)
- `MAX_PAGE_SIZE`: Maximum page size (example: `100`)
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.ZEBRUNNER_URLrequiredThe URL of your Zebrunner instance.ZEBRUNNER_LOGINrequiredYour Zebrunner login, usually your email.ZEBRUNNER_TOKENrequiredYour Zebrunner API token.Real-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.