# Honeybadger (EU) MCP connector

The Honeybadger (EU) connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent read and update faults, notices, comments, and projects in your EU Honeybadger account, with every call running as the signed-in person and landing in an audit log.

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

## Facts

| | |
| --- | --- |
| Application | Honeybadger (EU) |
| Category | Observability |
| AI tools | 39 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Honeybadger (EU) 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 (EU) is connected

- Which faults in the checkout project started since yesterday?
- How many users did fault 4821 affect this week?
- Add a comment to the login timeout fault saying a fix shipped.

## Connect Honeybadger (EU) in Elaichi

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

1. Open Connections, choose Add connection, and pick Honeybadger (EU).
2. Optionally set Share with, then press Connect.
3. Approve it in Honeybadger (EU). Honeybadger (EU)'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 (EU) tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Honeybadger (EU) 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 (EU) 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 (EU) 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 (EU) 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 (EU) 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 (EU) through Elaichi

### Triage this morning's new faults

Engineering. Ask for the faults that started overnight in a project, how many times each fired and how many users it hit, then resolve or assign the ones that matter.

### Understand a fault before opening the dashboard

On-call. Pull the latest notices for a fault, see which environment and which users were affected, and leave a comment with what you found for the next person.

### Check whether a customer hit a known error

Support. Ask which faults affected a given user recently and what the error said, so your reply to the ticket is accurate the first time.

### Measure whether a release made things worse

Product. Compare occurrence counts for a project before and after a deploy, and query Insights for the events behind the change.

### Get the weekly error report without a dashboard

Engineering leadership. Ask for a project report and the fault counts by status, summarized and ready for the Monday meeting.

### Set up a project for a new service

Platform. Create the Honeybadger project for a new service, adjust its settings as it evolves, and check which streams and dashboards are in place.

## Elaichi vs Zapier MCP vs Composio for Honeybadger (EU)

All three can connect Honeybadger (EU) 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 (EU) tools | Allow or restrict single Honeybadger (EU) 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 (EU) 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 (EU) to Claude?

Connect Honeybadger (EU) in Elaichi first: pick the EU connector, sign in to Honeybadger over OAuth as yourself, and approve the access it asks for. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. From that point Claude can work with the faults and projects in your EU Honeybadger account.

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

Yes. The same Elaichi endpoint, https://api.elaichi.ai/mcp, serves Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent, so Honeybadger in EU is connected once and available everywhere. Each person still signs in to Honeybadger as themselves from whichever client they use.

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

It can list your EU Honeybadger projects, pull the faults in each one with their occurrence counts, affected users and recent notices, and resolve or update a fault. It can read and add comments on a fault, run queries against Insights, list streams, and read dashboards and project reports. Short, concrete asks such as "faults in the checkout project since yesterday" work better than long paragraphs.

### Does connecting Honeybadger (EU) give the AI every project in my account?

No. Every call to Honeybadger in EU runs under the account of the person who signed in, so the agent sees only the projects and faults that person can already see in Honeybadger. Elaichi can narrow that further with per-action restrictions, and it can never widen it beyond what Honeybadger itself allows.

### Can my team share one Honeybadger (EU) connection?

Yes. One person connects Honeybadger (EU) and shares the connection with a team in Elaichi, and nobody else handles a token or credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every fault they resolved or commented on in EU Honeybadger.

### Can I stop an agent from deleting projects or changing faults in Honeybadger (EU)?

Yes. Restrictions in Elaichi apply per action, so you can allow reading faults and notices in Honeybadger (EU) while blocking project deletion, fault updates or comment deletion. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.

### What happens to a Honeybadger (EU) connection when someone leaves?

Offboarding that person in Elaichi ends their access to Honeybadger (EU) at once, from every client they had set up. A connection they shared with the team keeps working for everyone else. If you want it gone entirely, disconnecting Honeybadger (EU) once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

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

Yes. Honeybadger (EU) 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 (EU)?

Yes. Both let Claude, ChatGPT or Cursor use Honeybadger (EU). 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 (EU) call.

### How is Elaichi different from Composio for Honeybadger (EU)?

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 (EU): 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 (EU) tools

Every tool below is callable through https://api.elaichi.ai/mcp once Honeybadger (EU) 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.