JIRA Zephyr MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_BASE_URL | Yes | The base URL of your JIRA instance (e.g., https://your-domain.atlassian.net) | |
| JIRA_USERNAME | Yes | Your JIRA username/email address (e.g., your-email@company.com) | |
| JIRA_API_TOKEN | Yes | Your JIRA API token (generate from Atlassian Account Settings → Security → API tokens) | |
| ZEPHYR_API_TOKEN | Yes | Your Zephyr API token (generate from JIRA → Apps → Zephyr Scale → API Access Tokens) |
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 |
|---|---|
| read_jira_issueC | Read JIRA issue details and metadata |
| create_test_planC | Create a new test plan in Zephyr |
| list_test_plansC | List existing test plans |
| create_test_cycleC | Create a new test execution cycle |
| list_test_cyclesC | List existing test cycles with execution status |
| execute_testC | Update test execution results |
| get_test_execution_statusC | Get test execution progress and statistics |
| link_tests_to_issuesC | Associate test cases with JIRA issues |
| generate_test_reportC | Generate test execution report |
| create_test_caseC | Create a new test case in Zephyr |
| search_test_casesC | Search for test cases in a project |
| get_test_caseC | Get detailed information about a specific test case |
| create_multiple_test_casesC | Create multiple test cases in Zephyr at once |
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 13 tools
Every tool has a clearly distinct purpose targeting specific Zephyr test management resources and actions. The tools cover creation, retrieval, listing, execution, reporting, and linking operations with no overlap or ambiguity between them.
All tools follow a consistent verb_noun naming pattern throughout (e.g., create_test_case, list_test_cycles, get_test_execution_status). The naming convention is perfectly uniform and predictable across all 13 tools.
With 13 tools, this server is well-scoped for comprehensive test management operations in Zephyr. Each tool earns its place by covering distinct aspects of test case, test cycle, test plan, and execution management without being excessive.
The tool set provides complete CRUD/lifecycle coverage for Zephyr test management, including creation, reading, listing, updating (via execute_test), and reporting operations. It also integrates with JIRA issues and covers all major workflows without any apparent gaps.