Honeycomb MCP server
- Endpoint
-
https://mcp.honeycomb.io/mcp - Transport
- streamable-http
- Docs
- https://docs.honeycomb.io/integrations/mcp
OAuth · resolves from well-known metadata Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.
Authorization: Bearer <credential> Create a team Management API key in the Honeycomb UI: log in, go to Account → Team Settings → API Keys → Create Management API Key, choose the needed scopes, then copy and store both the Key ID and Secret. For MCP API-key auth, Honeycomb's owner declaration and troubleshooting docs say to send them together as `<Key ID>:<Secret Key> in the Authorization header as a bearer token; the MCP docs specifically mention mcp:read and mcp:write` permissions. See Manage Team API Keys, Connect to Honeycomb MCP, and Honeycomb's integrations.json declaration.