# Honeybadger MCP connector

The Honeybadger connector brings your projects, faults, error notices, affected users, comments and dashboards into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about live errors inside their own Honeybadger access.

Source: https://elaichi.ai/connectors/honeybadger/

## Facts

| | |
| --- | --- |
| Application | Honeybadger |
| Category | Observability |
| AI tools | 39 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Honeybadger builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | www.honeybadger.io/contact |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Honeybadger is connected

- Which faults in the production project spiked in the last 24 hours?
- Has anyone at Acme been hit by an unresolved fault this week?
- Add a comment to fault 4821 saying the fix ships Friday.

## Connect Honeybadger in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Honeybadger.
2. Optionally set Share with, then press Connect.
3. Approve it in Honeybadger. Honeybadger's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Honeybadger tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Honeybadger MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Honeybadger MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Honeybadger MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Honeybadger to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Honeybadger tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Honeybadger through Elaichi

### Catch up on overnight errors before standup

Engineering. Ask which Honeybadger faults appeared or spiked in the production project since yesterday, and get the counts, the latest notices and the affected users without opening every fault page.

### Check whether a customer hit a known fault

Support. When a ticket comes in, ask whether that user appears among the affected users on any open Honeybadger fault, and get the fault's status and the last comment on it.

### Triage a noisy fault during an incident

On-call. Pull the notices and occurrence counts for a fault, mark it resolved or assigned in Honeybadger, and leave a comment that says what was done and when.

### See which release broke things

Product. Query Honeybadger insights for error trends across projects after a deploy, and compare this week's occurrence counts against the week before.

### Write the weekly error report without the spreadsheet

Engineering management. Ask for each project's fault counts and its top unresolved faults, and get a report draft ready for the team meeting.

### Confirm a fix actually stopped the errors

QA. After a fix ships, ask whether the fault has received new notices in Honeybadger, then update the fault or add a comment once it stays quiet.

## Elaichi vs Zapier MCP vs Composio for Honeybadger

All three can connect Honeybadger to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Honeybadger tools | Allow or restrict single Honeybadger tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Honeybadger call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Honeybadger to Claude?

Connect Honeybadger in Elaichi first: pick it from the catalog and sign in to your Honeybadger account over OAuth, with no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Honeybadger projects and faults are available in the chat.

### Does Honeybadger work with ChatGPT and Cursor as well as Claude?

Yes. Honeybadger is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. There is nothing to set up again per client.

### What can an AI agent actually do with my Honeybadger data?

It can list your Honeybadger projects and their faults, read the notices and affected users behind a fault, pull occurrence counts and project reports, query insights, and read your dashboards and streams. It can also create or update a project, change a fault's status, and add or edit comments on a fault. Short concrete asks, such as naming the project and the time window, get better answers than long sentences.

### Does connecting Honeybadger give the AI access to every project?

No. Everything an agent does in Honeybadger runs inside the access of the person who signed in, so it sees the projects and faults that person can see and nothing more. Elaichi can narrow that access further for a team or a role, and it can never widen it beyond what Honeybadger itself allows.

### Can my team share one Honeybadger connection?

Yes. One person connects Honeybadger in Elaichi and shares it with a team, and nobody else has to handle a token or credential. Each teammate still signs in as themselves, so the audit log names the person who resolved a fault or added a comment, not the person who connected the account.

### Can I stop an agent from deleting or changing things in Honeybadger?

Yes. Restrictions in Elaichi work per action, so you can allow reading Honeybadger faults and notices while blocking deleting a project, changing a fault or removing a comment. A restricted action is never advertised to the AI client at all, so no prompt can reach it.

### What happens to a Honeybadger connection when someone leaves?

Offboarding a person in Elaichi ends their access to Honeybadger through every client at once. A connection they shared keeps working for everyone else on the team. If you want to remove Honeybadger entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the Honeybadger MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Honeybadger is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Honeybadger?

Yes. Both let Claude, ChatGPT or Cursor use Honeybadger. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Honeybadger call.

### How is Elaichi different from Composio for Honeybadger?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Honeybadger: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 39 Honeybadger tools

Every tool below is callable through https://api.elaichi.ai/mcp once Honeybadger is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get reference** (Get). Returns Honeybadger reference documentation by topic.
- **List projects** (List). List all Honeybadger projects (returns summary info; use get_project for full details)
- **Get project** (Get). Get a single Honeybadger project by ID
- **Create project** (Create). Create a new Honeybadger project
- **Update project** (Update). Update an existing Honeybadger project
- **Delete project** (Delete). Delete a Honeybadger project and all of its data.
- **Get project occurrence counts** (Get). Get occurrence counts for all projects or a specific project
- **Get project integrations** (Get). Get a list of integrations (channels) for a Honeybadger project
- **Get project report** (Get). Get report data for a Honeybadger project
- **List faults** (List). Get a list of faults for a project with optional filtering and ordering.
- **Get fault** (Get). Get detailed information for a specific fault in a project
- **Update fault** (Update). Update a fault's resolved, ignored, assignee, or resolve-on-deploy state.
- **List fault notices** (List). Get a list of notices (individual error events) for a specific fault
- **List fault affected users** (List). Get a list of users who were affected by a specific fault with occurrence counts
- **Get fault counts** (Get). Get fault count statistics for a project with optional filtering.
- **List fault comments** (List). List comments on a fault.
- **Get fault comment** (Get). Get a single comment on a fault by ID.
- **Create fault comment** (Create). Add a comment to a fault.
- **Update fault comment** (Update). Replace the body of an existing fault comment.
- **Delete fault comment** (Delete). Delete an existing comment from a fault.
- **Query insights** (Search). Execute a BadgerQL query against Insights data.
- **List streams** (List). List Insights data streams for a Honeybadger project.
- **List dashboards** (List). List all Insights dashboards for a Honeybadger project
- **Get dashboard** (Get). Get a single Insights dashboard by ID
- **Create dashboard** (Create). Create a new Insights dashboard for a Honeybadger project.
- **Update dashboard** (Update). Update an existing Insights dashboard.
- **Delete dashboard** (Delete). Delete an Insights dashboard.
- **List alarms** (List). List all Insights alarms for a Honeybadger project.
- **Get alarm** (Get). Get a single Insights alarm by ID.
- **Create alarm** (Create). Create a new Insights alarm for a Honeybadger project.
- **Update alarm** (Update). Update an existing Insights alarm.
- **Delete alarm** (Delete). Delete an Insights alarm.
- **Get alarm history** (Get). Get the trigger history for an Insights alarm.
- **List check ins** (List). List check-ins (cron/scheduled task monitoring) for a Honeybadger project.
- **Get check in** (Get). Get a single check-in by ID.
- **Create check in** (Create). Create a new check-in for a Honeybadger project.
- **Update check in** (Update). Update an existing check-in.
- **Delete check in** (Delete). Delete a check-in.
- **Search tools** (Search). Search available Honeybadger tools by name or description.