What it does
Investigate OpenTelemetry traces, metrics, and logs, and manage personal dashboards.
- Connects 在云端运行
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 26/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 38/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 72 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Pitot。按照 https://mcp.popnx.com/i/labstack-pitot.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 你的提问会经过开发者的服务器({pitot_host}) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
地址中有 {…} 部分,需要先改成你自己的 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称PitotRemote MCP server URL · 地址https://{pitot_host}/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsPitot
试一试
用 Pitot 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Pitot,或回答中出现 Pitot 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页 · 地址中有 {…} 部分,需要先改成你自己的
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称PitotConnection · 地址https://{pitot_host}/mcp在聊天中选择 Pitot
开启新聊天,输入前先从插件列表中选择 Pitot
试一试
用 Pitot 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Pitot,或回答中出现 Pitot 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code,但需要先准备
地址中有 {…} 部分,需要先改成你自己的
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user pitot 'https://{pitot_host}/mcp'在 Claude Code 中输入 /mcp
应能看到 Pitot 在列表中并显示已连接
试一试
用 Pitot 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Pitot,或回答中出现 Pitot 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
地址中有 {…} 部分,需要先改成你自己的
打开 Cursor 的 MCP 设置文件
~/.cursor/mcp.json
粘贴这些设置,填写空着的值并保存
{ "mcpServers": { "pitot": { "url": "https://{pitot_host}/mcp" } } }在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 Pitot 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Pitot,或回答中出现 Pitot 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
地址中有 {…} 部分,需要先改成你自己的
打开 VS Code 的 MCP 设置文件
MCP: Open User Configuration
粘贴这些设置,填写空着的值并保存
{ "servers": { "pitot": { "type": "http", "url": "https://{pitot_host}/mcp" } } }在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 Pitot 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Pitot,或回答中出现 Pitot 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://{pitot_host}/mcpJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user pitot 'https://{pitot_host}/mcp'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"pitot": {
"url": "https://{pitot_host}/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"pitot": {
"type": "http",
"url": "https://{pitot_host}/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
它能做什么
这个地址需要填入你自己的值,所以我们无法替你读取工具列表。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 labstack 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于今天
- ✓ 通过
有许可证
使用 Apache-2.0
- – 不适用
端点有响应
这个地址需要填入你自己的账户信息,所以我们无法替你检查
- – 不适用
使用 OAuth 登录
这个地址需要填入你自己的账户信息,所以我们无法替你检查
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/labstack-pitot)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6116 个服务器的 97%
- 发布到注册中心的时间比此分类中其他 6116 个服务器的 99% 更新
- 基础检查结果等于或优于此分类中其他 6116 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Pitot 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于今天,最新版本(2026.11.9-alpha)于昨天进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 Pitot | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Pitot
Pitot (pronounced PEE-toh).
Observability your agents can operate. Send OpenTelemetry to one binary, then investigate with Pitot's built-in agent or connect your own over MCP.
*Current Pitot interface with deterministic offline sample telemetry.*
Pitot keeps OpenTelemetry traces, logs, and metrics in one binary and one data directory, with no external storage services to operate. Pitot is pre-release and changes without migration paths; the browser client, built-in agent, MCP tools, dashboards, and alerts are preview capabilities (status). Start with the documentation or run it below.
- OTLP ingest over gRPC and HTTP, with local Parquet storage and DuckDB analytics.
- Explore and PitotQL for querying telemetry without an AI provider.
- An investigation agent that answers questions about your telemetry in plain language.
- An MCP server for external agents using the same typed query tools.
- Dashboards across traces, logs, and metrics, and alerts on service error rate, latency, throughput, and log volume.
Quick start
Docker
docker run --name pitot --restart unless-stopped -p 7520:7520 \
-v pitot-data:/var/lib/pitot/data \ -e PITOT_AUTH_CODE_SECRET=$(openssl rand -hex 32) \ labstack/pitot:latest
Open the one-time setup URL printed by the container and create the first administrator. Pitot displays the ingest token exactly once, unless PITOT_INGEST_TOKEN already set it; save it with your collector secrets. For later sign-in without SMTP, mint a 15-minute, single-use link against the running container's control database:
docker exec pitot pitot login-link admin@example.com
The UI, API, MCP, and both OTLP transports share port 7520. See installation for image defaults and bind-mount ownership, and first boot for setup and SMTP login.
Native binary
Install a checksum-verified release for Linux or macOS, amd64 or arm64:
curl -fsSL https://raw.githubusercontent.com/labstack/pitot/main/scripts/install.sh | sh
export PITOT_AUTH_CODE_SECRET=$(openssl rand -hex 32) pitot
Set PITOT_VERSION to a release tag, such as v2026.11.0-alpha, to pin a release, and PITOT_PREFIX to choose the installation directory. Native installs bind 127.0.0.1:7520; set PITOT_ADDR=:7520 for remote access, then follow the same first-boot setup.
Send telemetry
A standard OTLP/HTTP exporter can use the saved ingest token:
export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:7520 export OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer%20$INGEST_TOKEN"
For a Collector on the same private container network, the forwarding side is:
exporters:
otlp_http/pitot: endpoint: http://pitot:7520 headers: Authorization: "Bearer ${env:INGEST_TOKEN}"
service: pipelines: traces: { receivers: [otlp], exporters: [otlp_http/pitot] } metrics: { receivers: [otlp], exporters: [otlp_http/pitot] } logs: { receivers: [otlp], exporters: [otlp_http/pitot] }
Use an existing otlp receiver, set INGEST_TOKEN, and replace pitot with the Collector's reachable private hostname. OTLP/gRPC uses localhost:7520 locally; see send telemetry for TLS and HTTP/2 setup.
Enable chat
Select PITOT_AI_PROVIDER=anthropic and inject ANTHROPIC_API_KEY, or select PITOT_AI_PROVIDER=openai and inject OPENAI_API_KEY, then restart Pitot; the selected provider requires its key at startup. With no provider, chat is disabled and the other features still work. See AI settings.
Connect an MCP client
Set PITOT_PUBLIC_URL to your stable, externally reachable HTTPS origin, then point a remote MCP client at that origin's /mcp endpoint. The client discovers and registers through OAuth; you authorize its scopes in the browser. Pitot serves MCP 2026-07-28 and, through the initialize handshake, 2025-11-25 and 2025-06-18 over Streamable HTTP. See connect over MCP for setup and permissions.
How it compares
| If you use | Where Pitot differs |
|---|---|
| Grafana with Loki, Tempo, and Mimir | That stack keeps a service and a query language per signal, plus object storage underneath. Pitot keeps one process, one data directory, and one typed contract across all three signals, at the cost of the horizontal scale those components are built for. |
| SigNoz | Both are OTLP-native and self-hosted. SigNoz composes a collector, ClickHouse, and query services; Pitot compiles ingest, authoritative Parquet storage, indexed trace reads, DuckDB analytics, alerting, and the browser client into one binary. |
| Jaeger | Jaeger covers traces and expects a storage backend you run separately. Pitot ingests traces, logs, and metrics into the same store, with nothing else to deploy. |
| Prometheus with Grafana | Prometheus pulls metrics and is excellent at them. Pitot accepts pushed OTLP for all three signals and is built around investigating a specific incident rather than maintaining long-range metric series. |
| Datadog, Honeycomb, Grafana Cloud | Those are managed services: someone else runs the storage, the scaling, and the upgrades, and your telemetry leaves your network to get there. Pitot is a binary you run, on data that stays on your disk. |
| An OpenTelemetry Collector piped into ClickHouse | The same shape, assembled by hand: collector, database, dashboards, and the glue between them. Pitot is that assembly as one program, with an agent and an MCP server already wired to the same query contract. |
Pitot is a single node. It has no clustering, no replication, and no object tier; a deployment that outgrows one machine's disk and CPU has outgrown Pitot.
Architecture
One process contains ingest, storage, query, alerts, the agent, MCP, and the React client. Browser and agent clients share a typed observability contract.
Parquet holds telemetry, DuckDB query state is rebuildable, and SQLite holds transactional product state. See how storage works for durable ingest, indexed reads, and compaction while reads continue.
Configuration
Configuration is environment-only: built-in defaults followed by nonempty process environment values, validated before data files or listeners open. Settings are read once at startup; every change requires a restart.
| Environment variable | Default | Purpose |
|---|---|---|
PITOT_ADDR | 127.0.0.1:7520 | UI, API, MCP, and both OTLP transports |
PITOT_DATA_DIR | ./data | Parquet, query state, and control SQLite |
PITOT_AUTH_MODE | local | Login link or SMTP, or oidc |
PITOT_AUTH_CODE_SECRET | — | Required in local mode and for OIDC break-glass links, 32+ characters |
PITOT_AI_PROVIDER | — | Empty disables chat; anthropic or openai enables it |
ANTHROPIC_API_KEY | — | Required for Anthropic chat |
OPENAI_API_KEY | — | Required for OpenAI chat |
PITOT_RETENTION_DAYS | 30 | Telemetry retention window |
PITOT_MCP_ENABLED | true | Serve the MCP endpoint at /mcp |
Every secret accepts _FILE instead of its value; see the settings reference for validation and runtime secret delivery for deployment examples.
Advanced DuckDB sizing
Pitot sizes DuckDB automatically; measured workloads can override memory, connections, and threads as described in DuckDB sizing.
For TLS, health checks, backups, upgrades, retention, and recovery, see the operator runbook.
Performance
Pitot v2026.11.0-alpha accepted 507,311 mixed OpenTelemetry items/s over 306.8 seconds on a Hetzner Cloud ccx33 (8 dedicated vCPUs, 32 GB RAM), with telemetrygen on a separate ccx33. The ingest run on 6 November 2026 passed every quality gate. See the performance methodology. Pitot Bench reproduces the measurement on your hardware.
Build from source
- Go 1.27.3 and a C/C++ toolchain on native Linux or macOS, amd64 or arm64. Build with
just buildorbash scripts/with-duckdb.sh go build ./cmd/pitot; the wrapper supplies DuckDB's pinned headers, static libraries, and CGO flags. The first build needs network access to download the checksum-verified engine. - [Bun](https://bun.sh) — compiles the browser assets
- Node.js 24.19.0 — runs development helpers and builds the documentation site
- [just](https://just.systems) — task runner
- A 32-character authentication code secret
git clone https://github.com/labstack/pitot.git
cd pitot just install # browser dependencies and git hooks just build # browser assets, then the binary
Run it with the minimum configuration:
export PITOT_AUTH_CODE_SECRET=$(openssl rand -hex 32) # must be 32+ characters
./bin/pitot
Open http://localhost:7520 and follow first-boot setup. SMTP and chat are optional; without SMTP, run ./bin/pitot login-link admin@example.com with the same configuration and data directory.
Development
Run just to list recipes, just check for the full gate, just test for Go tests, and just ui to rebuild embedded browser assets. See CONTRIBUTING.md for environment setup, generated assets, hooks, and project layout.
Releases
Versions are CalVer — vYYYY.M.N[-alpha|-beta|-rc], numbered from 0 within each month across all maturity suffixes. Pitot is alpha (for example, v2026.11.0-alpha); GA has no suffix. Container tags omit the leading v, and every release moves latest. Tagged releases publish identical manifests to Docker Hub (labstack/pitot) and GHCR (ghcr.io/labstack/pitot); GHCR is canonical and also carries development images.
| Image tag | Points at |
|---|---|
labstack/pitot:latest | the newest release, mirrored on Docker Hub |
labstack/pitot:2026.11.0-alpha | that exact release, mirrored on Docker Hub |
ghcr.io/labstack/pitot:latest | the newest release |
ghcr.io/labstack/pitot:2026.11.0-alpha | that exact release |
ghcr.io/labstack/pitot:main | the tip of main |
| `ghcr.io/labstack