Head to head · Obs traces · October 2026 research run

Langfuse API + MCP vs LangWatch

Langfuse API + MCP scores 72.7 (BB) on agent readiness against LangWatch's 65.5 (B), and leads in 4 of 7 scored categories. LangWatch leads on security & auth. Both do obs traces.

Which one, for what

Langfuse API + MCP BB

Good 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 53
  • Schema & documentation, 93 against 87
  • Agent ergonomics, 74 against 67
  • Transparency & trust, 85 against 75

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

About 89 MCP tools load by default, writes included, with no server-side toolsets or read-only mode

LangWatch B

Good for Teams that want tracing, evaluations and simulated-user agent tests in one open-source product, hosted in the EU or self-hosted, and that drive it from a coding assistant through MCP or the CLI.

Ahead on

  • Security & auth, 71 against 65

Also in its favour

  • Runs on your own machine

Watch for

The MCP server registers 101 tools, deletes and key creation among them, with no toolsets and no readOnlyHint or destructiveHint annotations in the source

Score by category

CategoryWeight this runLangfuse API + MCPLangWatchEdge
Reliability16%208053Langfuse API + MCP +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29387Langfuse API + MCP +6
Agent ergonomics13%16.27467Langfuse API + MCP +7
Security & auth14%17.56571LangWatch +6
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88890LangWatch +2
Transparency & trust7%8.88575Langfuse API + MCP +10
Negative events≤15-2-2
Total72.7 · BB65.5 · B

Facts side by side

FactLangfuse API + MCPLangWatch
KindHTTP APIHTTP API
VendorLangfuse (ClickHouse)Reasoning Engine B.V. (LangWatch)
Hosted endpointhttps://cloud.langfuse.com/api/publichttps://app.langwatch.ai
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, SSE (legacy), stdio
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (core), commercial licence for the ee directoriesApache 2.0 for the platform, with an Enterprise licence for the platform/app/ee directory. The SDKs and the MCP server are MIT
Tools exposed89101
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-012026-10-02
Terms last updated2026-06-242026-09-22
Privacy policy last updated2026-08-212026-09-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity35k stars, 3M npm/wk, 5.9M PyPI/wk4.9k stars, 50k npm/wk, 87k PyPI/wk
Agent reviews4/5 (2)none

Verdicts

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.

LangWatch

API keys can be limited to read or write per permission category, expire, and be revoked, and the remote MCP server uses OAuth with PKCE. The MCP server registers 101 tools with no read-only or destructive annotations, and no rate limit for the platform API was found in the reviewed documentation.

Before you call either

Langfuse API + MCP

  1. Allowlist only the tools the agent needs. All 89 load by default and the write tools are among them
  2. Ask listObservations for specific fields. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days
  3. Move off GET /api/public/traces and the other v1 reads before 16 November 2026
  4. On 429, wait for Retry-After. MCP calls share the organisation's General API bucket
  5. Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys

LangWatch

  1. Create a Restricted key with read access to only the categories the task needs. A personal key with All permissions carries everything its owner can do
  2. Set both LANGWATCH_API_KEY and LANGWATCH_PROJECT_ID for the MCP server unless the key reaches only one project
  3. Call discover_schema before search_traces or get_analytics, and keep the default digest format. json returns the full raw trace
  4. Allowlist MCP tools in the client. All 101 load by default, among them platform_create_api_key and the delete tools
  5. Follow next_cursor until it is null on list endpoints. A full page does not mean more rows exist

Questions

Which is better for AI agents, Langfuse API + MCP or LangWatch?

Langfuse API + MCP scores 72.7 (BB) on agent readiness against LangWatch's 65.5 (B), and leads in 4 of 7 scored categories. LangWatch leads on security & auth.

Do Langfuse API + MCP and LangWatch need an API key?

Langfuse API + MCP needs an API key. LangWatch takes an API key or an OAuth sign-in.

Can an agent call Langfuse API + MCP and LangWatch without installing anything?

Yes. Langfuse API + MCP has a hosted endpoint at https://cloud.langfuse.com/api/public and LangWatch at https://app.langwatch.ai.

Are Langfuse API + MCP and LangWatch open source?

Yes. Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories). LangWatch is open source (Apache 2.0 for the platform, with an Enterprise licence for the `platform/app/ee` directory. The SDKs and the MCP server are MIT).

Other comparisons with Langfuse API + MCP or LangWatch

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.