# SmartBear MCP Connects SmartBear QA and API tools to your assistant over MCP. It lets you query BugSnag crashes, check Swagger specs, and inspect test runs in chat. - MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 44 - Author: SmartBear - License: MIT · policy=link-only · description only; the file stays with the author - Source: https://github.com/SmartBear/smartbear-mcp - Updated: 2026-10-23 - HTML: https://affpapa.org/en/nevibecode/mcp/smartbear-mcp ## What it does This server connects your AI assistant directly to SmartBear services. You can inspect BugSnag errors, check contract test status in PactFlow, review Swagger definitions, or pull test management records from Zephyr and QTM4J. Setup depends on which services you need. SmartBear hosts remote servers for BugSnag, Swagger, and Zephyr with browser-based OAuth logins. If you need BearQ, Reflect, Collaborator, or QMetry, you must run the local `@smartbear/mcp` package via `npx`. The local setup strictly requires Node.js 22 or higher. ## Requirements - Needs: Node.js (commands run via npx) - Remote server: `https://bugsnag.mcp.smartbear.com/mcp` - Environment variables: `BEARQ_API_TOKEN`, `BEARQ_API_BASE_URL`, `BUGSNAG_AUTH_TOKEN`, `BUGSNAG_PROJECT_API_KEY`, `REFLECT_API_TOKEN`, `SWAGGER_API_KEY`, `SWAGGER_FUNCTIONAL_TESTING_API_TOKEN`, `SWAGGER_FUNCTIONAL_TESTING_BASE_PATH`, `PACT_BROKER_BASE_URL`, `PACT_BROKER_TOKEN` — keys and tokens: ask the human for the values, never commit them or put them in shared files. ## Install ### Claude Code (native platform) 1. **Platform CLI: remote server** ```bash claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcp ``` 2. **Platform CLI** ```bash claude mcp add --env BEARQ_API_TOKEN= --env BEARQ_API_BASE_URL= --env BUGSNAG_AUTH_TOKEN= --env BUGSNAG_PROJECT_API_KEY= --env REFLECT_API_TOKEN= --transport stdio smartbear-mcp -- npx -y @smartbear/mcp ``` Replace <…> with your own values. 12 more environment variables are in the server README ### Codex 1. **Platform CLI: remote server** ```bash codex mcp add smartbear-mcp --url https://bugsnag.mcp.smartbear.com/mcp ``` 2. **Platform CLI** ```bash codex mcp add smartbear-mcp --env BEARQ_API_TOKEN= --env BEARQ_API_BASE_URL= --env BUGSNAG_AUTH_TOKEN= --env BUGSNAG_PROJECT_API_KEY= --env REFLECT_API_TOKEN= -- npx -y @smartbear/mcp ``` Replace <…> with your own values. 12 more environment variables are in the server README ### Cursor **Config file** File `.cursor/mcp.json`: ```json { "mcpServers": { "smartbear-mcp": { "url": "https://bugsnag.mcp.smartbear.com/mcp" } } } ``` File `.cursor/mcp.json`: ```json { "mcpServers": { "smartbear-mcp": { "command": "npx", "args": [ "-y", "@smartbear/mcp" ], "env": { "BEARQ_API_TOKEN": "", "BEARQ_API_BASE_URL": "", "BUGSNAG_AUTH_TOKEN": "", "BUGSNAG_PROJECT_API_KEY": "", "REFLECT_API_TOKEN": "" } } } } ``` Replace <…> with your own values. 12 more environment variables are in the server README ### GitHub Copilot **Config file** File `.vscode/mcp.json`: ```json { "servers": { "smartbear-mcp": { "type": "http", "url": "https://bugsnag.mcp.smartbear.com/mcp" } } } ``` File `.vscode/mcp.json`: ```json { "servers": { "smartbear-mcp": { "type": "stdio", "command": "npx", "args": [ "-y", "@smartbear/mcp" ], "env": { "BEARQ_API_TOKEN": "", "BEARQ_API_BASE_URL": "", "BUGSNAG_AUTH_TOKEN": "", "BUGSNAG_PROJECT_API_KEY": "", "REFLECT_API_TOKEN": "" } } } } ``` Replace <…> with your own values. 12 more environment variables are in the server README ### Gemini CLI 1. **Platform CLI: remote server** ```bash gemini mcp add -t http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcp ``` 2. **Platform CLI** ```bash gemini mcp add -e BEARQ_API_TOKEN= -e BEARQ_API_BASE_URL= -e BUGSNAG_AUTH_TOKEN= -e BUGSNAG_PROJECT_API_KEY= -e REFLECT_API_TOKEN= smartbear-mcp npx -y @smartbear/mcp ``` Replace <…> with your own values. 12 more environment variables are in the server README ## When to use it - inspect runtime crashes in BugSnag directly from your coding assistant - validate and generate API definitions in Swagger Studio - track test execution progress in Zephyr and QTM4J - verify service contract statuses using PactFlow ## Example prompts - Check the latest unhandled crashes reported in BugSnag - Review this API specification against Swagger Studio rules - List failed test runs in Zephyr from the recent build ## Similar - [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74559 - [Keploy](https://affpapa.org/en/nevibecode/mcp/keploy.md) — MCP server · ★ 18727 - [SeleniumBase MCP](https://affpapa.org/en/nevibecode/mcp/seleniumbase-mcp.md) — MCP server · ★ 13169 - [mobile-mcp](https://affpapa.org/en/nevibecode/mcp/mobile-mcp.md) — MCP server · ★ 9946 - [e2e](https://affpapa.org/en/nevibecode/mcp/e2e.md) — MCP server · ★ 11912 - [mockserver](https://affpapa.org/en/nevibecode/mcp/mockserver.md) — MCP server · ★ 4996 --- NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md