Zephyr Scale MCP. Audit, track, and report on QA cycles through chat.

Listen up. Forget clicking through a dozen Jira plugins just to see if your tests passed. This server hooks up your agent directly to your Zephyr Scale project so you don't gotta navigate any complex menus; you just talk to it. It handles all the heavy lifting, giving you the full picture without making you feel like an IT intern.

To find what you need: You can ask your AI client to pull up a list of all high-level test plans that define your whole testing strategy using list_test_plans. Need to see how things are organized? Use list_folders to browse the entire organizational hierarchy, whether it's for Test Cases, Cycles, or Plans.

For actual tests, you can get a quick rundown of all available test cases in a specific Jira project via list_test_cases, and if you need every single detail—the objective text, preconditions, and full scripts—you just call up get_test_case for any individual script.

To track down your work: You can pull a list of all grouped test cycles using list_test_cycles, which lets you see the major milestones. If you're checking on a specific sprint or release, calling get_test_cycle pulls up those full details and tells you exactly where things stand. For a complete audit trail, use list_executions to get a list of every single test run that’s ever happened in the project.

To check progress: When you need deep status checks, calling get_execution gives you the whole nine yards: step-by-step results and how long it took for one specific test run. If you're trying to scope out what environments are live, list_environments shows you every configured place—like Staging or Production—where your code runs.

You can also check all the custom status names used for results with list_statuses.

The full picture: When you combine these calls, you're covered. You use list_folders to browse assets, get_test_case to understand a single test, and then use get_execution or get_test_cycle to see how that test performed in the wild. If you need to know which tests exist at all, list_test_cases gives you their keys and current status.

You'll find everything from browsing the whole project structure with list_folders to checking the full scope of grouped runs using list_test_cycles. It’s basically your entire QA operations manual, but instead of reading it, you just ask your agent.