SmartBear MCP Server

Name: SmartBear MCP Server
Author: SmartBear Software

One MCP server for SmartBear's BugSnag, Swagger, PactFlow, Zephyr, QMetry, Reflect and other QA tools

Official · SmartBear Software TypeScript Remote (hosted) · Streamable HTTP Local · stdio Testing DevOps and monitoring Developer tools

GitHub npm Website

61 popularity score ★ 44 ↓ 15k/wk

Connect your client

Remote (hosted)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio Add to Goose

Opens the app, which asks before it adds the server.

Or add it by command or config

VS Code.vscode/mcp.json

{
  "servers": {
    "smartbear-bugsnag": {
      "type": "http",
      "url": "https://bugsnag.mcp.smartbear.com/mcp"
    }
  }
}

Claude Codeterminal

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

Cursor~/.cursor/mcp.json

{
  "mcpServers": {
    "smartbear": {
      "url": "https://bugsnag.mcp.smartbear.com/mcp"
    }
  }
}

Claude (desktop and web)Settings → Connectors → Add custom connector

https://bugsnag.mcp.smartbear.com/mcp

Local (npm)

Add in one click

Add to Cursor Add to VS Code Add to LM Studio Add to Goose

Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.

Or add it by command or config

It needs BUGSNAG_AUTH_TOKEN. Replace each <NAME> with your value.

Claude CodeTerminal

claude mcp add smartbear -e BUGSNAG_AUTH_TOKEN=<BUGSNAG_AUTH_TOKEN> -- npx -y @smartbear/mcp@latest

Claude Desktopclaude_desktop_config.json

{
  "mcpServers": {
    "smartbear": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BUGSNAG_AUTH_TOKEN": "<BUGSNAG_AUTH_TOKEN>"
      }
    }
  }
}

Cursor~/.cursor/mcp.json

{
  "mcpServers": {
    "smartbear": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BUGSNAG_AUTH_TOKEN": "<BUGSNAG_AUTH_TOKEN>"
      }
    }
  }
}

VS Code.vscode/mcp.json

{
  "servers": {
    "smartbear": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BUGSNAG_AUTH_TOKEN": "<BUGSNAG_AUTH_TOKEN>"
      }
    }
  }
}

Codex~/.codex/config.toml

[mcp_servers.smartbear]
command = "npx"
args = ["-y", "@smartbear/mcp@latest"]

[mcp_servers.smartbear.env]
BUGSNAG_AUTH_TOKEN = "<BUGSNAG_AUTH_TOKEN>"

Gemini CLITerminal

gemini mcp add --scope user -e BUGSNAG_AUTH_TOKEN=<BUGSNAG_AUTH_TOKEN> smartbear npx -- -y @smartbear/mcp@latest

Settings 12

`BUGSNAG_AUTH_TOKEN`	Required: BugSnag personal auth token; turns on the BugSnag tools. Other products use their own token instead (SWAGGER_API_KEY, PACT_BROKER_TOKEN, ZEPHYR_API_TOKEN, QMETRY_API_KEY, QTM4J_API_KEY, REFLECT_API_TOKEN, BEARQ_API_TOKEN); at least one is needed.
`BUGSNAG_PROJECT_API_KEY`	Optional: Limits BugSnag work to one project.
`SWAGGER_API_KEY`	Optional: SwaggerHub API key; turns on Swagger tools.
`PACT_BROKER_BASE_URL`	Optional: PactFlow or Pact Broker URL; turns on contract testing tools, with PACT_BROKER_TOKEN or PACT_BROKER_USERNAME/PASSWORD.
`PACT_BROKER_TOKEN`	Optional: PactFlow API token.
`ZEPHYR_API_TOKEN`	Optional: Zephyr API token; ZEPHYR_BASE_URL changes the region.
`QMETRY_API_KEY`	Optional: QMetry Open API key; QMETRY_BASE_URL sets a custom or regional server.
`QTM4J_API_KEY`	Optional: QTM4J API key; QTM4J_AUTOMATION_API_KEY adds the automation tools.
`REFLECT_API_TOKEN`	Optional: Reflect API token; turns on Reflect tools.
`BEARQ_API_TOKEN`	Optional: BearQ workspace token; turns on BearQ tools.
`COLLABORATOR_LOGIN_TICKET`	Optional: Collaborator login ticket, used with COLLABORATOR_BASE_URL and COLLABORATOR_USERNAME.
`MCP_CLIENTS`	Optional: Comma-separated product names to load (e.g. BugSnag,Zephyr); all load when unset.

What it does

