SmartBear MCP: BugSnag, Swagger, Zephyr and testing in the agent
smartbear-mcp
The SmartBear server gives the agent BugSnag, Swagger, Zephyr, QMetry and PactFlow: errors, API specs, test cases and contracts
- 44 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent receives product tokens and access to error data, test cases and API specs, and BugSnag errors often contain user data
- Swagger Studio and test product tools can create and change specs and test cases in a production account
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/smartbear-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent receives product tokens and access to error data, test cases and API specs, and BugSnag errors often contain user data
- Swagger Studio and test product tools can create and change specs and test cases in a production account
This is third-party code. Review the repository files before installing.
What it does
One MCP server bundles the SmartBear testing and monitoring products. Through BugSnag the agent reads errors and investigates failures, through Swagger it works with portals, API studio and functional tests, and through PactFlow with contract tests. Reflect, BearQ, QMetry, QTM4J, Zephyr and Collaborator cover test cases, runs and reviews. For BugSnag, Swagger and Zephyr SmartBear hosts remote servers with OAuth sign-in, so no installation or tokens are needed. The other products are available only in the local @smartbear/mcp npm package, started through npx and fed product tokens in environment variables. An empty variable turns off that product's tools.
Who it is for. QA engineers, API developers and teams already on SmartBear products who want to query that data through an agent
Good fit when
- You need to triage fresh BugSnag errors and find which release introduced them
- You want to create an API specification in Swagger Studio from a text description
- You need to find Zephyr or QMetry test cases for a given ticket and run them
- You need to check PactFlow contracts before deploying a service
- SmartBear products run on your own servers and the agent needs a single entry point
Not a fit when
- You have no SmartBear accounts: without tokens or OAuth sign-in the product tools do not work
- You only need application errors and you use Sentry: the catalog has a separate server for it
- You need to run tests on a local machine: the server calls the product cloud APIs and knows nothing about your runner
- Your Node.js is older than 22: the local package needs Node.js 22 or newer
Example request
Show the 10 most frequent unhandled BugSnag errors of the last week in the web-app project and find which release they started in.MCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
BUGSNAG_AUTH_TOKENsecret- BugSnag auth token; an empty value disables BugSnag tools
SWAGGER_API_KEYsecret- Swagger API key; an empty value disables Swagger tools
ZEPHYR_API_TOKENsecret- Zephyr token for the local setup
Limitations
For BearQ, Reflect, QMetry, QTM4J, PactFlow, Collaborator and functional testing only the local npm package is available; they have no remote servers. The local install needs Node.js 22. Tokens are set separately for each product in the local setup. The tool set depends on the products you have access to, and the SmartBear products themselves are paid. The last commit was made on November 6, 2026.
How to disable. Remove the server from the client config, for example with claude mcp remove smartbear, and revoke the issued tokens in the BugSnag, Swagger and other product settings. For remote servers revoke the OAuth grant in the SmartBear account.
FAQ
Do I need to install anything for BugSnag?
No. BugSnag, Swagger and Zephyr have remote servers at addresses like bugsnag.mcp.smartbear.com, and sign-in goes through OAuth in the browser.
What about BearQ and QMetry?
They connect only through the local @smartbear/mcp package: there are no remote servers for these products.
Can I enable only some products?
Yes. Leave the environment variables of unneeded products empty and their tools are disabled.
What licence does the project use?
MIT, as stated in the repository.
Does it work with on-premise installs?
Yes, the config has base-path variables for on-premise Swagger Portal, Registry and UI deployments.
Discussion
No questions or reviews yet.
Related
MCP serversBrowserStack MCP Server: testing on real devices
BrowserStack MCP Server
The official BrowserStack MCP server: real devices, automated tests and test cases driven by an agent from your editor
MCP server: an agent sends GET, POST, PUT, DELETE and PATCH to your REST API and gets back status, headers and body
kogiQA MCP gives an agent a browser that finds page elements without selectors, for debugging web apps and writing e2e tests
Official Qase MCP server with 42 tools: cases, runs, defects, CI reports and search in the QQL query language
The official MCP server debugger: web UI, automation CLI and terminal UI in one package
An MCP server that spins up several browser agents to test a site for broken links, UI bugs and accessibility issues
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| SmartBear MCP: BugSnag, Swagger, Zephyr and testing in the agent (this card) | yes | OAuth | 44 | |
| Swagger MCP Server | no | key is optional | 115 | a server around Swagger alone, while this one adds BugSnag, Zephyr and the testing products |
| Sentry MCP | no | API key | 961 | error monitoring in Sentry, while in SmartBear it is BugSnag plus testing |
README in short
The README lists the products the server covers, gives the remote server URLs for BugSnag, Swagger and Zephyr and a VS Code config example with environment variables for each product. Every integration links to its own guide with prompts and a tool list.