Integrations · Analytics

Connect Honeycomb to Well

Connect Honeycomb to Well over its MCP server so your agents can reach its traces, services, and error data from the same workspace as the rest of your stack. Honeycomb exposes no structured financial entity for Well to map today, so the connection is observability reach, not a records sync.

Connect HoneycombSee what Well does

What Well pulls from Honeycomb

Honeycomb feeds Honeycomb MCP server into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Honeycomb’s access.

From Honeycomb		In Well	Relation
Honeycomb MCP server		Workspace context	Reachable from

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Honeycomb → Well

What Well does with your Honeycomb connection

Connect

Connect Honeycomb over OAuth (MCP DCR): Well registers a client through Honeycomb's OAuth Dynamic Client Registration and you approve on Honeycomb's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Connecting Honeycomb makes it reachable from your workspace; Honeycomb exposes no structured records for Well to sync into the data model today.

Enrich

With no records to ingest, Honeycomb adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.

Available

Honeycomb is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.

Questions Honeycomb unlocks

Ask in plain language. Well answers from your connected Honeycomb connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Honeycomb connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Honeycomb connection…

Connect Honeycomb in three steps

01
Connect Honeycomb over its MCP server
Open Honeycomb in Well's Connections panel and authorise it through its MCP server at mcp.honeycomb.io over OAuth. Well registers a client via Dynamic Client Registration and walks you through Honeycomb's consent step, with no keys to paste.
- AuthOAuth (MCP DCR)
- MCP servermcp.honeycomb.io/mcp
02
Make it reachable
The connection brings Honeycomb within reach of your workspace and its agents. Honeycomb exposes no structured financial entity for Well to map today, so there is no invoice, transaction, or account sync to configure.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to let an agent reach Honeycomb's traces and service data from the same place it reaches the rest of your stack. If Honeycomb later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records.
- Availabilityreachable as soon as connect completes

The OAuth handshake completes in about a minute. This is a reach-and-availability connection, not a records feed, so nothing backfills.

How Honeycomb stays secure with Well

Honeycomb connects over its MCP server at mcp.honeycomb.io, with OAuth Dynamic Client Registration handling the credential so Well never holds a Honeycomb secret. Because no structured financial entity is mapped today, the token simply makes Honeycomb reachable from your workspace rather than pulling records. The connection is read-only and grants Well nothing it could change in Honeycomb.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.honeycomb.io/mcp

Read Honeycomb records
Resources the Honeycomb MCP server exposes, scoped by your OAuth approval.
granted
Resolve Honeycomb MCP server across your stack
Match identifiers in Honeycomb against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Honeycomb records
Not granted; Honeycomb is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Honeycomb passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Honeycomb’s admin panel.

Frequently asked questions about Honeycomb and Well

Open Honeycomb in Well's Connections panel and authorise it through its MCP server at mcp.honeycomb.io over OAuth. Well registers a client via Dynamic Client Registration and routes you through the consent step on Honeycomb's side, with no keys to paste. The connection brings Honeycomb's observability data within reach of your workspace and agents.

Not today, and the page is upfront about it. Honeycomb holds traces, services, and error data, but it exposes no supported target model for Well to map into an invoice, transaction, or account. So there is no records sync to configure; the connection is reach-only, letting an agent pull the observability data Honeycomb holds rather than feeding a workspace table.

It keeps your observability surface within reach of the agents working in your workspace, in the same place they reach the rest of your stack. An agent can pull a trace or service-level view from Honeycomb while it works on a question, instead of treating it as a separate silo. The connection is an availability link, not a data feed.

Only if Honeycomb begins exposing structured entities through its MCP server that map onto what Well captures. Until then, Well will not manufacture a synced record to fill the page. If that changes, the data-flow section would show the real entities rather than placeholders; for now the value is observability reach for your agents.

Disconnect Honeycomb in Well and the OAuth token is revoked and the MCP reach ends immediately. Because nothing structured was being synced, there are no workspace records to retain or purge from the connection. It simply removes Honeycomb from the set of tools your agents can reach through Well.