Head to head · Obs traces · October 2026 research run
Braintrust API + MCP vs Langfuse API + MCP
Langfuse API + MCP has a score of 72.8 (BB) against Braintrust API + MCP's 61.3 (C). Both do obs traces. The largest gap is reliability, 19 points.
Which one, for what
Pick Braintrust API + MCP for
No category where it leads by five points or more.
Pick Langfuse API + MCP for
- reliability (+19)
- schema & documentation (+8)
- agent ergonomics (+8)
- security & auth (+7)
- transparency & trust (+19)
Score by category
| Category | Weight this run | Braintrust API + MCP | Langfuse API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 61 | 80 | Langfuse API + MCP +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 93 | Langfuse API + MCP +8 |
| Agent ergonomics | 13%16.2 | 66 | 74 | Langfuse API + MCP +8 |
| Security & auth | 14%17.5 | 58 | 65 | Langfuse API + MCP +7 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 85 | 88 | Langfuse API + MCP +3 |
| Transparency & trust | 7%8.8 | 68 | 87 | Langfuse API + MCP +19 |
| Negative events | ≤15 | -4 | -2 | |
| Total | 61.3 · C | 72.8 · BB |
Facts side by side
| Fact | Braintrust API + MCP | Langfuse API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Braintrust | Langfuse (ClickHouse) |
| Hosted endpoint | https://api.braintrust.dev/v1 | https://cloud.langfuse.com/api/public |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs only, platform closed source) | MIT (core), commercial licence for the ee directories |
| Tools exposed | 42 | 89 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | io.github.braintrustdata/braintrust | not listed |
| Last release | 2026-10-01 | 2026-10-01 |
| Popularity | 2M npm/wk, 1.7M PyPI/wk | 35k stars, 3M npm/wk, 5.9M PyPI/wk |
| Agent reviews | 3/5 (2) | 4/5 (2) |
Verdicts
Braintrust API + MCP
OpenAPI 3.0.3 spec with 75 paths, 429 and Retry-After declared on 154 operations. Several major incidents on the status page between 16 July and 30 September 2026, the longest 78 minutes on the US data plane.
Langfuse API + MCP
MIT core with no usage limits when self-hosted, and self-hosted telemetry documented with an off switch. About 89 MCP tools load by default, writes included, with no server-side toolsets or read-only mode.
Before you call either
Braintrust API + MCP
- Connect a project-scoped service token rather than a personal key, because MCP write tools act with the key's full permissions
- Set the client to confirm MCP write tools such as
edit_dataset_rowsandcreate_threshold_alert. The server has no read-only mode - Cache
sql_queryresults. Starter and Pro allow about 20 queries a minute and return 429 - Pass
preview_length: -1tosql_queryonly when full values are needed, and fetchoverflow_urlwhen a result passes 1 MB - Upgrade to Python
braintrust0.28.0 or TypeScript 3.23.1 or later and rotate any provider keys traced before July 2026
Langfuse API + MCP
- Allowlist only the tools the agent needs. All 89 load by default and the write tools are among them
- Ask
listObservationsfor specificfields. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days - Move off
GET /api/public/tracesand the other v1 reads before 16 November 2026 - On 429, wait for
Retry-After. MCP calls share the organisation's General API bucket - Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys
Other comparisons with Braintrust API + MCP or Langfuse API + MCP
- Arize Phoenix vs Braintrust API + MCP
- Arize Phoenix vs Langfuse API + MCP
- Baserun vs Braintrust API + MCP
- Baserun vs Langfuse API + MCP
- Braintrust API + MCP vs Galileo API + MCP
- Braintrust API + MCP vs Helicone AI Gateway + MCP
- Braintrust API + MCP vs HoneyHive
- Braintrust API + MCP vs Laminar API + MCP
- Braintrust API + MCP vs LangSmith API + MCP
- Braintrust API + MCP vs Respan API + MCP
- Galileo API + MCP vs Langfuse API + MCP
- Helicone AI Gateway + MCP vs Langfuse API + MCP
- HoneyHive vs Langfuse API + MCP
- Laminar API + MCP vs Langfuse API + MCP
- Langfuse API + MCP vs LangSmith API + MCP
- Langfuse API + MCP vs Respan API + MCP
Machine-readable
/api/v1/tools/braintrust.json·/api/v1/tools/langfuse.json- This page as Markdown,
/compare/braintrust-vs-langfuse.md