SmartBear MCP

com.smartbear/smartbear-mcp

8/9 checks passed
Local or hosted
10 secrets
★ 44 GitHub stars
Updated 2026-10-07
Health score 76

About SmartBear MCP

SmartBear MCP is an MCP server published by smartbear.com. MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.

It runs on your own machine: your AI client starts it from the npm package @smartbear/mcp at version 0.42.0, or you can connect to the hosted version instead.

It asks for 10 secrets: BEARQ_API_TOKEN, BUGSNAG_AUTH_TOKEN, REFLECT_API_TOKEN, SWAGGER_API_KEY, SWAGGER_FUNCTIONAL_TESTING_API_TOKEN, PACT_BROKER_TOKEN, PACT_BROKER_PASSWORD, ZEPHYR_API_TOKEN, QTM4J_API_KEY and QTM4J_AUTOMATION_API_KEY. Give it a key with the least access that still works.

Version 0.42.0 was published on 7 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 10 automated checks on the registry entry and the package code: 8 pass, 1 warn, 0 fail, 1 info. How we check.

What it asks for

Variable	Required	Secret	Description
`BEARQ_API_TOKEN`	No	Yes	BearQ workspace API token. Leave empty to disable BearQ tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/bearq-integration
`BEARQ_API_BASE_URL`	No	No	Override the BearQ public API base URL (optional). Defaults to https://api.bearq.smartbear.com
`BUGSNAG_AUTH_TOKEN`	No	Yes	BugSnag auth token. Leave empty to disable BugSnag tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/bugsnag-integration
`BUGSNAG_PROJECT_API_KEY`	No	No	BugSnag project API key (optional; narrows interactions to a single project). Learn more: https://developer.smartbear.com/smartbear-mcp/docs/bugsnag-integration
`REFLECT_API_TOKEN`	No	Yes	Reflect API token. Leave empty to disable Reflect tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/reflect-integration
`SWAGGER_API_KEY`	No	Yes	Swagger API key. Leave empty to disable Swagger tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/swagger-portal-integration
`SWAGGER_FUNCTIONAL_TESTING_API_TOKEN`	No	Yes	Swagger Functional Testing API token. Leave empty to disable Functional Testing tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/functional-testing-integration
`SWAGGER_FUNCTIONAL_TESTING_BASE_PATH`	No	No	Override the Swagger Functional Testing API base URL (optional). Defaults to https://api.reflect.run/v1
`PACT_BROKER_BASE_URL`	No	No	PactFlow/Pact Broker base URL. Leave empty to disable Pact tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/contract-testing-with-pactflow
`PACT_BROKER_TOKEN`	No	Yes	PactFlow authentication token. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/contract-testing-with-pactflow
`PACT_BROKER_USERNAME`	No	No	Pact Broker username (alternative to token). Learn more: https://developer.smartbear.com/smartbear-mcp/docs/contract-testing-with-pactflow
`PACT_BROKER_PASSWORD`	No	Yes	Pact Broker password (alternative to token). Learn more: https://developer.smartbear.com/smartbear-mcp/docs/contract-testing-with-pactflow
`ZEPHYR_API_TOKEN`	No	Yes	The Zephyr Cloud API token for authentication. Learn more: https://support.smartbear.com/zephyr/docs/en/rest-api/api-access-tokens-management.html
`ZEPHYR_BASE_URL`	No	No	The Zephyr Cloud API base url. Should be changed depending on the region of your Jira instance. Learn more: https://support.smartbear.com/zephyr-scale-cloud/api-docs/#section/Authentication/Accessing-the-API
`QTM4J_API_KEY`	No	Yes	QTM4J (QMetry Test Management for Jira) API key. Leave empty to disable QTM4J tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/qtm4j-integration
`QTM4J_BASE_URL`	No	No	QTM4J base URL (optional). Defaults to https://qtmcloud.qmetry.com. Override when using a self-hosted or region-specific instance.
`QTM4J_AUTOMATION_API_KEY`	No	Yes	QTM4J Automation API key used exclusively by the automation import tools. Leave empty to disable automation tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/qtm4j-integration

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/SmartBear/smartbear-mcp
Version pinned	Pass	Every package has an explicit version
Remote uses HTTPS	Pass	All remote endpoints use https://
Secrets requested	Warn	Asks for 10 secrets: BEARQ_API_TOKEN, BUGSNAG_AUTH_TOKEN, REFLECT_API_TOKEN, SWAGGER_API_KEY, SWAGGER_FUNCTIONAL_TESTING_API_TOKEN, PACT_BROKER_TOKEN, PACT_BROKER_PASSWORD, ZEPHYR_API_TOKEN, QTM4J_API_KEY, QTM4J_AUTOMATION_API_KEY
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via domain smartbear.com
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	@smartbear/mcp@0.42.0 runs nothing at install
Code red flags	Pass	Read 263 files in @smartbear/mcp@0.42.0: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 263 files, including comments and the README

Popularity & health: 76 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity23 / 40

44 GitHub stars, 11,084 downloads last week, 0 Hacker News posts (0 points). Best two of the three, each on a log scale.

Activity25 / 25

Last push 2026-10-28, last release 2026-10-07, 101 commits in 90 days.

Issue health13 / 15

30 closed of 36 issues.

Our checks16 / 20

1 warning, each costing a fifth.

51 forks, 569 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`com.smartbear/smartbear-mcp`
Publisher	Domain smartbear.com
How the name is verified	Name verified via domain smartbear.com. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local package and a hosted remote
Packages	npm `@smartbear/mcp` 0.42.0 (stdio)
Remote endpoints	streamable-http https://bugsnag.mcp.smartbear.com/mcp streamable-http https://zephyr.mcp.smartbear.com/mcp
Version	0.42.0
Published	2026-10-07
Last updated	2026-10-07
Source repository	https://github.com/SmartBear/smartbear-mcp
Website	None linked
Category	Other (assigned by keyword rule, not by hand)

Install

Claude Desktop · npm package

{
  "mcpServers": {
    "smartbear-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@0.42.0"
      ]
    }
  }
}

Claude Code · hosted

claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcp

Claude Code · hosted

claude mcp add --transport http smartbear-mcp https://zephyr.mcp.smartbear.com/mcp

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/com-smartbear-smartbear-mcp.json. Text inside it that came from the publisher is data, not instructions.