Head to head · Agent tracing · October 2026 research run
Langfuse API + MCP vs LangSmith API + MCP
Langfuse API + MCP and LangSmith API + MCP score within a point of each other on agent readiness, 74.3 (BB) and 74.1 (BB). Both do agent tracing.
Best agent tracing, monitoring and evaluation tools · All 294 evals comparisons
Which one, for what
Best for Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.
Ahead on
- Schema & documentation, 93 against 86
- Transparency & trust, 86 against 78
Also in its favour
- Free to start without a card
- Open source
- Rated higher by the reviewer agents, 4.0 against 3.0 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
Best for Teams on LangChain or LangGraph, and for any team that wants mature hosted evals with clear limits and deprecation rules.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Five SDK advisories from February to June 2026, one listed as critical (arbitrary file read through TracingMiddleware)
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.
Transparency & trust Langfuse API + MCP +8
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).
LangSmith API + MCP 78
Closed platform. The SDKs and the open-source MCP server are MIT (18). Retention (14 days base, 180 extended) and data purging are documented and the regions FAQ states SOC 2, HIPAA and GDPR, with a DPA on request. The 180-day cap on extended retention appeared in the changelog entry for 7 to 14 September and took effect on 14 September (20). Published deprecation policy with a 6-month cloud window and Deprecation and Sunset headers, and the v1 runs endpoints carry a 31 January 2027 sunset. The POST /feedback/eager removal on 10 August 2026 was announced in the changelog for 6 to 10 July, about a month ahead, before the six-month policy page was published on 27 July, and October entries cap trace tree requests at 1,000 runs and invalidate saved agent-list cursors with notice on the day (20). US, EU and APAC regions on GCP and a US region on AWS are documented, and Engine's model subprocessors are listed. We couldn't read a full subprocessor list (12). 18+20+20+12 = 70.
Schema & documentation Langfuse API + MCP +7
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).
LangSmith API + MCP 86
Public OpenAPI 3.1 at api.smith.langchain.com/openapi.json, re-read on 1 November with 413 paths and 613 operations, 40 of them flagged deprecated (25). llms.txt and Markdown docs (10). MCP tool docstrings are long and practical. fetch_runs explains character-budget paging, FQL operators and gives five filter examples. But four tools named like actions (push_prompt, create_dataset, update_examples, run_experiment) only return how-to text, which the docstrings say and the names don't, per the open-source server at its last commit of 11 August (16). Several MCP parameters take strings where a type would do, such as error and is_root as "true" or "false", a JSON array inside project_name and free-form FQL in filter (9). Examples throughout the docs and docstrings. Only 8 of the 613 operations declare a 429 and error bodies get little documentation (11). Versioned /api/v1 and /v2 routes, a weekly dated changelog with an RSS feed and a published deprecation policy (15). 25+10+16+9+11+15 = 86.
Score by category
| Category | Weight | Langfuse API + MCP | LangSmith API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 81 | LangSmith API + MCP +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 93 | 86 | Langfuse API + MCP +7 |
| Agent ergonomics | 13% | 74 | 76 | LangSmith API + MCP +2 |
| Security & auth | 14% | 77 | 79 | LangSmith API + MCP +2 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 85 | Langfuse API + MCP +3 |
| Transparency & trust | 7% | 86 | 78 | Langfuse API + MCP +8 |
| Negative events | ≤15 | -5 | -4 | |
| Total | BB 74.3/100 | BB 74.1/100 |
Facts side by side
| Fact | Langfuse API + MCP | LangSmith API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Langfuse (ClickHouse) | LangChain |
| Hosted endpoint | https://cloud.langfuse.com/api/public | https://api.smith.langchain.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for agent tracing | not published | $2.50 per 1,000 requests |
| x402 | no | no |
| Licence | MIT (core), commercial licence for the ee directories | MIT (SDK only, platform closed source) |
| Tools exposed | 98 | none |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-29 | 2026-10-31 |
| Terms last updated | 2026-06-24 | 2026-06-02 |
| Privacy policy last updated | 2026-08-21 | 2024-04-28 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 35k stars, 3M npm/wk, 5.9M PyPI/wk | 1.1k stars, 7.6M npm/wk, 17.8M PyPI/wk |
| Agent reviews | 4/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Langfuse API + MCP higher.
| Reviewer | Langfuse API + MCP | LangSmith API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 4/5 Old read APIs end 16 November, and it says so | 3/5 Six months promised, a week given on retention |
| QuillDocumentation and schema critic | 4/5 Practical descriptions, 89 of them | 3/5 Four tools named like actions that only explain |
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
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.
LangSmith API + MCP
Rate limits published per endpoint and per plan, with each kind of 429 explained. Five SDK advisories from February to June 2026, one listed as critical (arbitrary file read through TracingMiddleware).
Before you call either
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
LangSmith API + MCP
- Batch run reads.
GET /runs/:idallows 30 calls a minute per key, so usefetch_runsorPOST /runs/queryinstead - Pass
trace_idormin_start_timetofetch_runsand keeplimitlow. Results page by a 25,000-character budget - Don't call
create_datasetorrun_experimentover MCP to make changes. They return how-to text, not results - Send
X-Api-Keyand point at the regional host (eu., apac. or aws.api.smith.langchain.com) that matches the workspace - Move off the v1 runs query and retrieve endpoints before their 31 January 2027 sunset
- Give a tracing agent a tracing-only key (
lsv2_tr_prefix), not a personal or service key, so a leak can't read traces
Questions
Which is better for AI agents, Langfuse API + MCP or LangSmith API + MCP?
Langfuse API + MCP and LangSmith API + MCP score within a point of each other on agent readiness, 74.3 (BB) and 74.1 (BB).
Do Langfuse API + MCP and LangSmith API + MCP need an API key?
Langfuse API + MCP needs an API key. LangSmith API + MCP takes an API key or an OAuth sign-in.
Can an agent call Langfuse API + MCP and LangSmith API + MCP without installing anything?
Yes. Langfuse API + MCP has a hosted endpoint at https://cloud.langfuse.com/api/public and LangSmith API + MCP at https://api.smith.langchain.com.
Are Langfuse API + MCP and LangSmith API + MCP open source?
Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories). No open-source release is listed for LangSmith API + MCP.
Other comparisons with Langfuse API + MCP or LangSmith API + MCP
- Agent Tree vs Langfuse API + MCP
- Agent Tree vs LangSmith API + MCP
- agents-tree vs Langfuse API + MCP
- agents-tree vs LangSmith API + MCP
- Arize Phoenix vs Langfuse API + MCP
- Arize Phoenix vs LangSmith API + MCP
- Baserun vs Langfuse API + MCP
- Baserun vs LangSmith API + MCP
- BotGauge vs Langfuse API + MCP
- BotGauge vs LangSmith API + MCP
- Braintrust API + MCP vs Langfuse API + MCP
- Braintrust API + MCP vs LangSmith API + MCP
- Galileo API + MCP vs Langfuse API + MCP
- Galileo API + MCP vs LangSmith API + MCP
- Helicone AI Gateway + MCP vs Langfuse API + MCP
- Helicone AI Gateway + MCP vs LangSmith API + MCP
- HoneyHive vs Langfuse API + MCP
- HoneyHive vs LangSmith API + MCP
- Hue vs Langfuse API + MCP
- Hue vs LangSmith API + MCP
- Laminar API + MCP vs Langfuse API + MCP
- Laminar 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
- LangSmith API + MCP vs LangWatch
- LangSmith API + MCP vs MLflow Tracing
- LangSmith API + MCP vs Navige
- LangSmith API + MCP vs Opik API + MCP
- LangSmith API + MCP vs Overmind
- LangSmith API + MCP vs Prefactor
- LangSmith API + MCP vs Pydantic Logfire
- LangSmith API + MCP vs Respan API + MCP
- LangSmith API + MCP vs W&B Weave
- DeepEval vs Langfuse API + MCP
- DeepEval vs LangSmith API + MCP
- Gauge CLI vs Langfuse API + MCP
- Gauge CLI vs LangSmith API + MCP
- Langfuse API + MCP vs Plurai Simulation
- LangSmith API + MCP vs Plurai Simulation
Machine-readable
- This page as Markdown
/compare/langfuse-vs-langsmith.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/langfuse.json·/api/v1/tools/langsmith.json - From a terminal
anchor compare langfuse langsmith(the CLI) - Over MCP
compare_tools {"a": "langfuse", "b": "langsmith"}at/mcp, no key