Skip to content

Summary

SmartBear's official MCP server, putting BugSnag error monitoring, Reflect and QMetry test management, Zephyr, PactFlow contract testing and the Swagger API Hub behind one agent connection.

Features

  • One server across BugSnag, Reflect, BearQ, Swagger/API Hub, PactFlow, QMetry, QTM4J, Zephyr and Collaborator
  • Hosted remote servers with OAuth for BugSnag, Swagger and Zephyr — no local install
  • Per-product credentials are all optional; unused products drop out of the tool list
  • Swagger Studio tools generate and standardise APIs from a prompt
  • Contract testing through PactFlow and the Pact Broker
  • Optional BugSnag project scoping to keep searches inside one project

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "SmartBear MCP" tools will be available.
{
  "mcpServers": {
    "smartbear-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BUGSNAG_AUTH_TOKEN": "your_bugsnag_auth_token",
        "SWAGGER_API_KEY": "your_swagger_api_key"
      }
    }
  }
}

Description

SmartBear ships a single official MCP server that fronts its whole testing and monitoring portfolio, so an agent debugging a production error and an agent authoring an API contract talk to the same connection.

What it reaches
  • BugSnag — error monitoring and debugging: find an error, read its stack traces and breadcrumbs, and trace it back to a release.
  • Reflect and BearQ — test management and execution, including AI-driven QA runs.
  • Swagger / API Hub — Portal and product management, Studio for API and domain management (with AI-generated APIs from a prompt and automatic standardisation), plus functional-test discovery.
  • PactFlow and Pact Broker — contract testing.
  • QMetry, QTM4J and Zephyr — test management, including Zephyr inside Jira.
  • Collaborator — code and document review, plus remote system configuration.
Two ways to connect

For BugSnag, Swagger and Zephyr, SmartBear hosts remote MCP servers at bugsnag.mcp.smartbear.com, swagger.mcp.smartbear.com and zephyr.mcp.smartbear.com. Point a client at the URL and authenticate through a browser OAuth flow — no Node.js, no tokens to paste.

Everything else, and any setup that prefers local execution, runs from the @smartbear/mcp npm package over stdio. Each product's credentials are supplied as environment variables and every one of them is optional: omit the products you do not use and their tools disappear from the surface. Supplying a BugSnag project API key narrows every search to that project; leaving it blank lets the agent work across projects.

The server is open source on GitHub with published test coverage, and per-product integration guides live at developer.smartbear.com.

Related MCP Servers

Featured

The official W&B MCP server: query experiment runs, Weave LLM traces, artifacts and registries in natural language, and write findings back as a W&B report.

Checkly's hosted MCP server gives an agent read access to your synthetic monitoring account — check health, failing results, test sessions, Rocky AI root-cause analyses, incidents and status pages — over streamable HTTP with OAuth.

MCP: Memfault MCP Server

by Memfault (Nordic Semiconductor)

Remote MCP server for Memfault (Nordic Semiconductor) exposing 18 read-only tools over device fleet telemetry — device vitals, timeseries, crash issues, traces, metrics and software versions.

Browse all MCP servers →