Developer · Remote MCP server

SmartBear MCP

MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.smartbear/smartbear-mcp
Version
0.41.3
Status
Active
Category
developer
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-09-30
Updated
2026-09-30
Publisher
com.smartbear
Repository
github.com/SmartBear/smartbear-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://bugsnag.mcp.smartbear.com/mcpNone
Streamable HTTPhttps://zephyr.mcp.smartbear.com/mcpNone

Packages

RegistryPackageVersionTransportEnvironment variables
npm@smartbear/mcp0.41.3stdioBEARQ_API_TOKEN (secret), BEARQ_API_BASE_URL, BUGSNAG_AUTH_TOKEN (secret), BUGSNAG_PROJECT_API_KEY, REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), SWAGGER_FUNCTIONAL_TESTING_BASE_PATH, PACT_BROKER_BASE_URL, PACT_BROKER_TOKEN (secret), PACT_BROKER_USERNAME, PACT_BROKER_PASSWORD (secret), ZEPHYR_API_TOKEN (secret), ZEPHYR_BASE_URL, QTM4J_API_KEY (secret), QTM4J_BASE_URL, QTM4J_AUTOMATION_API_KEY (secret)

How to connect SmartBear MCP

SmartBear MCP is a remote MCP server: there is nothing to install. Its endpoints are https://bugsnag.mcp.smartbear.com/mcp and https://zephyr.mcp.smartbear.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @smartbear/mcp version 0.41.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @smartbear/mcp@0.41.3. It reads these environment variables: BEARQ_API_TOKEN (secret), BEARQ_API_BASE_URL, BUGSNAG_AUTH_TOKEN (secret), BUGSNAG_PROJECT_API_KEY, REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), SWAGGER_FUNCTIONAL_TESTING_BASE_PATH, PACT_BROKER_BASE_URL, PACT_BROKER_TOKEN (secret), PACT_BROKER_USERNAME, PACT_BROKER_PASSWORD (secret), ZEPHYR_API_TOKEN (secret), ZEPHYR_BASE_URL, QTM4J_API_KEY (secret), QTM4J_BASE_URL and QTM4J_AUTOMATION_API_KEY (secret); set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "smartbear-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@0.41.3"
      ],
      "env": {
        "BEARQ_API_TOKEN": "<secret>",
        "BEARQ_API_BASE_URL": "<value>",
        "BUGSNAG_AUTH_TOKEN": "<secret>",
        "BUGSNAG_PROJECT_API_KEY": "<value>",
        "REFLECT_API_TOKEN": "<secret>",
        "SWAGGER_API_KEY": "<secret>",
        "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN": "<secret>",
        "SWAGGER_FUNCTIONAL_TESTING_BASE_PATH": "<value>",
        "PACT_BROKER_BASE_URL": "<value>",
        "PACT_BROKER_TOKEN": "<secret>",
        "PACT_BROKER_USERNAME": "<value>",
        "PACT_BROKER_PASSWORD": "<secret>",
        "ZEPHYR_API_TOKEN": "<secret>",
        "ZEPHYR_BASE_URL": "<value>",
        "QTM4J_API_KEY": "<secret>",
        "QTM4J_BASE_URL": "<value>",
        "QTM4J_AUTOMATION_API_KEY": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 6,250 →
ServerRunsEndpoint or package
Slush Meme MCPAI-native meme coin launchpad on Avalanche. Deploy tokens, simulate trades, query risk.Local · stdionpm: slush-meme-mcp-server
SmallprintThe small print of MCP servers, skills and plugins, hashed, diffed and graded, from the record.Local · stdionpm: smallprint-mcp
Smart ConnectionsMCP server for Obsidian Connections. Semantic search using your vault's embeddings.Local · stdionpm: @gogogadgetbytes/smart-connections-mcp
Smart Connections MCPLocal semantic search over Obsidian vaults via Connections embeddings. Multi-vault, private.Local · stdionpm: smart-connections-mcp
SmartFetchPaid fallback for public webpages: clean text, Markdown, links, metadata, and JavaScript rendering.Remote · HTTPsmartfetch-production-ea53.up.railway.app
Smartguard MCPSmartGuard MCP Server - AI-powered contract security audit tools for Claude Code, Cursor,...Local · stdionpm: smartguard-mcp
smbCloud Mail & AuthEmail infrastructure and authentication for developers: domains, inbox routes, auth apps, deploys.Local · stdionpm: @smbcloud/cli
SMI Aware AssistantRemote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.Remote · HTTPmcp.smiaware.com