Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZEPHYR_REGIONNoOne of us, eu, au, de. Defaults to us.us
ZEPHYR_BASE_URLNoFull base URL override. Takes precedence over ZEPHYR_REGION.
ZEPHYR_API_TOKENYesJWT bearer token for Zephyr Scale Cloud. Generate in Jira profile → Zephyr API keys.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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_cases — if you only need the list/titles of a story's tests, use that instead. Read-only; returns empty coverage (not an error) when no tests are linked.

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 search_test_cases (which is project-wide, not story-scoped) and over review_story_coverage (which is heavier) when you only need the list. Read-only; returns an empty list (not an error) when no tests are linked.

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 list_story_executions instead. Read-only; returns an empty list (not an error) when the test case has never been run.

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 list_story_test_cases (titles) or review_story_coverage (full). Read-only.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pabloveintimilla/zephyr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server