August 2026 product update: hosted MCP, anomaly detection, and more

Your MCP client doesn’t need your whole API key just to look up an error anymore.

Honeybadger's hosted MCP server now supports OAuth. You can approve it through your browser, scope your permissions, revoke your permissions, and rest easy knowing that our tokens auto-refresh and don’t sit around in a config.

Keep reading to see how it works and get a quick recap of everything else that shipped this cycle.

MCP gets OAuth, and self-hosting gets more flexible

Until now, connecting an AI agent to Honeybadger's MCP server meant handing it a personal API token, giving it full account access and no way to reduce its scope. If you wanted to give Claude or Cursor read-only access to investigate errors, you were stuck granting it everything.

The new hosted server fixes that. Add https://mcp.honeybadger.io/mcp to your client and approve the connection in your browser — no local install or token to manage.

The first time a client connects, you pick an account and choose read-only or read-write access. Behind the scenes, Honeybadger issues short-lived tokens that refresh automatically, so there's no long-lived secret sitting in a config file. You can review or revoke any connected app anytime from User Settings → API Access (or, for admins, from any team member's account under Account Settings → API Access).

Getting started:

Claude Code:

claude mcp add --transport http honeybadger "https://mcp.honeybadger.io/mcp"

Cursor, Windsurf, and Claude Desktop use a JSON config:

json

{
  "mcpServers": {
    "honeybadger": {
      "url": "https://mcp.honeybadger.io/mcp"
    }
  }
}

VS Code has its own CLI equivalent:

code --add-mcp '{"name":"honeybadger","type":"http","url":"https://mcp.honeybadger.io/mcp"}'

EU accounts should use https://eu-mcp.honeybadger.io/mcp instead. Each endpoint only accepts accounts from its own region.

EU support is also here

If you want to use the self-hosted MCP with the EU stack, you can set HONEYBADGER_API_URL to https://eu-app.honeybadger.io in the env block (and add a matching -e HONEYBADGER_API_URL entry to args for Docker, so the variable actually gets passed through), then authenticate with a personal auth token from your EU user settings. Keep in mind that a US token won't work against the EU region, and vice versa.

What to do with your MCP

Once connected, your agent can list and manage projects, search and filter errors, look at stack traces and affected users, run BadgerQL queries against Insights, and manage dashboards and alarms. The server also handles your agent reference material from BadgerQL and error search syntax automatically, so you don't need to paste documentation into your prompts.

Full setup instructions, including client-specific configuration and building from source, are in the MCP documentation.

Also shipped this month

Natural language search. Error search and BadgerQL can answer almost any question about your errors and events, but only if you remember the syntax. Now you can describe what you want instead. Just click the lightbulb next to the search box, type something like "unresolved production errors from the last 24 hours that have comments," and Honeybadger writes the query for you, editable and ready to run.

Anomaly detection. Some of the worst incidents don't show up as one new error; they show up as a flood. Honeybadger now learns each project's normal error volume and alerts you when it spikes above that baseline — no thresholds to configure. Available on Business and Enterprise plans.

Oban-py support. Honeybadger now integrates with the Python port of Oban’s background job library. Unhandled worker exceptions are reported automatically, per-job telemetry flows into Insights, and request context carries through to the jobs it enqueues.

---

That's everything from July. As always, the full history is on the changelog. If you're interested in trying out any of these features, a Honeybadger account starts out as free for a single user.