SmartBear Zephyr Remote MCP Server

What it does

SmartBear runs this endpoint at https://zephyr.mcp.smartbear.com/mcp so an MCP client can work with Zephyr, its test management app for Jira, without installing anything. The client connects by URL over streamable HTTP and the user signs in through a browser OAuth flow; no Zephyr API token or environment variable is set.

Through it an assistant can browse projects, folders, statuses, priorities, environments and test plans; read, create and update test cases, their steps and scripts; create and update test cycles and test executions, including per-step execution results; and attach web links or Jira issue links to cases, cycles and executions, or look up which cases, cycles and executions a Jira issue is linked to. There are 37 tools, registered in src/zephyr/client.ts of SmartBear's open-source smartbear-mcp repository, which also documents the Zephyr tools for this endpoint.

The same Zephyr tools ship in SmartBear's local smartbear-mcp package (@smartbear/mcp), which runs on the user's machine and instead takes a ZEPHYR_API_TOKEN. The endpoint's OAuth protected-resource metadata names https://app.tm4j.smartbear.com as its authorization server, while the remote setup page describes the browser step as an Atlassian OAuth login.

What it needs

A Jira Cloud site with Zephyr on the Standard or Advanced plan (Zephyr Essential is not supported), and a user who can sign in through the browser OAuth flow. An MCP client that can connect to a remote streamable-HTTP server and complete OAuth; SmartBear's snippets for Cursor, Claude Desktop and Claude Code use local callback port 8080, so that port must be free.

Limits

Covers Zephyr only; BugSnag and Swagger have their own SmartBear endpoints, and other SmartBear products need the local smartbear-mcp package. There are no delete tools: cases, cycles, executions and folders can be created and updated but not removed. Updates are partial, but a list field such as labels replaces the old values when given, and a null value clears a field; Update Test Execution and Update Test Execution Steps instead ignore null or absent fields. The setup docs' Cursor and Claude Desktop blocks nest the URL inside a transport object with an oauth callbackPort rather than those clients' usual remote form. The docs do not say which smartbear-mcp release the endpoint runs.

Who it suits

Suits QA engineers and teams already on Zephyr Standard or Advanced in Jira Cloud who want an assistant to draft test cases, record execution results or trace tests to Jira issues, and who prefer a vendor-run endpoint with OAuth sign-in over storing an API token. Since its tools can create and change test data, start with a test project. Pick SmartBear's local smartbear-mcp package instead to run the code on your own machine, to pin a version, to use a region-specific Zephyr API base URL via ZEPHYR_BASE_URL, or to reach BugSnag, Reflect, PactFlow, QMetry and other SmartBear products from one server.