JIRA Zephyr

A Model Context Protocol (MCP) server that provides comprehensive integration with JIRA's Zephyr test management system. This server enables seamless test management operations including creating test plans, managing test cycles, executing tests, and reading JIRA issues.

- Test Plan Management: Create and list test plans in Zephyr
- Test Cycle Management: Create and manage test execution cycles
- JIRA Integration: Read JIRA issue details and metadata
- Test Execution: Update test execution results and status
- Progress Tracking: Monitor test execution progress and statistics
- Issue Linking: Associate test cases with JIRA issues
- Reporting: Generate comprehensive test execution reports
- read_jira_issue- Retrieve JIRA issue information
- create_test_plan- Create new test plans in Zephyr
- list_test_plans- Browse existing test plans
- create_test_cycle- Create test execution cycles
- list_test_cycles- View test cycles with execution status
- execute_test- Update test execution results
- get_test_execution_status- Check test execution progress
- link_tests_to_issues- Associate tests with JIRA issues
- generate_test_report- Create test execution reports

- Node.js 18.0.0 or higher
- JIRA instance with Zephyr Scale or Zephyr Squad
- Valid JIRA API credentials
- Zephyr API access token

Clone the project, then add the following to your Cursor configuration:

{ "mcpServers": { "jira-zephyr": { "command": "node", "args": ["/path/to/jira-zephyr-mcp/dist/index.js"], "env": { "JIRA_BASE_URL": "https://your-domain.atlassian.net", "JIRA_USERNAME": "your-email@company.com", "JIRA_API_TOKEN": "your-jira-api-token", "ZEPHYR_API_TOKEN": "your-zephyr-api-token" } } } }

Alternatively, you can configure Cursor to run the MCP server in Docker (ensure the image is built first):

{ "mcpServers": { "jira-zephyr": { "command": "docker", "args": ["run", "--rm", "-i","-e","JIRA_BASE_URL","-e","JIRA_USERNAME","-e","JIRA_API_TOKEN","-e","ZEPHYR_API_TOKEN", "jira-zephyr-mcp"], "env": { "JIRA_BASE_URL": "https://your-domain.atlassian.net", "JIRA_USERNAME": "your-email@company.com", "JIRA_API_TOKEN": "your-jira-api-token", "ZEPHYR_API_TOKEN": "your-zephyr-api-token" } } } }

git clone https://github.com/your-username/jira-zephyr-mcp.git cd jira-zephyr-mcp

- Configure your JIRA and Zephyr credentials in.env:

JIRA_BASE_URL=https://your-domain.atlassian.net JIRA_USERNAME=your-email@company.com JIRA_API_TOKEN=your-jira-api-token ZEPHYR_API_TOKEN=your-zephyr-api-token

- Go toAtlassian Account Settings
- Navigate to Security → API tokens
- Create a new API token
- Copy the token to your.envfile
- In JIRA, go to Apps → Zephyr Scale → API Access Tokens
- Generate a new token
- Copy the token to your.envfile

docker build -t jira-zephyr-mcp:latest .

docker run -d --name jira-zephyr-mcp \ -e JIRA_BASE_URL=https://your-domain.atlassian.net \ -e JIRA_USERNAME=your-email@company.com \ -e JIRA_API_TOKEN=your-jira-api-token \ -e ZEPHYR_API_TOKEN=your-zephyr-api-token \ jira-zephyr-mcp:latest

// Read basic issue information await readJiraIssue({ issueKey: "ABC-123" }); // Read specific fields await readJiraIssue({ issueKey: "ABC-123", fields: ["summary", "status", "assignee"] });

await createTestPlan({ name: "Release 2.0 Test Plan", description: "Comprehensive testing for release 2.0", projectKey: "ABC", startDate: "2024-01-15", endDate: "2024-01-30" });

// Create a test cycle await createTestCycle({ name: "Sprint 10 Testing", description: "Testing for sprint 10 features", projectKey: "ABC", versionId: "10001", environment: "Production" }); // List test cycles await listTestCycles({ projectKey: "ABC", limit: 25 });

// Update test execution status await executeTest({ executionId: "12345", status: "PASS", comment: "All tests passed successfully" }); // Get execution status await getTestExecutionStatus({ cycleId: "67890" });

// Generate JSON report await generateTestReport({ cycleId: "67890", format: "JSON" }); // Generate HTML report await generateTestReport({ cycleId: "67890", format: "HTML" });

The server implements comprehensive error handling:

- Input validation using Zod schemas
- API error mapping and user-friendly messages
- Network timeout handling
- Authentication error detection

- npm run build- Build the TypeScript project
- npm run dev- Run in development mode with file watching
- npm run lint- Run ESLint
- npm run typecheck- Run TypeScript type checking

src/ ├── index.ts # Main MCP server entry point ├── clients/ # API clients │ ├── jira-client.ts # JIRA REST API client │ └── zephyr-client.ts # Zephyr API client ├── tools/ # MCP tool implementations │ ├── jira-issues.ts # JIRA issue tools │ ├── test-plans.ts # Test plan management │ ├── test-cycles.ts # Test cycle management │ └── test-execution.ts # Test execution tools ├── types/ # TypeScript type definitions │ ├── jira-types.ts # JIRA API types │ └── zephyr-types.ts # Zephyr API types └── utils/ # Utility functions ├── config.ts # Configuration management └── validation.ts # Input validation schemas

- Fork the repository
- Create a feature branch
- Make your changes
- Add tests for new functionality
- Submit a pull request

- Never commit API tokens or credentials to the repository
- Use environment variables for all sensitive configuration
- Regularly rotate API tokens
- Implement proper access controls in your JIRA instance

MIT License - see LICENSE file for details
- Check the existing GitHub issues
- Create a new issue with detailed information
- Include error logs and configuration (without sensitive data)

- Support for Zephyr Squad (in addition to Zephyr Scale)
- Bulk test execution operations
- Advanced reporting with charts and metrics
- Test case creation and management
- Integration with CI/CD pipelines
- Custom field support for test management

MCP server for Xray test management plugin for Jira. Avoids the problem of slow Jira/ Xray combination. Can bring an entire test suite faster than manually adding. Can integrate AI testing as this is able to update test cases as well. Why MCP and not a skill? MCP communicates well with Atlassian MCP.

Official Atlassian MCP server for connecting AI agents to Jira, Confluence, Opsgenie, and other Atlassian products.

Interact with Atlassian tools like Confluence and Jira.

Integrate with Atlassian Cloud to access Jira tickets, issues, projects, and Confluence pages.

Integrates AI with Atlassian Jira to manage projects, search for issues, and view development information like commits and pull requests.

An MCP client for integrating with Atlassian tools like Jira and Confluence using OAuth authentication.

A server for querying Jira issues, requiring a Jira token for authentication.

Integrate with Jira's REST API to manage projects, track issues, and perform analytics.

Interact with Jira to manage issues, projects, and workflows using the Jira Cloud Platform REST API.

An MCP server for interacting with Jira's REST API to manage projects, issues, and users.