Fanout · labstack — Claude Code MCP server: what it does, how to install
Fanout ingests OpenTelemetry traces, logs, and metrics, then exposes investigation tools, dashboards, and alerts to an MCP client.
Open on GitHubWhat Fanout does
Fanout accepts OTLP over gRPC and HTTP and keeps traces, logs, and metrics together. Telemetry is stored in Parquet, DuckDB handles analytical queries, and SQLite keeps transactional product state. The same binary includes the investigation agent, MCP server, browser client, dashboards, and alerts.
An MCP client connects to Fanout through an externally reachable HTTPS origin and its /mcp endpoint. OAuth handles client registration and scope approval. The client must support MCP 2026-07-28 over stateless Streamable HTTP. Chat needs either ANTHROPIC_API_KEY with the Anthropic provider or OPENAI_API_KEY with the OpenAI provider.
Fanout runs as a single node with no clustering, replication, or object tier. A deployment that outgrows one machine’s disk or CPU has outgrown Fanout. The project is pre-release and changes without migration paths, so that constraint matters before deployment.
What it helps with
- investigate service errors through traces
- keep logs, metrics, and traces in one store
- ask an agent questions about telemetry
- build dashboards for service signals
- trigger alerts for latency and error rate
Example prompts for the agent
- Investigate the rise in errors and latency for this service using Fanout traces and metrics.
- Show logs and related traces for requests reaching the
checkoutservice. - Create a dashboard for this service with throughput, latency, and error rate.
How to install Fanout
1Template address
The server address is a template: replace {…} or […] with your own values
2Platform CLI: remote server
claude mcp add --transport http fanout https://{fanout_host}/mcp1Template address
The server address is a template: replace {…} or […] with your own values
2Platform CLI: remote server
codex mcp add fanout --url https://{fanout_host}/mcp1Template address
The server address is a template: replace {…} or […] with your own values
2Config file
{
"mcpServers": {
"fanout": {
"url": "https://{fanout_host}/mcp"
}
}
}1Template address
The server address is a template: replace {…} or […] with your own values
2Config file
{
"servers": {
"fanout": {
"type": "http",
"url": "https://{fanout_host}/mcp"
}
}
}1Template address
The server address is a template: replace {…} or […] with your own values
2Platform CLI: remote server
gemini mcp add -t http fanout https://{fanout_host}/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Fanout
How do I install Fanout in Claude Code?
Add the MCP server with claude mcp add --transport http fanout https://{fanout_host}/mcp.
What does Fanout do?
It receives OTLP telemetry, stores traces, logs, and metrics, and exposes typed query tools for agent-led investigations. It also provides dashboards and alerts through its browser client.
What does an MCP client need to connect?
Fanout requires a stable, externally reachable HTTPS origin with an /mcp endpoint. The client must support MCP 2026-07-28 over stateless Streamable HTTP; older versions and the initialize handshake are unsupported.
Similar MCP servers
All MCP servers for DevOps and infrastructure →Fanout by other authors comes first.
