Does BugSnag have an MCP server?

Yes Official

BugSnag maintains an official MCP server.

Verified 2026-09-29 against vendor docs
Access
Remote server
Endpoint
https://bugsnag.mcp.smartbear.com/mcp
Maintainer
SmartBear Software
License
MIT
Language
TypeScript
Stars
44
Last commit
today
Category
Monitoring
What it does
SmartBear's official MCP Server
— how SmartBear/smartbear-mcp describes itself

Project site: developer.smartbear.com

The receipts
Vendor-hosted https://bugsnag.mcp.smartbear.com/mcp

A remote server run by BugSnag itself — nothing to install. Documented at developer.smartbear.com.

Official package @smartbear/mcp

Published on npm. The package page carries the exact launch arguments and required credentials.

Official repository SmartBear/smartbear-mcp

SmartBear's official MCP Server

★ 44 pushed 2026-09-29 MIT Active
Connect it

Hosted by the vendor — no install, connect over HTTP with OAuth or a token.

Add it from the terminal, then restart your session:

terminal
claude mcp add --transport http bugsnag https://bugsnag.mcp.smartbear.com/mcp

Add --scope user to make it available in every project.

Setup sponsor · open Put your product right here, under the setup steps of all 645 verdict pages. One sponsor at a time. $149 first month, then $399/mo →
Questions
Does BugSnag have an official MCP server?

Yes. BugSnag maintains an official MCP server, hosted at https://bugsnag.mcp.smartbear.com/mcp, distributed as @smartbear/mcp on npm. The source lives at SmartBear/smartbear-mcp on GitHub.

How do I connect BugSnag to Claude?

Add https://bugsnag.mcp.smartbear.com/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http bugsnag https://bugsnag.mcp.smartbear.com/mcp" in Claude Code.

Do I need to install anything to use the BugSnag MCP server?

No. It is a remote server hosted by BugSnag, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.

How is this verdict verified?

BugSnag's owner SmartBear lists bugsnag.mcp.smartbear.com/mcp in its MCP Registry entry com.smartbear/smartbear-mcp and documents it at developer.smartbear.com; the endpoint answers MCP initialize with 401 (OAuth), and BugSnag tools are also in the open-source @smartbear/mcp package. GitHub metadata is refreshed every six hours.

How we know

BugSnag's owner SmartBear lists bugsnag.mcp.smartbear.com/mcp in its MCP Registry entry com.smartbear/smartbear-mcp and documents it at developer.smartbear.com; the endpoint answers MCP initialize with 401 (OAuth), and BugSnag tools are also in the open-source @smartbear/mcp package.

  • github data refreshed 2026-09-29, then every 6 hours
  • vendor docs verified on 2026-09-29

Spotted something out of date? Tell us — corrections ship same-day.

Also in Monitoring

See all Monitoring servers →