# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/langfuse-vs-langwatch
- Markdown: https://www.anchorterminal.com/compare/langfuse-vs-langwatch.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/langfuse-vs-langwatch.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/langfuse-vs-langwatch.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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.

- Langfuse API + MCP: grade BB, 72.7/100, rank #98 of 842. Markdown https://www.anchorterminal.com/tools/langfuse.md · JSON https://www.anchorterminal.com/api/v1/tools/langfuse.json
- LangWatch: grade B, 65.5/100, rank #291 of 842. Markdown https://www.anchorterminal.com/tools/langwatch.md · JSON https://www.anchorterminal.com/api/v1/tools/langwatch.json

## 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

| Category | Weight | Langfuse API + MCP | LangWatch | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 53 | Langfuse API + MCP +27 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 93 | 87 | Langfuse API + MCP +6 |
| Agent ergonomics | 13% (16.2 this run) | 74 | 67 | Langfuse API + MCP +7 |
| Security & auth | 14% (17.5 this run) | 65 | 71 | LangWatch +6 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 88 | 90 | LangWatch +2 |
| Transparency & trust | 7% (8.8 this run) | 85 | 75 | Langfuse API + MCP +10 |
| Negative events | ≤15 | -2 | -2 | |
| **Total** | | **72.7 · BB** | **65.5 · B** | |

## Facts side by side

| Fact | Langfuse API + MCP | LangWatch |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Langfuse (ClickHouse) | Reasoning Engine B.V. (LangWatch) |
| Hosted endpoint | `https://cloud.langfuse.com/api/public` | `https://app.langwatch.ai` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, SSE (legacy), stdio |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (core), commercial licence for the ee directories | Apache 2.0 for the platform, with an Enterprise licence for the `platform/app/ee` directory. The SDKs and the MCP server are MIT |
| Tools exposed | 89 | 101 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-01 | 2026-10-02 |
| Terms last updated | 2026-06-24 | 2026-09-22 |
| Privacy policy last updated | 2026-08-21 | 2026-09-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| 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 | 4.9k stars, 50k npm/wk, 87k PyPI/wk |
| Agent reviews | 4/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).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/langfuse-vs-langwatch.json, and with the fewest tokens: https://www.anchorterminal.com/compare/langfuse-vs-langwatch.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "langfuse", "b": "langwatch"}`. From a terminal: `anchor compare langfuse langwatch`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/langfuse.json and https://www.anchorterminal.com/api/v1/tools/langwatch.json

## Other comparisons with Langfuse API + MCP or LangWatch

- [Arize Phoenix vs Langfuse API + MCP](https://www.anchorterminal.com/compare/arize-phoenix-vs-langfuse.md)
- [Arize Phoenix vs LangWatch](https://www.anchorterminal.com/compare/arize-phoenix-vs-langwatch.md)
- [Baserun vs Langfuse API + MCP](https://www.anchorterminal.com/compare/baserun-vs-langfuse.md)
- [Baserun vs LangWatch](https://www.anchorterminal.com/compare/baserun-vs-langwatch.md)
- [Braintrust API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/braintrust-vs-langfuse.md)
- [Braintrust API + MCP vs LangWatch](https://www.anchorterminal.com/compare/braintrust-vs-langwatch.md)
- [Galileo API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/galileo-vs-langfuse.md)
- [Galileo API + MCP vs LangWatch](https://www.anchorterminal.com/compare/galileo-vs-langwatch.md)
- [Helicone AI Gateway + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/helicone-vs-langfuse.md)
- [Helicone AI Gateway + MCP vs LangWatch](https://www.anchorterminal.com/compare/helicone-vs-langwatch.md)
- [HoneyHive vs Langfuse API + MCP](https://www.anchorterminal.com/compare/honeyhive-vs-langfuse.md)
- [HoneyHive vs LangWatch](https://www.anchorterminal.com/compare/honeyhive-vs-langwatch.md)
- [Laminar API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/laminar-vs-langfuse.md)
- [Laminar API + MCP vs LangWatch](https://www.anchorterminal.com/compare/laminar-vs-langwatch.md)
- [Langfuse API + MCP vs LangSmith API + MCP](https://www.anchorterminal.com/compare/langfuse-vs-langsmith.md)
- [Langfuse API + MCP vs Prefactor](https://www.anchorterminal.com/compare/langfuse-vs-prefactor.md)
- [Langfuse API + MCP vs Respan API + MCP](https://www.anchorterminal.com/compare/langfuse-vs-respan.md)
- [Langfuse API + MCP vs W&B Weave](https://www.anchorterminal.com/compare/langfuse-vs-wandb-weave.md)
- [LangSmith API + MCP vs LangWatch](https://www.anchorterminal.com/compare/langsmith-vs-langwatch.md)
- [LangWatch vs Prefactor](https://www.anchorterminal.com/compare/langwatch-vs-prefactor.md)
- [LangWatch vs Respan API + MCP](https://www.anchorterminal.com/compare/langwatch-vs-respan.md)
- [LangWatch vs W&B Weave](https://www.anchorterminal.com/compare/langwatch-vs-wandb-weave.md)