MCP server for integrating with JIRA's Zephyr test management system
MCP server for integrating with JIRA's Zephyr test management system. The jira zephyr mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
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.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
Development — The Development tool exposed by this serverProduction — The Production tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverScripts — The Scripts tool exposed by this serverYou will need 4 environment variables: JIRA_BASE_URL, JIRA_USERNAME, JIRA_API_TOKEN, ZEPHYR_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Jira Zephyr MCP's toolset — Development, Production, Prerequisites and 1 more — is a fair guide to whether it matches your workflow. It is maintained by leorosignoli; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Jira Zephyr MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Development | The Development tool exposed by this server. |
| Production | The Production tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Scripts | The Scripts tool exposed by this server. |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| JIRA_USERNAME | Configuration value read at startup. | Optional |
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
| ZEPHYR_API_TOKEN | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.