Smartbear
SmartBear's official MCP Server
{ "mcpServers": { "smartbear-smartbear-mcp": { "url": "https://bugsnag.mcp.smartbear.com/mcp", "headers": {} } }}.cursor/mcp.jsonMCP-Server
- Transport
- http
- Status
- Remote
Agenten stärken
Diesen Server hinzufügen
Die eigene URL des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Server-URL
https://bugsnag.mcp.smartbear.com/mcpZugangsdaten vom Herausgeber
- 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
Die Claude-Schaltfläche oben öffnet Claude mit ausgefülltem Namen und ausgefüllter URL. Sie bestätigen dort noch.
shClaude Code
claude mcp add --transport http smartbear-smartbear-mcp https://bugsnag.mcp.smartbear.com/mcpRun in a terminal.
jsonClaude Desktop
{ "mcpServers": { "smartbear-smartbear-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://bugsnag.mcp.smartbear.com/mcp" ] } }}claude_desktop_config.json
Remote · HTTPInstallation vom HerausgeberSchritt für Schritt: in Claude hinzufügen
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenServer-Details
Remote- Transport
- http
- Lizenz
- MIT
- API-Schlüssel
- 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, PACT_BROKER_USERNAME, PACT_BROKER_PASSWORD, ZEPHYR_API_TOKEN, ZEPHYR_BASE_URL, QTM4J_API_KEY, QTM4J_BASE_URL, QTM4J_AUTOMATION_API_KEY
- Zuletzt geprüft
- 2026-11-13
- Sterne
- 44
- Tools
- —
- Uptime
- —
Tools
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Smartbear?
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Smartbear einen API-Schlüssel?
Der Herausgeber nennt diese Umgebungsvariablen: 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, PACT_BROKER_USERNAME, PACT_BROKER_PASSWORD, ZEPHYR_API_TOKEN, ZEPHYR_BASE_URL, QTM4J_API_KEY, QTM4J_BASE_URL, QTM4J_AUTOMATION_API_KEY.
Welchen Transport verwendet Smartbear?
Smartbear wird über HTTP erreicht.
Wann wurde Smartbear zuletzt geprüft?
Zuletzt geprüft: 2026-11-13. SmartBear's official MCP Server
Vom Herausgeber
Dokumentation
Die README wurde noch nicht gecrawlt. Repository öffnen
SmartBear's official MCP Server