Zephyr Review MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZEPHYR_REGION | No | One of us, eu, au, de. Defaults to us. | us |
| ZEPHYR_BASE_URL | No | Full base URL override. Takes precedence over ZEPHYR_REGION. | |
| ZEPHYR_API_TOKEN | Yes | JWT bearer token for Zephyr Scale Cloud. Generate in Jira profile → Zephyr API keys. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review_story_coverageA | FULL coverage for one story (Jira issue key), including every step and execution. Use when assessing whether a story is well covered, well-formed, or passing. Returns a digested bundle: linked test cases with objective, priority, status, steps (action / expected result / data), each case's most recent execution, referenced test cycles, and a coverage summary (passed / failed / not-run counts and step-quality flags). Heavier than |
| list_story_test_casesA | LIGHTWEIGHT list of the test cases linked to one story (Jira issue key) — each with key, name/title, priority, and status. No steps, no executions. Use this when asked for the test cases or titles of a specific story. Prefer this over |
| get_test_caseA | Returns the full detail of a single Zephyr test case, including ordered steps with expected results. Steps with an empty expected-result field are preserved so quality gaps stay visible. Read-only. |
| list_story_executionsA | Returns the test executions linked to a Jira issue (story) with their status, cycle, and date — a focused pass/fail view. Returns an empty list when the story's tests have not been run. Read-only. |
| list_test_case_executionsA | FULL execution history of ONE test case (Zephyr test case key), newest-first — every run across all cycles plus ad-hoc runs, not just the latest. Each execution includes status, cycle, date, comment, automated flag, timing (execution/estimated ms), who ran it, environment, custom fields, and linked Jira issues. Use this when asked about a specific test case's runs, history, or flakiness. This is TEST-CASE scoped — for the executions of a whole story (Jira issue key) use |
| search_test_casesA | PROJECT-WIDE search across ALL test cases in a project, matching key/name/objective (case-insensitive, client-side; the Zephyr API has no full-text search). This is NOT scoped to a story — do not use it to get the tests of a specific issue. Use it only when you do NOT have a Jira issue key, or to look beyond the tests linked to a single story. For a story's tests, use |
| get_projectA | Returns Zephyr project metadata (Zephyr id, Jira project id, key, enabled flag) for a project key. Useful to resolve keys and scope during a review. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: project metadata, individual test case details, story-level test listing, story-level execution summary, test-case-level full execution history, comprehensive coverage review, and project-wide search. Descriptions explicitly differentiate between similar-sounding tools (e.g., list_story_test_cases vs review_story_coverage).
All tools follow a consistent verb_noun pattern with snake_case (get_project, get_test_case, list_story_executions, list_story_test_cases, list_test_case_executions, review_story_coverage, search_test_cases). The verbs are appropriately varied (get, list, review, search) and clearly indicate the operation type.
With 7 tools, the server is well-scoped for a read-only Zephyr review interface. Each tool serves a clear purpose without redundancy, covering project lookup, test case retrieval, story-level test listing, execution history (both story and test-case scoped), full coverage review, and project-wide search.
The tool surface fully covers the read-only Zephyr review domain: project metadata, individual test cases (with steps), story-linked tests (lightweight), story executions (pass/fail view), test case execution history (detailed), full coverage bundle (with step quality, cycles, summary), and project-wide search. No obvious gaps for the intended use case.