SmartBear

listing.by

Query and manage BugSnag, Swagger, PactFlow, Reflect, Zephyr, QMetry and other SmartBear testing and monitoring tools.

state.local.long (state.local.title)listing.badge.runs_withstate.key.long

listing.install

listing.local.explain

npx -y @smartbear/mcp@latest

listing.local.needs listing.local.note

  • BEARQ_API_TOKEN listing.env.secret listing.env.optional BearQ workspace API token. Leave empty to disable BearQ tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/bearq-integra…
  • BEARQ_API_BASE_URL listing.env.optional Override the BearQ public API base URL (optional). Defaults to https://api.bearq.smartbear.com
  • BUGSNAG_AUTH_TOKEN listing.env.secret listing.env.optional BugSnag auth token. Leave empty to disable BugSnag tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/bugsnag-integration
  • BUGSNAG_PROJECT_API_KEY listing.env.optional BugSnag project API key (optional; narrows interactions to a single project). Learn more…
  • REFLECT_API_TOKEN listing.env.secret listing.env.optional Reflect API token. Leave empty to disable Reflect tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/reflect-integration
  • SWAGGER_API_KEY listing.env.secret listing.env.optional Swagger API key. Leave empty to disable Swagger tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/swagger-portal-integr…

listing.share.h

listing.share.p_local

mcp.tc/i/smartbear

listing.about

Connects an assistant to SmartBear products: BearQ, BugSnag, Reflect, Swagger (Portal, Studio, Functional Testing), PactFlow and Pact Broker, QMetry, QTM4J, Zephyr and Collaborator. You can look up error data, manage API definitions, work with contract tests and handle test management through natural language.

Runs locally as the npm package @smartbear/mcp (Node.js 22+) over stdio. Each product is enabled by setting its own token or API key, and unused products can be left blank. SmartBear also hosts OAuth-based remote servers for BugSnag, Swagger and Zephyr, which need no local install or tokens.

listing.can

  • Query BugSnag error monitoring data
  • Manage Swagger Portal and Studio APIs and domains
  • Work with PactFlow contract testing
  • Run and manage Reflect and BearQ tests
  • Access Zephyr, QMetry and QTM4J test management
  • Manage Collaborator reviews

listing.tools

listing.notools.key

