Developer · Local MCP server
Advanced Zebrunner MCP Server
Advanced analytics, reporting, and safe mutations for Zebrunner. 64 tools, 14 resources, 17 prompts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.maksimsarychau/mcp-zebrunner- Version
- 9.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process), Streamable HTTP
- Package
- npm
- Published
- 2026-07-08
- Updated
- 2026-07-08
- Publisher
- maksimsarychau (GitHub)
- Website
- github.com/maksimsarychau/mcp-zebrunner
- Repository
- github.com/maksimsarychau/mcp-zebrunner
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | mcp-zebrunner | 9.2.1 | stdio |
| npm | mcp-zebrunner | 9.2.1 | HTTP |
How to connect Advanced Zebrunner MCP Server
Advanced Zebrunner MCP Server runs locally from a Node.js package published to the npm registry: mcp-zebrunner version 9.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y mcp-zebrunner@9.2.1. It reads these environment variables: ZEBRUNNER_URL (required), ZEBRUNNER_LOGIN (required), ZEBRUNNER_TOKEN (required, secret), TIMEOUT, RETRY_ATTEMPTS, RETRY_DELAY, MAX_PAGE_SIZE, DEFAULT_PAGE_SIZE, DEBUG, ENABLE_RULES_ENGINE, STRICT_URL_VALIDATION, SKIP_URL_VALIDATION_ON_ERROR, ENABLE_RATE_LIMITING, MAX_REQUESTS_PER_SECOND and RATE_LIMITING_BURST; set them in the client's configuration for this server.
Advanced Zebrunner MCP Server runs locally from a Node.js package published to the npm registry: mcp-zebrunner version 9.2.1. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL. It reads these environment variables: PORT (required), ZEBRUNNER_URL (required), MCP_TRANSPORT, MCP_AUTH_MODE and MCP_SERVER_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-zebrunner": {
"command": "npx",
"args": [
"-y",
"mcp-zebrunner@9.2.1"
],
"env": {
"ZEBRUNNER_URL": "<value>",
"ZEBRUNNER_LOGIN": "<value>",
"ZEBRUNNER_TOKEN": "<secret>",
"TIMEOUT": "<value>",
"RETRY_ATTEMPTS": "<value>",
"RETRY_DELAY": "<value>",
"MAX_PAGE_SIZE": "<value>",
"DEFAULT_PAGE_SIZE": "<value>",
"DEBUG": "<value>",
"ENABLE_RULES_ENGINE": "<value>",
"STRICT_URL_VALIDATION": "<value>",
"SKIP_URL_VALIDATION_ON_ERROR": "<value>",
"ENABLE_RATE_LIMITING": "<value>",
"MAX_REQUESTS_PER_SECOND": "<value>",
"RATE_LIMITING_BURST": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| AdscapiFire one canonical conversion event to every ad platform's server-side Conversions API. | Local · stdio |
| AdsmcpMCP-native ad server. Monetize AI chatbots and agents with conversational ads. | Remote · HTTP |
| AdsTurbo Creative MCPLocal-only MCP server and CLI for AI video ad briefs, UGC scripts, storyboards, and prompts. | Local · stdio |
| Advanced GitLab MCP server58 CQRS tools exposing 230 GitLab operations across 26 entity types. | Local · stdio |
| AdWhiz — Google & Meta Ads MCP ServerGoogle & Meta Ads management with 100+ tools. Audit, create, and optimize campaigns. | Remote · HTTP |
| AegisLocal stdio MCP server for the AEGIS governance client. The hosted evaluation service is offline. | Local · stdio |
| AegisCharter-bound defensive security copilot: secrets, obfuscation, deps, Dockerfile, IaC scans. | Local · stdio |
| Aegis — AI Agent GovernancePolicy-based governance for AI agent tool calls. YAML policy, approval gates, audit logging. | Local · stdio |