Zephyr Scale MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 80 installs a week from npm. Last commit 31 Jul 2026.
Zephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments
Today is the operative word: we check Zephyr Scale MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add zephyr-scale-mcp -e 'JIRA_BASE_URL=<JIRA_BASE_URL>' -- npx -y zephyr-scale-mcp
{
"mcpServers": {
"zephyr-scale-mcp": {
"command": "npx",
"args": [
"-y",
"zephyr-scale-mcp"
],
"env": {
"JIRA_BASE_URL": "<JIRA_BASE_URL>"
}
}
}
}
[mcp_servers.zephyr-scale-mcp]
command = "npx"
args = ["-y", "zephyr-scale-mcp"]
env = { JIRA_BASE_URL = "<JIRA_BASE_URL>" }
{
"mcpServers": {
"zephyr-scale-mcp": {
"command": "npx",
"args": [
"-y",
"zephyr-scale-mcp"
],
"env": {
"JIRA_BASE_URL": "<JIRA_BASE_URL>"
}
}
}
}
{
"servers": {
"zephyr-scale-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"zephyr-scale-mcp"
],
"env": {
"JIRA_BASE_URL": "<JIRA_BASE_URL>"
}
}
}
}
Put your own value in place of
<JIRA_BASE_URL> (Jira base URL without a trailing slash, e.g. https://jira.example.com).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
JIRA_PAT (Jira Data Center Personal Access Token (used when JIRA_AUTH=pat, the default)), JIRA_AUTH (Authentication mode: pat (default) or basic), JIRA_USERNAME (Username for JIRA_AUTH=basic), JIRA_PASSWORD (Password for JIRA_AUTH=basic), ZEPHYR_DEFAULT_PROJECT_KEY (Project key used when a tool is called without projectKey), ZEPHYR_ALLOW_INTERNAL_API (true registers 11 UNOFFICIAL tools backed by the internal /rest/tests/1.0 API the vendor does not support: editing a test cycle in place (rename/move, add/remove/reorder its cases), editing or DELETING individual executions, linking a cycle to a test plan, the folder tree, folder deletion, exact status names and custom field definitions), ZEPHYR_READONLY (true disables all write tools), JIRA_TLS_REJECT_UNAUTHORIZED (false allows self-signed certificates (disables TLS verification)), JIRA_TIMEOUT_MS (Timeout of a single HTTP request in milliseconds (default 30000)), JIRA_MAX_RETRIES (Retries for GET requests and for 429/503 responses, honoring Retry-After (default 2)), ZEPHYR_LOG_LEVEL (Log verbosity: debug | info | warn | error (default info; all logs go to stderr)).
MCP server for QMetry Test Management for Jira (QTM4J): test cases, cycles, executions, plans.
MCP Server for software testing, test case management, test execution, and defect tracking.
Free test management over MCP: projects, test cases, plans, runs, environments and tasks.
Local test execution and coverage summaries for onboarding agents.
MCP server for Cucumber Studio - test scenarios, action words, and execution data
Connect AI assistants to TestRail: manage test cases, suites, runs, results, and attachments.
MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants
Test management over MCP: author cases, run manual executions, cut releases, read health
Answers built from our own checks of this server.