What an agent can do in Honeycomb
Investigate production with Honeycomb: run queries, fetch traces, explore dataset columns, and create boards, triggers and SLOs. US region; add the EU server as a custom server.
Jobs on Rush that use Honeycomb
- Was It Slow on Our Side? A SaaS Support Team Checks Each Slowness Ticket Against Honeycomb
- How Did Our API Perform for This Customer Last Quarter? A Customer-Success Team's Honeycomb Report
How Honeycomb connects
Honeycomb is a remote MCP server, published by Honeycomb, at https://mcp.honeycomb.io/mcp. Connecting it signs in through the MCP OAuth flow on Honeycomb's side.
From Honeycomb: Honeycomb's MCP documentation.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names honeycomb in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Honeycomb",
"url": "https://mcp.honeycomb.io/mcp"
}Whose Honeycomb account the agent uses
Your Honeycomb connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Honeycomb, and a run started with an API key uses the Honeycomb of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Honeycomb, and that agent's runs use their account and nothing else: never yours, never another user's.
More Observability integrations
Frequently asked questions
How do I connect Honeycomb to Rush?
Open Settings → Connections in the console and connect Honeycomb, or send POST /me/connections with {"type":"mcp","name":"Honeycomb","url":"https://mcp.honeycomb.io/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Honeycomb account?
No. A run gets your Honeycomb connection only when it names it in connections ("connections": ["honeycomb"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Honeycomb?
Investigate production with Honeycomb: run queries, fetch traces, explore dataset columns, and create boards, triggers and SLOs. US region; add the EU server as a custom server. 2 published jobs use it; this page lists them.
Can my app's users connect their own Honeycomb?
Yes. Make each user an agent from your template, and they sign in to their own Honeycomb through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for engineering teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to