MCP Zephyr
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZEPHYR_BASE_URL | No | Base URL for Zephyr Scale Cloud API (optional) | https://api.zephyrscale.smartbear.com/v2 |
| ZEPHYR_API_TOKEN | Yes | Your Zephyr API token (required) | |
| ZEPHYR_PROJECT_KEY | No | Default project key (optional) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsC | List all Zephyr-integrated Jira projects |
| get_projectC | Get detailed information about a specific Zephyr project |
| list_foldersB | List folders in a project or specific folder |
| get_folderC | Get detailed information about a specific folder |
| create_folderC | Create a new folder in a project |
| list_test_casesC | List test cases with optional filtering by project and folder |
| get_test_caseC | Get detailed information about a specific test case |
| create_test_caseC | Create a new test case |
| update_test_caseC | Update an existing test case |
| get_test_stepsB | Get test steps for a test case (paged response, 100 items per page) |
| get_all_test_stepsA | Get all test steps for a test case (handles pagination automatically) |
| append_test_stepsC | Append new test steps to a test case (max 100 steps per request) |
| get_test_scriptB | Get the test script (Gherkin format) for a test case |
| create_test_scriptB | Create or update a test script for a test case (removes existing test steps) |
| create_bdd_test_scriptC | Create a BDD test script using Gherkin format with helper validation |
| list_statusesB | List all available test case statuses (e.g., Draft, Ready, Approved) |
| list_prioritiesB | List all available test case priorities (e.g., High, Medium, Low) |
| get_reference_dataB | Get all reference data (statuses and priorities) in a single call |
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 18 tools
Most tools have clearly distinct purposes, but there is some overlap between 'get_all_test_steps' and 'get_test_steps' which could cause confusion as both retrieve test steps with different pagination approaches. All other tools target specific resources and actions without ambiguity.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'create_test_case', 'get_project', 'list_folders', and 'update_test_case'. This predictability makes it easy for agents to understand and select the appropriate tool.
With 18 tools, the count is slightly high but reasonable for a test management domain, covering projects, folders, test cases, steps, scripts, and reference data. It might feel a bit heavy, but each tool appears to serve a specific function without obvious redundancy.
The tool set provides comprehensive coverage for test management, including CRUD operations for projects, folders, test cases, and test steps, along with listing reference data and handling test scripts. There are no apparent gaps that would hinder agent workflows in this domain.