Honeycomb MCP connector
The Honeycomb connector lets Claude, ChatGPT, Cursor, or the Elaichi Agent run queries, read traces, and manage boards and triggers in Honeycomb, with each person signed in as themselves and every call logged.
-
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.
How to connect
How to connect Honeycomb to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Honeycomb once
-
Open Connections, choose Add connection, and pick Honeycomb.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Honeycomb. Honeycomb'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.
Honeycomb 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.
Honeycomb 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.
Honeycomb 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 Honeycomb 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 Honeycomb through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
On-call
Find the slow request behind a page
Ask for the trace behind a latency alert, see which spans took the time, and get a plain summary before you open a laptop.
-
SRE
Explain a spike with BubbleUp
Run BubbleUp on the error rate in a dataset and have the agent tell you which build, region, or customer stands out from the rest.
-
Engineering
Check a service before a deploy
Pull the service map and the anomaly profiles for the service you are about to ship, and see what depends on it.
-
Platform
Keep triggers and boards tidy
Create a trigger for a new dataset or update the queries on a board without clicking through the Honeycomb UI.
-
Support
Confirm a customer's reported error
Ask for recent spans from that customer's requests and get a plain answer you can paste into the ticket.
-
Product
Report on SLOs for the weekly review
List the SLOs and the queries behind them, then turn them into a short status the whole team can read.
Try asking
- “Which spans made checkout slow in the last hour?”
- “Run BubbleUp on errors in the api-gateway dataset today”
- “Which SLOs are burning budget fastest this week?”
Compare
Elaichi vs Zapier MCP vs Composio for Honeycomb
All three can connect Honeycomb 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 Honeycomb tools | Allow or restrict single Honeycomb 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 Honeycomb 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
Honeycomb tools for your AI agents
34 tools are ready to call through Elaichi's MCP endpoint the moment you connect Honeycomb, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Honeycomb builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Honeycomb gets you
6 screens from the product, each doing one job for your Honeycomb account.
The agent
Ask Honeycomb questions in plain language.
Live datasets, traces, and SLOs answer back without writing a query.
- datasets
- traces
- boards
- triggers
Ask Elaichi to work across your apps.
Which spans made checkout slow in the last hour?
Run BubbleUp on errors in the api-gateway dataset today
Which SLOs are burning budget fastest this week?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Honeycomb to every client.
Claude, ChatGPT, and Cursor sign in over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
34 Honeycomb tools, ready with no code.
Queries, traces, spans, boards, triggers, and SLOs covered with no custom code.
- Get workspace context
- Get environment
- Get dataset
- Get dataset columns
Toolboxes
Every team gets its own Honeycomb toolbox.
On-call reads traces, platform manages triggers, product sees SLOs, each scoped by team.
- On-call
- SRE
- Platform
- Engineering
Shared connections
Share a Honeycomb connection, never the credential.
One person connects, teams work through it, nobody else handles a key.
- Production
- Staging
- On-call
- Platform
Audit log
Every Honeycomb call is written down.
When, who, what happened, and which dataset, in an append-only log.
- When
- Who
- What happened
- Type
Launching 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 starts the SLO digest itself.
Honeycomb SLOs are fetched, grouped, drafted, approved by a person, then posted back.
Honeycomb digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch datasets
Honeycomb
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
Honeycomb
Queued
Collections and dashboards
Honeycomb health numbers, computed without a model.
Four metrics, 14 days of triggers created, and a breakdown by team, refreshed on schedule.
Honeycomb health
Refreshed 4 minutes ago · every 15 minutes · from the datasets collection
Datasets
1,284 ↓ 12%
Traces
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Datasets created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
On-call 21%
Platform 18%
FAQ
Frequently asked questions
How do I connect Honeycomb to Claude?
Connect Honeycomb in Elaichi first: you sign in to Honeycomb over OAuth and approve access, with no OAuth application to register and 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 to Elaichi and Honeycomb is available from that point.
Does Honeycomb work with ChatGPT and Cursor as well as Claude?
Yes. Honeycomb is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. There is nothing extra to set up per client.
What can an AI agent actually do with my Honeycomb data?
It can run queries against your Honeycomb datasets, read the results, pull a trace and walk its spans, run BubbleUp to explain an outlier, and look at the service map and anomaly profiles for a service. It can also list boards, triggers, and SLOs, and create or update boards and triggers. Short, specific asks such as which spans were slow in checkout this hour work better than long paragraphs.
Does connecting Honeycomb give the AI access to every environment and dataset?
No. Access follows the person who signed in to Honeycomb, so the agent sees the environments and datasets that person can already see and nothing more. Elaichi can narrow that further for a team or a toolbox, but it can never widen it beyond what Honeycomb itself allows.
Can I stop an agent from creating or changing triggers and boards in Honeycomb?
Yes. Restrictions in Elaichi apply per action, so you can allow running queries and reading traces in Honeycomb while blocking the creation or updating of triggers and boards. A restricted action is never advertised to the AI client, so no prompt can reach it.
What happens to a Honeycomb connection when someone leaves?
Offboarding that person in Elaichi ends their Honeycomb access at once, across every client they used. A shared Honeycomb connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Honeycomb once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the Honeycomb MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Honeycomb 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 Honeycomb?
Yes. Both let Claude, ChatGPT or Cursor use Honeycomb. 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 Honeycomb call.
How is Elaichi different from Composio for Honeycomb?
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 Honeycomb: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Honeycomb 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.