Honeybadger MCP server

What the model can do

Honeybadger error monitoring: projects, errors (faults) with counts, search and recent occurrences, error counts by environment and status, deploys, check-ins and uptime checks with outages. Can comment on, resolve, reopen, ignore, assign, pause and delete errors, delete a comment, and create or change check-ins.

Reads

• honeybadger_list_projectsHoneybadger projects (one per app or service): id, environments, error count, when an error was last and first seen, owner and uptime checks.
• honeybadger_list_faultsErrors (Honeybadger calls them faults) in one project: class, message, environment, resolved or ignored, assignee, occurrence and comment counts…
• honeybadger_get_faultOne Honeybadger error in full, with its most recent occurrences (newest first): when, message, environment…
• honeybadger_fault_summaryCounts of a project's Honeybadger errors: the total and the split by environment, resolved and ignored.
• honeybadger_list_deploysDeploys Honeybadger was told about for a project, newest first: when, environment, who deployed, repository and revision.
• honeybadger_list_check_insCheck-ins (scheduled-job monitors) for a project: name, state (reporting, pending, missing…), schedule, when it last reported and is next expected…
• honeybadger_list_uptimeUptime checks (Honeybadger calls them sites) for a project with their state, or, given a site_id…

Acts, when you ask

These change something in Honeybadger. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• honeybadger_add_commentAdds a comment to an error (fault) in Honeybadger, posted as the token's user.
• honeybadger_resolve_faultResolve a Honeybadger error now (`now`), mark it to resolve itself on the project's next deploy (`on_next_deploy`), or reopen it (`reopen`).
• honeybadger_ignore_faultIgnore a Honeybadger error (`ignored: true`), so new occurrences no longer notify anyone, or stop ignoring it (`ignored: false`).
• honeybadger_assign_faultAssign a Honeybadger error to a project member by their numeric user id (an error's current assignee_id shows in honeybadger_list_faults).
• honeybadger_pause_faultPause a Honeybadger error's notifications for an hour, a day or a week (`time`), or for the next 10, 100 or 1000 occurrences (`count`).
• honeybadger_unpause_faultClear the pause on one Honeybadger error, so its occurrences notify the project's channels again.
• honeybadger_delete_faultPermanently delete a Honeybadger error with its comments and history.
• honeybadger_delete_commentPermanently delete one comment on a Honeybadger error.
• honeybadger_create_check_inCreate a Honeybadger check-in (a scheduled-job monitor) in a project: `simple` expects a report every `report_period`, `cron` on a cron schedule.
• honeybadger_update_check_inChange a Honeybadger check-in's name, slug, grace period or schedule (report_period for a simple check-in…

Connect it

First connect Honeybadger on Dashboard → Connections, then add Memtro to your client once. The Honeybadger tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Honeybadger connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What new errors appeared since the last deploy?
• › How many open production errors does the Acme API have?
• › Did the nightly invoice job check in last night?
• › Add a comment to the billing NoMethodError saying Priya is looking at it
• › Resolve the Northwind import error on the next deploy

Questions

Is this an official Honeybadger MCP server?

No. It is Memtro's MCP server with Memtro's Honeybadger connector behind it: the connector reads Honeybadger through its API with the credentials you connect on Dashboard → Connections, and Honeybadger publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Honeybadger?

Only when you ask, and only what it has been granted: add a comment to an error (fault) in a Honeybadger project; resolve an error now or on the next deploy, or reopen it; ignore an error, or stop ignoring it; assign an error to a project member; pause an error's notifications for a time or a number of occurrences; unpause an error's notifications; delete an error (permanent); delete a comment on an error (permanent); create a check-in (the project's alert channels are notified when it goes missing); change a check-in's name, slug or schedule. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server