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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
39 tools
How to connect
How to connect Honeybadger to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Honeybadger once
-
Open Connections, choose Add connection, and pick Honeybadger.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Honeybadger. Honeybadger's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Honeybadger MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Honeybadger to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Honeybadger through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Catch up on overnight errors before standup
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.
-
Support
Check whether a customer hit a known fault
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.
-
On-call
Triage a noisy fault during an incident
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.
-
Product
See which release broke things
Query Honeybadger insights for error trends across projects after a deploy, and compare this week's occurrence counts against the week before.
-
Engineering management
Write the weekly error report without the spreadsheet
Ask for each project's fault counts and its top unresolved faults, and get a report draft ready for the team meeting.
-
QA
Confirm a fix actually stopped the errors
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.
Try asking
- “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.”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Honeybadger tools for your AI agents
39 tools are ready to call through Elaichi's MCP endpoint the moment you connect Honeybadger, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Honeybadger builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Honeybadger gets you
6 screens from the product, each doing one job for your Honeybadger account.
The agent
Ask about live faults in plain language.
Get fault counts, affected users and recent notices from Honeybadger without opening a dashboard.
- projects
- faults
- notices
- comments
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches Honeybadger from every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
All 39 Honeybadger tools, no code to write.
Projects, faults, notices, affected users, comments, insights and dashboards, ready the moment you connect.
- Get reference
- List projects
- Get project
- Create project
ElaichiToolsToolboxes
Each team gets its own Honeybadger toolbox.
On-call sees faults and notices, support sees affected users, each scoped to its team.
- Engineering
- On-call
- Support
- Product
ElaichiToolboxesShared connections
Share one Honeybadger connection, never a credential.
One person connects Honeybadger, teammates work through it, and nobody else sees a token.
- Production
- Staging
- Backend
- Web app
ElaichiConnectionsAudit log
Every fault update is recorded with a name.
See who resolved a fault, who commented and who changed a project, with time and resource.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns new faults into a digest.
Faults are fetched and grouped, an agent drafts a digest, a person approves, it posts back.
Honeybadger digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Honeybadger
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Honeybadger
Queued
Collections and dashboards
Honeybadger error health, computed without a model.
Four metrics, 14 days of faults created and a breakdown by team, refreshed on a schedule.
Honeybadger health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Faults
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Backend 21%
Web app 18%
FAQ
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 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.
Put Honeybadger in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.