MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
SmartBear MCP is an MCP integration. MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
The registry lists a streamable-http connection at https://bugsnag.mcp.smartbear.com/mcp.
The registry lists a streamable-http connection at https://zephyr.mcp.smartbear.com/mcp.
The published npm package is @smartbear/mcp, version 0.42.0. Its declared MCP transport is stdio.
The package declares BEARQ_API_TOKEN: BearQ workspace API token. Leave empty to disable BearQ tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/bearq-integration; BEARQ_API_BASE_URL: Override the BearQ public API base URL (optional). Defaults to https://api.bearq.smartbear.com; BUGSNAG_AUTH_TOKEN: BugSnag auth token. Leave empty to disable BugSnag tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/bugsnag-integration; BUGSNAG_PROJECT_API_KEY: BugSnag project API key (optional; narrows interactions to a single project). Learn more: https://developer.smartbear.com/smartbear-mcp/docs/bugsnag-integration; REFLECT_API_TOKEN: Reflect API token. Leave empty to disable Reflect tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/reflect-integration; SWAGGER_API_KEY: Swagger API key. Leave empty to disable Swagger tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/swagger-portal-integration; SWAGGER_FUNCTIONAL_TESTING_API_TOKEN: Swagger Functional Testing API token. Leave empty to disable Functional Testing tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/functional-testing-integration; SWAGGER_FUNCTIONAL_TESTING_BASE_PATH: Override the Swagger Functional Testing API base URL (optional). Defaults to https://api.reflect.run/v1; PACT_BROKER_BASE_URL: PactFlow/Pact Broker base URL. Leave empty to disable Pact tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/contract-testing-with-pactflow; PACT_BROKER_TOKEN: PactFlow authentication token. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/contract-testing-with-pactflow; PACT_BROKER_USERNAME: Pact Broker username (alternative to token). Learn more: https://developer.smartbear.com/smartbear-mcp/docs/contract-testing-with-pactflow; PACT_BROKER_PASSWORD: Pact Broker password (alternative to token). Learn more: https://developer.smartbear.com/smartbear-mcp/docs/contract-testing-with-pactflow; ZEPHYR_API_TOKEN: The Zephyr Cloud API token for authentication. Learn more: https://support.smartbear.com/zephyr/docs/en/rest-api/api-access-tokens-management.html; ZEPHYR_BASE_URL: The Zephyr Cloud API base url. Should be changed depending on the region of your Jira instance. Learn more: https://support.smartbear.com/zephyr-scale-cloud/api-docs/section/Authentication/Accessing-the-API; QTM4J_API_KEY: QTM4J (QMetry Test Management for Jira) API key. Leave empty to disable QTM4J tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/qtm4j-integration; QTM4J_BASE_URL: QTM4J base URL (optional). Defaults to https://qtmcloud.qmetry.com. Override when using a self-hosted or region-specific instance.; QTM4J_AUTOMATION_API_KEY: QTM4J Automation API key used exclusively by the automation import tools. Leave empty to disable automation tools. Learn more: https://developer.smartbear.com/smartbear-mcp/docs/qtm4j-integration.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.42.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| Swagger | Portal - Portal and product management capabilities |
{
"mcpServers": {
"smartbear": {
"command": "npx",
"args": [
"-y",
"@smartbear/mcp@latest"
],
"env": {
"BEARQ_API_TOKEN": "YOUR_BEARQ_API_TOKEN",
"BUGSNAG_AUTH_TOKEN": "YOUR_BUGSNAG_AUTH_TOKEN",
"BUGSNAG_PROJECT_API_KEY": "YOUR_BUGSNAG_PROJECT_API_KEY",
"REFLECT_API_TOKEN": "YOUR_REFLECT_API_TOKEN",
"SWAGGER_API_KEY": "YOUR_SWAGGER_API_KEY",
"SWAGGER_PORTAL_BASE_PATH": "https://api.portal.swaggerhub.com/v1",
"SWAGGER_REGISTRY_BASE_PATH": "https://api.swaggerhub.com",
"SWAGGER_UI_BASE_PATH": "https://app.swaggerhub.com",
"PACT_BROKER_BASE_URL": "your_pactflow_or_pactbroker_base_url",
"PACT_BROKER_TOKEN": "YOUR_PACT_BROKER_TOKEN",
"PACT_BROKER_USERNAME": "your_pact_broker_username",
"PACT_BROKER_PASSWORD": "YOUR_PACT_BROKER_PASSWORD",
"QMETRY_API_KEY": "YOUR_QMETRY_API_KEY",
"QMETRY_BASE_URL": "https://testmanagement.qmetry.com",
"ZEPHYR_API_TOKEN": "YOUR_ZEPHYR_API_TOKEN",
"ZEPHYR_BASE_URL": "https://api.zephyrscale.smartbear.com/v2",
"COLLABORATOR_BASE_URL": "your collab base url",
"COLLABORATOR_USERNAME": "your collab user name",
"COLLABORATOR_LOGIN_TICKET": "your collab login ticket",
"QTM4J_API_KEY": "YOUR_QTM4J_API_KEY",
"QTM4J_BASE_URL": "https://qtmcloud.qmetry.com",
"QTM4J_AUTOMATION_API_KEY": "YOUR_QTM4J_AUTOMATION_API_KEY",
"SWAGGER_FUNCTIONAL_TESTING_API_TOKEN": "YOUR_SWAGGER_FUNCTIONAL_TESTING_API_TOKEN",
"SWAGGER_FUNCTIONAL_TESTING_BASE_PATH": "https://api.reflect.run/v1"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| BEARQ_API_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
| BUGSNAG_AUTH_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
| BUGSNAG_PROJECT_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
| REFLECT_API_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
| SWAGGER_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
| SWAGGER_PORTAL_BASE_PATH | Declared in the maintainer’s client configuration. | Check documentation |
| SWAGGER_REGISTRY_BASE_PATH | Declared in the maintainer’s client configuration. | Check documentation |
| SWAGGER_UI_BASE_PATH | Declared in the maintainer’s client configuration. | Check documentation |
| PACT_BROKER_BASE_URL | Declared in the maintainer’s client configuration. | Check documentation |
| PACT_BROKER_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
| PACT_BROKER_USERNAME | Declared in the maintainer’s client configuration. | Check documentation |
| PACT_BROKER_PASSWORD | Declared in the maintainer’s client configuration. | Check documentation |
| QMETRY_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
| QMETRY_BASE_URL | Declared in the maintainer’s client configuration. | Check documentation |
| ZEPHYR_API_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
| ZEPHYR_BASE_URL | Declared in the maintainer’s client configuration. | Check documentation |
| COLLABORATOR_BASE_URL | Declared in the maintainer’s client configuration. | Check documentation |
| COLLABORATOR_USERNAME | Declared in the maintainer’s client configuration. | Check documentation |
| COLLABORATOR_LOGIN_TICKET | Declared in the maintainer’s client configuration. | Check documentation |
| QTM4J_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
| QTM4J_BASE_URL | Declared in the maintainer’s client configuration. | Check documentation |
| QTM4J_AUTOMATION_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
| SWAGGER_FUNCTIONAL_TESTING_API_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
| SWAGGER_FUNCTIONAL_TESTING_BASE_PATH | Declared in the maintainer’s client configuration. | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.