Labsco
MCP SERVER · OFFICIAL PROJECT

SmartBear MCP Server

by SmartBear ↗

One connection across SmartBear's testing and monitoring line — BugSnag errors, Swagger APIs, contract tests, and the QMetry, Zephyr, QTM4J, Reflect and BearQ test suites.

Observability, Monitoring & Incident Response✓ Verified
Summary
An error, the test that should have caught it, and the API contract behind it — in one connection.

Because the products share a server, a BugSnag error can be followed into the test management system that owns its coverage and the contract tests that govern the API involved, without three separate integrations. Two things to decide up front: the hosted endpoints cover BugSnag, Swagger and Zephyr with an OAuth login and no install, so reach for the npm package only when you need the other products; and since every credential you add loads another product's tool family, supplying only the ones you use is what keeps the tool list navigable.

What it is

SmartBear's own server, bundling every product into one package with each integration switched on by whether you supply its credential. Three products also have hosted remote servers that need no install at all.

What you get
  • BugSnag: projects and their event filters, errors listed, read and updated, individual events including one resolved straight from a dashboard URL, releases and builds, plus tracing — span groups, spans, traces, trace fields and network endpoint groupings
  • Swagger: API Hub portals and portal products created, updated, published and organised into sections and a table of contents, alongside API and domain management
  • Contract testing against PactFlow or a Pact Broker — the largest family here, covering the pacts, participants and verification results that decide whether a consumer and provider still agree
  • QMetry, Zephyr and QTM4J test management: test cases, cycles, executions and results in whichever of the three your team runs
  • Reflect: suites and tests listed, created and executed, with execution status, screenshots, segments, and a live session you can attach prompt steps to
  • BearQ: regression tests and test cases run, tests run across functional areas, an application model expanded, a QA-lead chat, environments listed, and long jobs handled through get_task, get_task_status, wait_for_task and stop_task
  • Collaborator: code and document reviews plus remote system configuration
  • Every tool is prefixed by product — bugsnag_, swagger_, zephyr_, qmetry_, qtm4j_, reflect_, bearq_, collaborator_, contract-testing_ — so what belongs to what is legible in the tool list
Requirements

Access to the SmartBear products you want, and a credential per product — the server starts with whichever are present and the rest simply do not load. The quickest path for three of them is the hosted remote servers, which need no Node.js and no tokens and authenticate through an OAuth browser flow: https://swagger.mcp.smartbear.com/mcp, https://bugsnag.mcp.smartbear.com/mcp and https://zephyr.mcp.smartbear.com/mcp. Everything else — BearQ, Reflect, QMetry, QTM4J, PactFlow, Collaborator, functional testing — comes from the local package: Node.js 22+ and npx -y @smartbear/mcp@latest, configured with the relevant variables such as BUGSNAG_AUTH_TOKEN, SWAGGER_API_KEY, ZEPHYR_API_TOKEN, QMETRY_API_KEY, QTM4J_API_KEY, REFLECT_API_TOKEN, BEARQ_API_TOKEN, PACT_BROKER_TOKEN and COLLABORATOR_LOGIN_TICKET. Setting BUGSNAG_PROJECT_API_KEY narrows every BugSnag search to that one project; leave it blank to work across several.

Setup effort

One command plus a key — npx -y @smartbear/mcp@latest, then supply credentials