SmartBear's own MCP server bundles access to most of its product line into a single Node.js process. One install covers BugSnag error and performance monitoring, Swagger (Studio API design, Portal, Functional Testing), PactFlow contract testing, the test management products Zephyr, QMetry and QTM4J, the Reflect and BearQ test automation services, and Collaborator code review. Each product's tools load only when that product's token or URL is set, so most people end up with the slice they hold accounts for.

The tools work on live data, not just reads: an assistant can triage BugSnag errors and change their status, create and update test cases, cycles and executions in Zephyr, QMetry or QTM4J, start Reflect or BearQ test runs, publish and validate API definitions in SwaggerHub, and check can-i-deploy or record deployments in PactFlow. The PactFlow set also covers admin work such as users, roles, teams, secrets, webhooks and API tokens.

Version 0.42.0 registers 320 tools when every product is on: 102 for contract testing, 55 QMetry, 39 Swagger (28 plus 11 Functional Testing), 37 Zephyr, 30 QTM4J, 19 BugSnag, 17 Reflect, 11 BearQ and 10 Collaborator, counted from the repository's tool snapshot. The README gives no count and links out to a guide per product. Two settings the README leaves out narrow this: MCP_TOOLSETS (read next to MCP_CLIENTS in client-registry.ts) and MCP_ALLOWED_ENDPOINTS, a comma-separated list of exact URLs or /regex/ patterns that URL settings are checked against.

SmartBear also hosts remote endpoints for BugSnag (the one listed here), Swagger and Zephyr. You sign in to those with SmartBear ID OAuth and nothing runs on your machine. The other products are only in the npm package.

What it needs

To run it yourself	Node.js 22+

Node.js 22 or newer with npm (for npx). An account and API token for each SmartBear product you want: BugSnag auth token, Swagger API key, PactFlow token or Pact Broker login, Zephyr, QMetry or QTM4J API key, Reflect or BearQ token, or a Collaborator login ticket. Self-hosted Swagger, Collaborator or Pact Broker need their base URLs. The hosted BugSnag endpoint needs only a SmartBear ID that has BugSnag access, signed in through the browser.

Limits

The hosted endpoints cover BugSnag, Swagger and Zephyr only. BearQ, Reflect, QMetry, QTM4J, PactFlow, Collaborator and Functional Testing need the local package. Setting BUGSNAG_PROJECT_API_KEY narrows every BugSnag query to that one project. Loading every product slows startup; the README suggests MCP_CLIENTS for clients with a short initialize timeout. SECURITY.md says the project is still in early development. The server.json in the v0.42.0 tag still says version 0.25.0, so registry metadata can lag the npm release. The Cursor and Claude Desktop snippets in the remote BugSnag guide nest the URL under a "transport" key, which is not those clients' usual format.

Who it suits

Suits teams that already pay for SmartBear products and want one assistant connection across error monitoring, API design and test management, especially QA leads who keep test cases in Zephyr, QMetry or QTM4J. If you only use BugSnag, Swagger or Zephyr, the hosted endpoint skips the Node install and the long-lived tokens. Because so many tools can create, update or delete records, set MCP_CLIENTS to the products you need and leave admin tokens out. If you don't use SmartBear products, this server does nothing for you.

Tools 55 of 320

