Advanced Zebrunner MCP Server

What this does

Advanced Zebrunner MCP Server exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

ZEBRUNNER_URL
ZEBRUNNER_LOGIN
ZEBRUNNER_TOKEN
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
RATE_LIMITING_BURST

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Advanced Zebrunner MCP Server?

Run the Claude Code command in the install section to add Advanced Zebrunner MCP Server to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Advanced Zebrunner MCP Server?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Advanced Zebrunner MCP Server as well.

Does Advanced Zebrunner MCP Server need an API key?

Yes. Before it can run, set these environment variables: ZEBRUNNER_URL, ZEBRUNNER_LOGIN, ZEBRUNNER_TOKEN, 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, RATE_LIMITING_BURST. They go in the env block of your MCP config.