Honeycomb Remote MCP Server
Honeycomb's official MCP brings observability-driven debugging to agents — query traces, analyze latency outliers, inspect SLOs and explore high-cardinality telemetry data. Endpoint verified live on RemoteMCP.net (preflighted 401 OAuth challenge).
- Provider
- Honeycomb ↗
- Categories
- ☁️ Cloud, Infrastructure & DevOps
中文简介
Honeycomb 官方托管的远程 MCP 服务器。Honeycomb 官方 MCP,为代理带来可观测性调试:查询 Trace、分析延迟异常与探索高基数遥测数据。
Maintainer of Honeycomb? Claim or update this listing →
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"honeycomb": {
"url": "https://mcp.honeycomb.io/mcp"
}
}
}claude mcp add --transport http honeycomb https://mcp.honeycomb.io/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"honeycomb": {
"type": "http",
"url": "https://mcp.honeycomb.io/mcp"
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.honeycomb.io/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"honeycomb": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.honeycomb.io/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"honeycomb": {
"serverUrl": "https://mcp.honeycomb.io/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"honeycomb": {
"url": "https://mcp.honeycomb.io/mcp"
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.honeycomb] url = "https://mcp.honeycomb.io/mcp"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"honeycomb": {
"type": "streamableHttp",
"url": "https://mcp.honeycomb.io/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"honeycomb": {
"httpUrl": "https://mcp.honeycomb.io/mcp"
}
}
}🧰 Honeycomb MCP Tools & Schema (0)
| Tool | Safety | Description | Parameters |
|---|
🛡️ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLM’s context on every request — Estimate per-call LLM token cost →
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
🔐 OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- —
- PKCE S256
- ✅ Supported
- Protected resource metadata
- https://mcp.honeycomb.io/.well-known/oauth-protected-resource (expected location)
🧩 Recommended Agent Skills
📖 Honeycomb MCP Endpoint Overview & Security Guide
Honeycomb — Remote MCP Server
Honeycomb's official MCP brings observability-driven debugging to agents — query traces, analyze latency outliers, inspect SLOs and explore high-cardinality telemetry data. The remote endpoint means there is nothing to install — point your MCP client at the URL and complete the OAuth consent screen. Honeycomb operates and versions the server themselves, so tool coverage tracks their API surface as it ships.
Official Honeycomb Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.honeycomb.io/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Honeycomb does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Honeycomb uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE — and simply open a browser consent screen.
All 0 cataloged tools are read-only — Honeycomb cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Id— just re-sendinitialize; stateless clients can ignore session headers entirely.
🚀 How to Connect
- Copy the Honeycomb endpoint URLThe remote endpoint is https://mcp.honeycomb.io/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http honeycomb https://mcp.honeycomb.io/mcp. Cursor: add"honeycomb": { "url": "https://mcp.honeycomb.io/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Honeycomb consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.honeycomb.io/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Honeycomb's 0 tools respond.
❓ FAQ
What is the Honeycomb remote MCP endpoint?
The primary endpoint is https://mcp.honeycomb.io/mcp. It is an official first-party server operated by Honeycomb, speaking the Streamable HTTP transport.
How do I authenticate with Honeycomb?
Honeycomb uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen.
I'm getting a 401 Unauthorized from Honeycomb — what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Honeycomb?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http honeycomb https://mcp.honeycomb.io/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Honeycomb expose?
0 tools are cataloged in this directory — including . Use our online inspector to fetch the live tool list straight from the endpoint.
🔗 Connect Guides
📛 Embed Status Badge in README
Related Servers
AWS Knowledge's hosted remote MCP server. AWS's fully-managed public knowledge MCP gives agents access to the latest AWS documentation, API references, What's New posts and architectural guidance across all AWS services. It is public and unauthenticated — connect and call tools immediately.
Cloudflare's free, authless documentation MCP server. Agents can search the full Cloudflare docs corpus — no account or token required.
Vercel's official remote MCP server. Agents can list deployments, fetch build logs and search Vercel docs with a token-authorized connection.
Sentry's hosted MCP server for error monitoring. Agents can inspect issues, search events and resolve regressions directly from your IDE.