SmartBear MCP logo

SmartBear MCP

Connect AI assistants to SmartBear testing, monitoring, API, contract-testing, and review tools through MCP.

Install SmartBear MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "smartbear-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

SmartBear MCP MCP server exposes SmartBear APIs to AI assistants through natural-language MCP tools. It covers BearQ, BugSnag, Reflect, Swagger, PactFlow, Pact Broker, QMetry, QTM4J, Zephyr, and Collaborator, with some Swagger, BugSnag, and Zephyr access available through hosted remote endpoints. Run the bundled npm server locally when you need the broader product set or want to configure credentials in your MCP client. It fits developer workflows involving test management, API work, error investigation, contract testing, and code review administration.

Use cases

  • Investigate BugSnag errors from an AI-assisted development workflow
  • Manage and execute QA tests across SmartBear test products
  • Generate and standardize APIs through Swagger
  • Inspect contract-testing data from PactFlow or Pact Broker
  • Manage test cases and reviews across SmartBear platforms

Key features

  • Exposes SmartBear APIs through MCP tools
  • Supports local stdio execution with the @smartbear/mcp npm package
  • Provides hosted remote endpoints for Swagger, BugSnag, and Zephyr
  • Connects to test management, monitoring, API, contract-testing, and review products
  • Enables per-product credential and endpoint configuration

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

20/21 checks healthy over the last 90d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · @smartbear/mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars44Stargazers on the source repository.
npm downloads33kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How SmartBear MCP works

What SmartBear MCP MCP server does

SmartBear MCP connects MCP-compatible AI assistants with SmartBear products used for testing, monitoring, API management, contract testing, and review workflows. Its supported product areas include BearQ, BugSnag, Reflect, Swagger, PactFlow, Pact Broker, QMetry, QTM4J, Zephyr, and Collaborator.

The exposed capabilities vary by product. They include QA test management and execution, error monitoring and debugging, test discovery, API and domain management, API generation from prompts, API standardization, contract testing, review management, and remote-system configuration management.

How it works

The local distribution is published as the @smartbear/mcp npm package and runs as a standard MCP server over stdio. An MCP client starts the package with npx, then supplies credentials and product-specific connection settings through environment variables. Product credentials can be omitted to disable the corresponding tools, allowing one local server configuration to cover only the SmartBear services in use.

SmartBear also hosts remote MCP endpoints for Swagger, BugSnag, and Zephyr:

  • https://swagger.mcp.smartbear.com/mcp
  • https://bugsnag.mcp.smartbear.com/mcp
  • https://zephyr.mcp.smartbear.com/mcp

These hosted endpoints use an OAuth browser flow and can be connected directly from an MCP client. Multiple remote servers can be used at the same time.

Setup and configuration

Local installation requires Node.js 22 or newer and npm. Add @smartbear/mcp@latest as a stdio server in the MCP client configuration, or use the client’s MCP server installation flow. The server accepts separate settings for products such as BearQ, BugSnag, Reflect, Swagger, Pact Broker, QMetry, Zephyr, Collaborator, QTM4J, and Swagger Functional Testing.

Authentication is configured per product. Depending on the integration, settings include API tokens or keys, base URLs, usernames, passwords, login tickets, and service-specific paths. BugSnag can also receive a project API key to restrict searches to one project; leaving that value empty permits searches across multiple projects.

Remote connections are an alternative for Swagger, BugSnag, and Zephyr. They do not require a local Node.js installation or local API tokens, because authentication takes place through the OAuth flow.

Tools and capabilities

  • Query and work with BugSnag error-monitoring data.
  • Manage and execute QA tests through BearQ and Reflect.
  • Manage APIs and domains with Swagger, including prompt-based API generation and standardization.
  • Discover API tests through Swagger Functional Testing.
  • Work with contract-testing data through PactFlow and Pact Broker.
  • Manage tests in QMetry, QTM4J, and Zephyr.
  • Manage reviews and remote-system configuration in Collaborator.

Limitations and notes

The hosted remote option covers only Swagger, BugSnag, and Zephyr. BearQ, Reflect, QMetry, QTM4J, PactFlow, Collaborator, and Swagger Functional Testing are available through the local npm package. Access also depends on having the relevant SmartBear product and valid credentials. Product-specific environment variables are optional individually, but integrations cannot be used without their corresponding authentication and connection settings.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about SmartBear MCP

SmartBear MCP is an MCP server that connects AI assistants to SmartBear products including BugSnag, Reflect, Swagger, BearQ, PactFlow, QMetry, Zephyr, QTM4J, and Collaborator. Its tools support error monitoring, test management and execution, API work, contract testing, test discovery, and review configuration.

Install it through the `@smartbear/mcp` npm package and configure it as a stdio MCP server. The local setup uses Node.js 22 or newer and npm; clients can launch it with `npx -y @smartbear/mcp@latest` and product-specific environment variables.

Yes, SmartBear MCP works with VS Code and Copilot through the “MCP: Add server…” command or a manual `.vscode/mcp.json` configuration. The local package runs as a stdio server, with credentials supplied through the configuration.

Yes, for Swagger, BugSnag, and Zephyr you can connect to SmartBear-hosted remote MCP endpoints without a local Node.js installation or API tokens. Authentication uses an OAuth browser flow. Other listed products require the local npm package.

The local package supports all listed product integrations, including BearQ, BugSnag, Reflect, Swagger, PactFlow, Pact Broker, QMetry, QTM4J, Zephyr, Collaborator, and Swagger Functional Testing. Product tools activate when their relevant credentials and settings are configured.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSmartBear MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/smartbear-mcp?style=directory)](https://allmcps.com/mcp/smartbear-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/smartbear-mcp"><img src="https://allmcps.com/api/badge/smartbear-mcp?style=directory" alt="SmartBear MCP on AllMCPs" /></a>