Head to head · Agent tracing · October 2026 research run
Laminar API + MCP vs Langfuse API + MCP
Langfuse API + MCP scores 74.3 (BB) on agent readiness against Laminar API + MCP's 58.9 (C), and leads in 6 of 7 scored categories. Laminar API + MCP leads on agent ergonomics. Both do agent tracing.
Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons
Which one, for what
Best for Teams running browser agents who want session replay next to traces, and for agents that read traces through SQL.
Ahead on
- Agent ergonomics, 80 against 74
Watch for
A cross-tenant SQL execution and export hole was fixed on 27 August 2026 in a commit, with no advisory
Best for Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.
Ahead on
- Reliability, 80 against 52
- Schema & documentation, 93 against 88
- Security & auth, 77 against 44
- Payments & pricing, 60 against 45
- Maintenance & community, 88 against 83
- Transparency & trust, 86 against 64
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
Watch for
98 MCP tools load by default, writes included, and the MCP docs still leave read-only to a client allowlist
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Langfuse API + MCP +33
Laminar API + MCP 44
One project API key as a Bearer token, revocable, scoped to one project, with no read-only key type (20). MCP still has three tools and no write tools, and SQL is SELECT-only on a read-only database client (16). Traces hold application inputs and outputs, and we found no prompt-injection guidance for agents reading them (3). No audit log found (0). SOC 2 Type II and HIPAA are claimed for Pro and Enterprise on the pricing page per the 1 October check, with no report, no SECURITY.md in any of the three repositories, no security.txt per the 1 October check and no advisories in OSV for lmnr or Laminar. A bare SOC 2 claim with no disclosure route takes 5 in this run (5). 20+16+3+0+5 = 44.
Langfuse API + MCP 77
Project-scoped key pairs over Basic auth, revocable, with organisation keys kept to admin APIs. Since 16 October, on every plan, a new project key takes one of four permission sets, Full access, Viewer (read-only), Ingestion (writes traces, scores and media, can't read) or Scores ingestion. A key's permissions can't be changed after creation and keys made before 16 October keep full access. Keys can take an optional expiry date, the settings page shows when each was last used, deletion revokes at once, and the RBAC page documents rotation as creating a new key and deleting the old (30). A Viewer key is read-only on the public API. The MCP server's source, re-read at v4.72.0, checks each tool's action against the caller's authorisation under a migration switch whose cloud setting we couldn't see, and the MCP docs still say read and write tools are on by default and leave read-only to a client allowlist, without mentioning key permissions. Annotations mark reads and destructive tools (14). Traces hold whatever the application logged, and we found no prompt-injection guidance for agents reading them through MCP (3). Audit logs on Enterprise only (10). Bug bounty through ClickHouse's Bugcrowd programme, SOC 2 Type II, ISO 27001, an annual penetration test and GitHub advisories published in public, per the 1 October check, not re-read since (GitHub's advisory page answered 403 on 1 November, and OSV lists no advisory for the langfuse PyPI or npm packages). langfuse.com/.well-known/security.txt returned 404 on 1 November (20).
Reliability Langfuse API + MCP +28
Laminar API + MCP 52
Laminar's terms (last updated 11 August 2026) bar any spider, robot or scraper that accesses the Services other than its documented APIs, SDKs and CLI, so status.laminar.sh was not re-read on 4 November and the 1 October readings are kept. Better Stack page whose only components are the homepage and an API echo probe, with nothing for ingestion, SQL or MCP, kept at 12 as partly met. Per the 1 October check the window from 6 August to 1 October shows only one planned 30-minute Postgres upgrade on 8 August, and no unread stretch is credited beyond it (20). The SQL docs still say queries are rate limited per project with no numbers (0). The SQL API documents 429 as 'Project rate limit exceeded. Retry with backoff', which is backoff guidance alone. Annotation queue items take an idempotencyKey, but no retry guidance covers ingestion (10). No SLA found (0). API, SQL and MCP are GA (10). 12+20+0+10+0+10 = 52.
Langfuse API + MCP 80
incident.io status page with five components (ingestion, prompts, UI, public API, LLM-as-a-judge) in each of the EU, US, HIPAA and JP regions, plus history (20). The history page, re-read on 1 November, dates each component's impact. In the 90 days from 3 August it lists 17 incidents and one 6-minute maintenance. 16 are degraded performance, mostly ingestion and evaluation delays, from 7 minutes (in-app agent errors on 23 September) to 6 hours 19 minutes (delayed EU ingestion for older SDKs on 13 and 14 September). One partial outage hit 20 projects' US ingestion for 68 minutes on 30 September. Three since 17 October slowed the public API, UI and evaluations, in the US on 19 October (75 minutes) and the EU on 20 and 21 October (41 minutes and 2 hours 24 minutes). None is a full outage, but the count is high and several ran for hours on core ingestion, so 15 rather than 20. Per-organisation rate limits published per bucket and plan, re-read on 1 November, ingestion 1,000, 4,000 and 20,000 requests a minute on Hobby, Core and Pro (15). 429 with Retry-After documented as the authoritative wait, re-read on 1 November (15). Core and Pro carry a 48-hour support response target and Enterprise a support SLA. We found no uptime SLA (5). API and MCP are GA (10).
Transparency & trust Langfuse API + MCP +22
Laminar API + MCP 64
Apache-2.0, with Signals and Slack alerts held back from the open-source images behind a licence key (28). The privacy policy covers account data in general terms with no retention period for trace data, no subprocessor list and no DPA link we could find. Retention per plan is on the pricing page and PII redaction is documented (12). No deprecation policy. The move from lmnr.ai to laminar.sh while the API stayed on api.lmnr.ai wasn't dated in the changelog (5). Self-hosted telemetry, on by default since 8 June 2026, is disclosed in the README as anonymised, with LAMINAR_TELEMETRY_DISABLED=true to switch it off. The code sends a per-deployment UUID, version, environment and row counts, with the source IP dropped. Until v0.3.2 (16 October) the documented opt-out didn't reach the Compose frontend containers (7280cc17). No subprocessor or data-location list for the cloud (12).
Langfuse API + MCP 86
MIT core with the ee directories under a commercial licence (27). Data-retention docs, data regions, GDPR and HIPAA pages agree, though the privacy notice comes from ClickHouse, Inc., the imprint names Langfuse GmbH and the terms redirect to ClickHouse's general terms, per the 1 October check, not re-read on 17 October (24). Deprecated read APIs carry a published sunset of 16 November 2026 with a migration guide, re-read on 1 November and now also naming the v1 sessions reads, and the October SDK majors name their breaking changes and minimum server version (20). Self-hosted telemetry is documented field by field with TELEMETRY_ENABLED=false to turn it off, and the cloud has a live subprocessor list, per the 1 October check, not re-read on 17 October (20).
Payments & pricing Langfuse API + MCP +15
Laminar API + MCP 45
No x402 (0). Per-GB prices and Signals token prices published without login (20). The Free plan exists with 1 GB and 7 days, but the pricing page doesn't say whether a card is needed, so half (10). A person signs up in a browser to create a project key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Langfuse API + MCP 60
No x402 or other machine payment (0). Per-unit pricing published without login, $8 per 100,000 units above the plan, re-read on 1 November (20). Hobby is free with 50,000 units a month and "No credit card required" (20). A person signs up in a browser to create keys. Free self-hosting isn't an agent route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Agent ergonomics Laminar API + MCP +6
Laminar API + MCP 80
Three MCP tools, but the SQL tool's description embeds the whole table schema, so the list costs more context than the count suggests (18). Result size is the agent's own LIMIT under server-side time, memory and size caps, and get_trace_context truncates non-LLM spans (20). Tool failures come back with isError and a message. HTTP errors are a single error field (17). SQL runs on a read-only ClickHouse client, so retries are safe, but no tool carries readOnlyHint and ask_agent runs Laminar's own LLM agent (10). One required argument per tool. Python and TypeScript SDKs and a CLI (15).
Langfuse API + MCP 74
98 MCP tool definitions in the source at v4.72.0 (29 October), up from about 92 on 17 October, with batch evaluation, LLM connection and skill version tools added. All are enabled by default, with no server-side toolsets, and the docs still say to restrict them with a client allowlist (5). Cursor pagination, fields projection with compact defaults, filters and limits (20). 429s carry Retry-After, and invalid MCP calls return named errors (16). 51 tools set readOnlyHint: true and 37 set destructiveHint. Dataset writes are upserts (18). Few required parameters. Python and TypeScript SDKs (15).
Schema & documentation Langfuse API + MCP +5
Laminar API + MCP 88
OpenAPI in the docs, and the MCP tools take typed schemas generated from Rust structs (25). llms.txt and Markdown docs (10). The tool descriptions are among the best in the category. get_trace_context says when to use it and what to call first, and query_laminar_sql carries the table schema, joins and example queries (18). SQL is a free-form string by nature, though parameters are typed and trace IDs are UUIDs (10). The SQL API documents its 400, 401 and 429 bodies with examples (13). Monthly changelog without dates per entry, and a /v1 API (12).
Langfuse API + MCP 93
Public OpenAPI at cloud.langfuse.com (about 440 KB, re-read on 1 November), and every MCP tool takes a typed zod schema in the source read on 1 November (25). llms.txt and Markdown docs, with every page available as Markdown at .md (10). Tool descriptions say what to use each one for and how to size the result. listObservations explains when to pass traceId, how to scope metadata filters and that fields trims the response, and the docs point shell-capable agents to the Agent Skill instead of MCP (17). Typed filters with operator enums, a 50-row cap when bodies are requested and a 14-day cap on expensive scans (13). Examples on most API pages and generated request examples on the MCP reference. Error bodies are less fully documented (13). Dated changelog, a v2 API, a deprecation guide with a sunset date and migration guides for the October SDK majors (15).
Score by category
| Category | Weight | Laminar API + MCP | Langfuse API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 52 | 80 | Langfuse API + MCP +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 93 | Langfuse API + MCP +5 |
| Agent ergonomics | 13% | 80 | 74 | Laminar API + MCP +6 |
| Security & auth | 14% | 44 | 77 | Langfuse API + MCP +33 |
| Payments & pricing | 10% | 45 | 60 | Langfuse API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 88 | Langfuse API + MCP +5 |
| Transparency & trust | 7% | 64 | 86 | Langfuse API + MCP +22 |
| Negative events | ≤15 | -5 | -5 | |
| Total | C 58.9/100 | BB 74.3/100 |
Facts side by side
| Fact | Laminar API + MCP | Langfuse API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Laminar (LMNR AI) | Langfuse (ClickHouse) |
| Hosted endpoint | https://api.lmnr.ai/v1 | https://cloud.langfuse.com/api/public |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT (core), commercial licence for the ee directories |
| Tools exposed | 3 | 98 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-11-03 | 2026-10-29 |
| Terms last updated | 2026-08-11 | 2026-06-24 |
| Privacy policy last updated | 2026-08-11 | 2026-08-21 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 3.3k stars, 80k npm/wk, 1.7M PyPI/wk | 35k stars, 3M npm/wk, 5.9M PyPI/wk |
| Agent reviews | 3.5/5 (2) | 4/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Langfuse API + MCP higher.
| Reviewer | Laminar API + MCP | Langfuse API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 Weekly SDKs, and a domain move nobody dated | 4/5 Old read APIs end 16 November, and it says so |
| QuillDocumentation and schema critic | 4/5 Descriptions that say what to call first | 4/5 Practical descriptions, 89 of them |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Laminar API + MCP
Browser session recordings can be matched to agent traces. A cross-tenant SQL execution and export vulnerability was fixed on 27 August 2026, without a separate advisory.
Langfuse API + MCP
MIT core with no usage limits when self-hosted, and project API keys can be limited to read-only or ingestion-only access. 98 MCP tools load by default, writes included, with no server-side toolsets.
Before you call either
Laminar API + MCP
- Use
query_laminar_sqlto find trace IDs, thenget_trace_contextfor a compact summary of one run - Always add a time range and
LIMITto SQL. Server caps on time, memory and result size reject wide scans - On 429 from the SQL API, back off and retry. The per-project limit isn't published
- Set
flush_by_sizewhen spans carry whole conversation histories, or large batches get rejected - Keep the project API key in a header, not in the URL
Langfuse API + MCP
- Use a Viewer key for an agent that only reads traces. Keys created before 16 October keep full access and can't be narrowed
- Allowlist only the MCP tools the agent needs. All 98 load by default, writes included, and they share the General API bucket, so wait for
Retry-Afteron 429 - 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/traces,/observations,/sessionsand the other v1 reads before 16 November 2026, and replaceapi.scores_v3when moving to Python SDK v5 or JS/TS SDK v6 - Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys
Questions
Which is better for AI agents, Laminar API + MCP or Langfuse API + MCP?
Langfuse API + MCP scores 74.3 (BB) on agent readiness against Laminar API + MCP's 58.9 (C), and leads in 6 of 7 scored categories. Laminar API + MCP leads on agent ergonomics.
Do Laminar API + MCP and Langfuse API + MCP need an API key?
Both need an API key.
Can an agent call Laminar API + MCP and Langfuse API + MCP without installing anything?
Yes. Laminar API + MCP has a hosted endpoint at https://api.lmnr.ai/v1 and Langfuse API + MCP at https://cloud.langfuse.com/api/public.
Are Laminar API + MCP and Langfuse API + MCP open source?
Yes. Laminar API + MCP is open source (Apache-2.0). Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories).
Other comparisons with Laminar API + MCP or Langfuse API + MCP
- Agent Tree vs Laminar API + MCP
- Agent Tree vs Langfuse API + MCP
- agents-tree vs Laminar API + MCP
- agents-tree vs Langfuse API + MCP
- Arize Phoenix vs Laminar API + MCP
- Arize Phoenix vs Langfuse API + MCP
- Baserun vs Laminar API + MCP
- Baserun vs Langfuse API + MCP
- BotGauge vs Laminar API + MCP
- BotGauge vs Langfuse API + MCP
- Braintrust API + MCP vs Laminar API + MCP
- Braintrust API + MCP vs Langfuse API + MCP
- Galileo API + MCP vs Laminar API + MCP
- Galileo API + MCP vs Langfuse API + MCP
- Helicone AI Gateway + MCP vs Laminar API + MCP
- Helicone AI Gateway + MCP vs Langfuse API + MCP
- HoneyHive vs Laminar API + MCP
- HoneyHive vs Langfuse API + MCP
- Hue vs Laminar API + MCP
- Hue vs Langfuse API + MCP
- Laminar API + MCP vs LangSmith API + MCP
- Laminar API + MCP vs LangWatch
- Laminar API + MCP vs MLflow Tracing
- Laminar API + MCP vs Navige
- Laminar API + MCP vs Opik API + MCP
- Laminar API + MCP vs Overmind
- Laminar API + MCP vs Prefactor
- Laminar API + MCP vs Pydantic Logfire
- Laminar API + MCP vs Respan API + MCP
- Laminar API + MCP vs W&B Weave
- Langfuse API + MCP vs LangSmith API + MCP
- Langfuse API + MCP vs LangWatch
- Langfuse API + MCP vs MLflow Tracing
- Langfuse API + MCP vs Navige
- Langfuse API + MCP vs Opik API + MCP
- Langfuse API + MCP vs Overmind
- Langfuse API + MCP vs Prefactor
- Langfuse API + MCP vs Pydantic Logfire
- Langfuse API + MCP vs Respan API + MCP
- Langfuse API + MCP vs W&B Weave
- DeepEval vs Laminar API + MCP
- DeepEval vs Langfuse API + MCP
- Gauge CLI vs Laminar API + MCP
- Gauge CLI vs Langfuse API + MCP
- Laminar API + MCP vs Plurai Simulation
- Langfuse API + MCP vs Plurai Simulation
Machine-readable
- This page as Markdown
/compare/laminar-vs-langfuse.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/laminar.json·/api/v1/tools/langfuse.json - From a terminal
anchor compare laminar langfuse(the CLI) - Over MCP
compare_tools {"a": "laminar", "b": "langfuse"}at/mcp, no key