listing.prompts

  • Show the most frequent unresolved BugSnag errors in my project

  • List the APIs in my Swagger Studio organization

  • Check contract test status for my consumer in PactFlow

  • List recent Zephyr test cycles for my project

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio smartbear --env "BEARQ_API_TOKEN=<YOUR_BEARQ_API_TOKEN>" --env "BUGSNAG_AUTH_TOKEN=<YOUR_BUGSNAG_AUTH_TOKEN>" --env "REFLECT_API_TOKEN=<YOUR_REFLECT_API_TOKEN>" --env "SWAGGER_API_KEY=<YOUR_SWAGGER_API_KEY>" --env "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN=<YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN>" --env "PACT_BROKER_TOKEN=<YOUR_PACT_BROKER_TOKEN>" --env "PACT_BROKER_PASSWORD=<YOUR_PACT_BROKER_PASSWORD>" --env "ZEPHYR_API_TOKEN=<YOUR_ZEPHYR_API_TOKEN>" -- npx -y @smartbear/mcp@latest
  1. Start Claude Code and type /mcp. smartbear should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "smartbear": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BEARQ_API_TOKEN": "<YOUR_BEARQ_API_TOKEN>",
        "BUGSNAG_AUTH_TOKEN": "<YOUR_BUGSNAG_AUTH_TOKEN>",
        "REFLECT_API_TOKEN": "<YOUR_REFLECT_API_TOKEN>",
        "SWAGGER_API_KEY": "<YOUR_SWAGGER_API_KEY>",
        "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN": "<YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN>",
        "PACT_BROKER_TOKEN": "<YOUR_PACT_BROKER_TOKEN>",
        "PACT_BROKER_PASSWORD": "<YOUR_PACT_BROKER_PASSWORD>",
        "ZEPHYR_API_TOKEN": "<YOUR_ZEPHYR_API_TOKEN>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "smartbear": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BEARQ_API_TOKEN": "<YOUR_BEARQ_API_TOKEN>",
        "BUGSNAG_AUTH_TOKEN": "<YOUR_BUGSNAG_AUTH_TOKEN>",
        "REFLECT_API_TOKEN": "<YOUR_REFLECT_API_TOKEN>",
        "SWAGGER_API_KEY": "<YOUR_SWAGGER_API_KEY>",
        "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN": "<YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN>",
        "PACT_BROKER_TOKEN": "<YOUR_PACT_BROKER_TOKEN>",
        "PACT_BROKER_PASSWORD": "<YOUR_PACT_BROKER_PASSWORD>",
        "ZEPHYR_API_TOKEN": "<YOUR_ZEPHYR_API_TOKEN>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "smartbear": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BEARQ_API_TOKEN": "${input:bearq-api-token}",
        "BUGSNAG_AUTH_TOKEN": "${input:bugsnag-auth-token}",
        "REFLECT_API_TOKEN": "${input:reflect-api-token}",
        "SWAGGER_API_KEY": "${input:swagger-api-key}",
        "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN": "${input:swagger-functional-testing-api-token}",
        "PACT_BROKER_TOKEN": "${input:pact-broker-token}",
        "PACT_BROKER_PASSWORD": "${input:pact-broker-password}",
        "ZEPHYR_API_TOKEN": "${input:zephyr-api-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "bearq-api-token",
      "description": "BEARQ_API_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "bugsnag-auth-token",
      "description": "BUGSNAG_AUTH_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "reflect-api-token",
      "description": "REFLECT_API_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "swagger-api-key",
      "description": "SWAGGER_API_KEY",
      "password": true
    },
    {
      "type": "promptString",
      "id": "swagger-functional-testing-api-token",
      "description": "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "pact-broker-token",
      "description": "PACT_BROKER_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "pact-broker-password",
      "description": "PACT_BROKER_PASSWORD",
      "password": true
    },
    {
      "type": "promptString",
      "id": "zephyr-api-token",
      "description": "ZEPHYR_API_TOKEN",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "smartbear": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BEARQ_API_TOKEN": "<YOUR_BEARQ_API_TOKEN>",
        "BUGSNAG_AUTH_TOKEN": "<YOUR_BUGSNAG_AUTH_TOKEN>",
        "REFLECT_API_TOKEN": "<YOUR_REFLECT_API_TOKEN>",
        "SWAGGER_API_KEY": "<YOUR_SWAGGER_API_KEY>",
        "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN": "<YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN>",
        "PACT_BROKER_TOKEN": "<YOUR_PACT_BROKER_TOKEN>",
        "PACT_BROKER_PASSWORD": "<YOUR_PACT_BROKER_PASSWORD>",
        "ZEPHYR_API_TOKEN": "<YOUR_ZEPHYR_API_TOKEN>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add smartbear --env "BEARQ_API_TOKEN=<YOUR_BEARQ_API_TOKEN>" --env "BUGSNAG_AUTH_TOKEN=<YOUR_BUGSNAG_AUTH_TOKEN>" --env "REFLECT_API_TOKEN=<YOUR_REFLECT_API_TOKEN>" --env "SWAGGER_API_KEY=<YOUR_SWAGGER_API_KEY>" --env "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN=<YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN>" --env "PACT_BROKER_TOKEN=<YOUR_PACT_BROKER_TOKEN>" --env "PACT_BROKER_PASSWORD=<YOUR_PACT_BROKER_PASSWORD>" --env "ZEPHYR_API_TOKEN=<YOUR_ZEPHYR_API_TOKEN>" -- npx -y @smartbear/mcp@latest

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.smartbear]
command = "npx"
args = ["-y", "@smartbear/mcp@latest"]
env = { BEARQ_API_TOKEN = "<YOUR_BEARQ_API_TOKEN>", BUGSNAG_AUTH_TOKEN = "<YOUR_BUGSNAG_AUTH_TOKEN>", REFLECT_API_TOKEN = "<YOUR_REFLECT_API_TOKEN>", SWAGGER_API_KEY = "<YOUR_SWAGGER_API_KEY>", SWAGGER_FUNCTIONAL_TESTING_API_TOKEN = "<YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN>", PACT_BROKER_TOKEN = "<YOUR_PACT_BROKER_TOKEN>", PACT_BROKER_PASSWORD = "<YOUR_PACT_BROKER_PASSWORD>", ZEPHYR_API_TOKEN = "<YOUR_ZEPHYR_API_TOKEN>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "BEARQ_API_TOKEN=<YOUR_BEARQ_API_TOKEN>" -e "BUGSNAG_AUTH_TOKEN=<YOUR_BUGSNAG_AUTH_TOKEN>" -e "REFLECT_API_TOKEN=<YOUR_REFLECT_API_TOKEN>" -e "SWAGGER_API_KEY=<YOUR_SWAGGER_API_KEY>" -e "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN=<YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN>" -e "PACT_BROKER_TOKEN=<YOUR_PACT_BROKER_TOKEN>" -e "PACT_BROKER_PASSWORD=<YOUR_PACT_BROKER_PASSWORD>" -e "ZEPHYR_API_TOKEN=<YOUR_ZEPHYR_API_TOKEN>" smartbear npx -- -y @smartbear/mcp@latest

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "smartbear": {
      "command": "npx",
      "args": [
        "-y",
        "@smartbear/mcp@latest"
      ],
      "env": {
        "BEARQ_API_TOKEN": "<YOUR_BEARQ_API_TOKEN>",
        "BUGSNAG_AUTH_TOKEN": "<YOUR_BUGSNAG_AUTH_TOKEN>",
        "REFLECT_API_TOKEN": "<YOUR_REFLECT_API_TOKEN>",
        "SWAGGER_API_KEY": "<YOUR_SWAGGER_API_KEY>",
        "SWAGGER_FUNCTIONAL_TESTING_API_TOKEN": "<YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN>",
        "PACT_BROKER_TOKEN": "<YOUR_PACT_BROKER_TOKEN>",
        "PACT_BROKER_PASSWORD": "<YOUR_PACT_BROKER_PASSWORD>",
        "ZEPHYR_API_TOKEN": "<YOUR_ZEPHYR_API_TOKEN>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

listing.faq

Can I paste mcp.tc/i/smartbear into my MCP client?

No. SmartBear runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @smartbear/mcp@latest.

Does SmartBear need an API key?

Yes. It reads BEARQ_API_TOKEN, BUGSNAG_AUTH_TOKEN, REFLECT_API_TOKEN, SWAGGER_API_KEY, SWAGGER_FUNCTIONAL_TESTING_API_TOKEN, PACT_BROKER_TOKEN, PACT_BROKER_PASSWORD and ZEPHYR_API_TOKEN from its environment, and BEARQ_API_TOKEN, BUGSNAG_AUTH_TOKEN, REFLECT_API_TOKEN, SWAGGER_API_KEY, SWAGGER_FUNCTIONAL_TESTING_API_TOKEN, PACT_BROKER_TOKEN, PACT_BROKER_PASSWORD and ZEPHYR_API_TOKEN are secrets. Put the value in your client's config on your own machine, never in a shared file.

Is SmartBear a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @smartbear/mcp@latest, which needs Node.js.

What can SmartBear do?

You can query BugSnag error monitoring data, manage Swagger Portal and Studio APIs and domains and work with PactFlow contract testing.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read SmartBear's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![SmartBear on mcp.tc](https://mcp.tc/i/smartbear/badge.svg)](https://mcp.tc/i/smartbear)
HTML
<a href="https://mcp.tc/i/smartbear"><img src="https://mcp.tc/i/smartbear/badge.svg" alt="SmartBear on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/smartbear.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/smartbear" title="SmartBear on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/smartbear.json

listing.em.fields

listing.related

listing.more_in

  • Swagger

    SmartBear

    state.auth.label (state.auth.title)

    Search, read and manage API definitions and portals in SwaggerHub (Swagger Studio) from your AI assistant.

    mcp.tc/i/swagger

  • GitKraken

    Developer Tools

    state.local.label (state.local.title)

    Work with Git, pull requests and issues across GitHub, GitLab, Bitbucket, Azure DevOps and Jira from your assistant.

    mcp.tc/i/gitkraken

  • Unleash

    Developer Tools

    state.local.label (state.local.title)

    Create and manage Unleash feature flags and rollout strategies from your coding assistant.

    mcp.tc/i/unleash

  • MCP for Unity

    Coplay (CoplayDev)

    state.local.label (state.local.title)

    Control the Unity Editor from your assistant: scenes, GameObjects, C# scripts, assets, tests and builds.

    mcp.tc/i/unity

  • Godot MCP

    Coding-Solo

    state.local.label (state.local.title)

    Launch the Godot editor, run projects, read debug output and create or edit scenes from your AI assistant.

    mcp.tc/i/godot

  • Claude Context

    Zilliz

    state.local.label (state.local.title)

    Index a whole codebase into a vector database and search it semantically from your coding assistant.

    mcp.tc/i/claude-context

listing.disclaimer_checked