Developer · Local MCP server
Zephyr Scale MCP
Zephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.vilaabo/zephyr-scale-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-31
- Updated
- 2026-07-31
- Publisher
- vilaabo (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/vilaabo) · how
- Listed under
- Jira MCP servers
- Repository
- github.com/vilaabo/zephyr-scale-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | zephyr-scale-mcp | 1.0.0 | stdio |
How to connect Zephyr Scale MCP
Zephyr Scale MCP runs locally from a Node.js package published to the npm registry: zephyr-scale-mcp version 1.0.0. 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 zephyr-scale-mcp@1.0.0. It reads these environment variables: JIRA_BASE_URL (required), JIRA_PAT (secret), JIRA_AUTH, JIRA_USERNAME, JIRA_PASSWORD (secret), ZEPHYR_DEFAULT_PROJECT_KEY, ZEPHYR_ALLOW_INTERNAL_API, ZEPHYR_READONLY, JIRA_TLS_REJECT_UNAUTHORIZED, JIRA_TIMEOUT_MS, JIRA_MAX_RETRIES and ZEPHYR_LOG_LEVEL; 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": {
"zephyr-scale-mcp": {
"command": "npx",
"args": [
"-y",
"zephyr-scale-mcp@1.0.0"
],
"env": {
"JIRA_BASE_URL": "<value>",
"JIRA_PAT": "<secret>",
"JIRA_AUTH": "<value>",
"JIRA_USERNAME": "<value>",
"JIRA_PASSWORD": "<secret>",
"ZEPHYR_DEFAULT_PROJECT_KEY": "<value>",
"ZEPHYR_ALLOW_INTERNAL_API": "<value>",
"ZEPHYR_READONLY": "<value>",
"JIRA_TLS_REJECT_UNAUTHORIZED": "<value>",
"JIRA_TIMEOUT_MS": "<value>",
"JIRA_MAX_RETRIES": "<value>",
"ZEPHYR_LOG_LEVEL": "<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 |
|---|---|
| ZenLink MCPBrowser automation for MCP clients via Zen Browser. Parallel multi-tab, content extraction. | Local · stdio |
| Zenrows MCPZenrows MCP server - Fetch, Extract, Batch, and Browser Sessions for AI coding assistants. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Zentric Protocol MCPPrompt injection + PII detection for LLM apps and agent pipelines. Deterministic, sub-25ms. | Local · stdio |
| ZephexMCP gateway with 10 tools for code analysis, architecture, package audit & security. | Remote · HTTPLive check: ✗ no handshake |
| zermAgent utility belt: memory, locks, webhook inboxes, timers, DNS, email, URL, timezone, cron. | Remote · HTTPLive check: ✓ handshake |
| Zero Core ToolsWeb scraping, code review, content gen, sentiment. Zero Core Tools. | Remote & Local · HTTPLive check: ✓ handshake |
| Zero Core VerifyPost-tx outcome verification via LLM-as-judge. Zero Core Verify. | Remote & Local · HTTPLive check: ✓ handshake |
| ZeroCMSAI-native Git-based CMS for Astro. Create and publish content in the browser, without learning git. | Remote · HTTPLive check: sign-in required |