Zephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments
Zephyr-scale-mcp is an MCP integration. Zephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments.
The published npm package is zephyr-scale-mcp, version 1.0.0. Its declared MCP transport is stdio.
The package declares JIRA_BASE_URL (required): Jira base URL without a trailing slash, e.g. https://jira.example.com; 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).
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 1.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| JIRA_BASE_URL | Jira base URL without a trailing slash, e.g. https://jira.example.com | Yes |
| JIRA_PAT | Jira Data Center Personal Access Token (used when JIRA_AUTH=pat, the default) | Optional |
| JIRA_AUTH | Authentication mode: pat (default) or basic | Optional |
| JIRA_USERNAME | Username for JIRA_AUTH=basic | Optional |
| JIRA_PASSWORD | Password for JIRA_AUTH=basic | Optional |
| ZEPHYR_DEFAULT_PROJECT_KEY | Project key used when a tool is called without projectKey | Optional |
| 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 | Optional |
| ZEPHYR_READONLY | true disables all write tools | Optional |
| JIRA_TLS_REJECT_UNAUTHORIZED | false allows self-signed certificates (disables TLS verification) | Optional |
| JIRA_TIMEOUT_MS | Timeout of a single HTTP request in milliseconds (default 30000) | Optional |
| JIRA_MAX_RETRIES | Retries for GET requests and for 429/503 responses, honoring Retry-After (default 2) | Optional |
| ZEPHYR_LOG_LEVEL | Log verbosity: debug | info | warn | error (default info; all logs go to stderr) | Optional |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.