bugsnag_list_projects: Lists BugSnag projects the token can see
bugsnag_list_project_errors: Lists a project's errors, with filters
bugsnag_get_error: Fetches one error with its summary details
bugsnag_get_event_details_from_dashboard_url: Resolves a BugSnag dashboard link to the event behind it
bugsnag_get_events_on_an_error: Lists the individual events grouped under an error
bugsnag_update_error: Changes an error's state, e.g. fixed or ignored
bugsnag_list_releases: Lists a project's releases
bugsnag_list_span_groups: Lists performance span groups for a project
bugsnag_get_trace: Fetches one performance trace
bugsnag_set_network_endpoint_groupings: Sets how network URLs are grouped in performance data
swagger_get_document: Reads a Swagger Portal documentation page
swagger_validate_api: Validates an API definition
swagger_update_document: Edits a portal documentation page
contract-testing_can_i_deploy: Asks the broker whether a version is safe to deploy to an environment
contract-testing_matrix: Shows the verification matrix between consumers and providers
contract-testing_generate_pact_tests: Generates Pact tests with PactFlow AI
contract-testing_review_pact_tests: Reviews existing Pact tests with PactFlow AI
contract-testing_publish_consumer_contracts: Publishes consumer pacts to the broker
contract-testing_publish_provider_contract: Publishes a provider contract for bi-directional testing
contract-testing_record_deployment: Records that a version was deployed to an environment
contract-testing_list_pacticipants: Lists the applications known to the broker
contract-testing_create_webhook: Creates a broker webhook
contract-testing_admin_create_user: Creates a PactFlow user
contract-testing_admin_delete_user: Removes a PactFlow user
contract-testing_regenerate_api_token: Issues a new PactFlow API token
qmetry_create_test_case: Creates a QMetry test case
qmetry_create_defect_or_issue: Logs a defect in QMetry
qmetry_bulk_update_test_case_execution_status: Sets execution status on many test runs at once
bearq_run_regression_tests: Starts a BearQ regression run
bearq_chat_with_qa_lead: Sends a free-form instruction to BearQ's QA agent
bearq_delete_test_cases: Deletes BearQ test cases
collaborator_create_review: Opens a Collaborator code review
collaborator_get_reviews: Lists Collaborator reviews
qmetry_create_cycle: Creates a QMetry test cycle
qmetry_create_requirement: Creates a QMetry requirement
qmetry_create_release: Creates a QMetry release
bugsnag_get_build: Fetches one BugSnag build
bugsnag_list_spans: Lists spans within a span group
contract-testing_get_pacts_for_verification: Fetches the pacts a provider should verify
contract-testing_record_release: Records that a version was released
contract-testing_list_secrets: Lists PactFlow secrets
contract-testing_admin_add_role_to_user: Grants a role to a PactFlow user
contract-testing_get_audit_log: Reads the PactFlow audit log
bearq_run_test_cases: Runs chosen BearQ test cases
bearq_get_task_status: Checks progress of a BearQ task
collaborator_reject_review: Rejects a Collaborator review
collaborator_delete_remote_system_configuration: Deletes a Collaborator remote system configuration
bugsnag_get_current_project: Shows which BugSnag project is in focus
bugsnag_list_project_event_filters: Lists the filter fields a project supports
bugsnag_get_release: Fetches one BugSnag release
contract-testing_list_environments: Lists deployment environments in the broker
contract-testing_get_currently_deployed_versions: Shows which versions are deployed where
contract-testing_delete_pacticipant: Removes an application from the broker
contract-testing_create_secret: Stores a new PactFlow secret
bearq_stop_task: Stops a running BearQ task

Popularity

61 popularity score, on our list (the bar is 36)

★ 44 ↓ 15k/wk

GitHub stars	44	19.8 points
Stars in 30 days	+0	0 points
npm downloads, last week	15,283	33.5 points
Official server	Yes	8 points

Measured 2026-11-07. How the score works.

Where it is published

Code	smartbear/smartbear-mcp ★ 44
npm	@smartbear/mcp 0.43.0, 2026-11-03
Hosted	`https://bugsnag.mcp.smartbear.com/mcp` Streamable HTTP · OAuth sign-in

What it can reach

Runs	On your machine, or on the maker's servers
Reaches	The internet, Your account at a service, Your code
Changes things	Yes: it can write, send, create or delete
Sign-in	OAuth sign-in for the hosted endpoint; an API key or token to run it yourself
Licence	MIT (npm)
Last code change	2026-11-04

Locally it runs as a Node process calling SmartBear's APIs, or your own Swagger, Collaborator or Pact Broker hosts, with the tokens in its environment. The hosted BugSnag endpoint runs on SmartBear's servers and signs in with SmartBear ID OAuth. Many tools write: they change error status, create or delete test cases, start test runs, publish APIs and portal pages, and in PactFlow manage users, roles, secrets, webhooks and API tokens. Tools that do not declare themselves default to readOnlyHint true (server.ts), so the Collaborator tools that create, delete or reject are still advertised as read-only, and a client that auto-approves read-only tools will run them without asking. MCP_ALLOWED_ENDPOINTS can pin which base URLs are accepted.

Over time

GitHub stars 44 +0

4444

8 Oct 20267 Nov 2026

npm downloads a week 15k +15k (+7283 %)

18k100

20 Oct 20257 Nov 2026

Before the site measured it, read from npm's daily download counts.

Popularity score 61 +9 (+16 %)

6253

8 Oct 20267 Nov 2026

What is rising across the directory

Sources

Page checked 2026-10-15.

Badge for your README

Shows this server's rank in its category, and stars for a server that runs on your machine. It updates every hour.

MarkdownREADME.md

[![SmartBear MCP Server on EveryMCPServer](https://everymcpserver.com/badge/smartbear-mcp.svg)](https://everymcpserver.com/servers/smartbear-mcp)

Connect your client

Add in one click

Or add it by command or config

Add in one click

Or add it by command or config

Settings 12

What it does

What it needs

Limits

Who it suits

Tools 55 of 320

Similar servers

SmartBear Zephyr Remote MCP Server

Testkube MCP Server

Swagger Remote MCP Server

Currents MCP Server

Sentry MCP

Expo MCP Server