SmartBear MCP
Connect BugSnag, Reflect, API Hub, and PactFlow to your coding agent so you triage crashes, run tests, and manage APIs without leaving the IDE.
Overview
SmartBear MCP is a MCP server for the Ship phase that lets agents use BugSnag, Reflect, API Hub, and PactFlow from a single npm stdio server.
What is this MCP server?
- Optional BugSnag tools via BUGSNAG_AUTH_TOKEN and BUGSNAG_PROJECT_API_KEY
- Reflect test automation via REFLECT_API_TOKEN
- API Hub access via API_HUB_API_KEY
- PactFlow contract workflows (enable per SmartBear MCP docs)
- npm package @smartbear/mcp v0.9.0 with stdio transport
- Package @smartbear/mcp version 0.9.0
- stdio transport via npm registry
- Four optional product integrations gated by environment variables
What problem does it solve?
Jumping between BugSnag, test runners, and API portals slows solo builders who want one agent session to debug, test, and review APIs.
Who is it for?
Indie SaaS teams already on BugSnag or Reflect who want MCP-driven triage, test hub actions, and API Hub lookups during ship and operate.
Skip if: Greenfield projects with no SmartBear accounts, or builders who only need a single open-source linter with no observability stack.
What do I get? / Deliverables
After installing @smartbear/mcp and setting tokens, your agent can call enabled SmartBear tools for crashes, tests, and API operations from Claude Code or Cursor.
- Agent-callable BugSnag investigation tools when token is set
- Reflect and API Hub tool surfaces for enabled keys
- Unified SmartBear tool plane for ship-and-operate workflows
Recommended MCP Servers
Journey fit
SmartBear spans pre-release testing and production observability; the canonical shelf is Ship because Reflect and contract checks gate release quality. Testing is the primary subphase for Reflect and PactFlow-style verification invoked before and during ship.
How it compares
Vendor observability and test-hub MCP, not a generic code-review skill.
Common Questions / FAQ
Who is SmartBear MCP for?
Solo builders and small teams using SmartBear products who want Claude Code, Cursor, or Codex to interact with BugSnag, Reflect, API Hub, or PactFlow via MCP.
When should I use SmartBear MCP?
Use it during ship and operate when you need agent-assisted crash investigation, Reflect tests, API catalog work, or contract checks alongside your codebase.
How do I add SmartBear MCP to my agent?
Install @smartbear/mcp from npm, run stdio transport in your MCP config, and set BUGSNAG_AUTH_TOKEN, REFLECT_API_TOKEN, API_HUB_API_KEY, and related vars per SmartBear docs—leave unset to disable a product.