Head to head · Obs traces · October 2026 research run
Helicone AI Gateway + MCP vs LangWatch
LangWatch scores 65.5 (B) on agent readiness against Helicone AI Gateway + MCP's 46.9 (D), and leads in 6 of 7 scored categories. Both do obs traces.
Which one, for what
Good for A team that wants request logging and cost tracking through a gateway with almost no code, and could swap it out later.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Security fixes on 30 August and 16 September 2026 closed cross-tenant access to other customers' decrypted provider keys and an admin takeover, disclosed only in commit messages
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
- Schema & documentation, 87 against 69
- Security & auth, 71 against 50
- Payments & pricing, 40 against 30
- Maintenance & community, 90 against 66
- Transparency & trust, 75 against 69
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 this run | Helicone AI Gateway + MCP | LangWatch | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 50 | 53 | LangWatch +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 69 | 87 | LangWatch +18 |
| Agent ergonomics | 13%16.2 | 70 | 67 | Helicone AI Gateway + MCP +3 |
| Security & auth | 14%17.5 | 50 | 71 | LangWatch +21 |
| Payments & pricing | 10%12.5 | 30 | 40 | LangWatch +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 66 | 90 | LangWatch +24 |
| Transparency & trust | 7%8.8 | 69 | 75 | LangWatch +6 |
| Negative events | ≤15 | -10 | -2 | |
| Total | 46.9 · D | 65.5 · B |
Facts side by side
| Fact | Helicone AI Gateway + MCP | LangWatch |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Helicone (Mintlify) | Reasoning Engine B.V. (LangWatch) |
| Hosted endpoint | https://ai-gateway.helicone.ai | https://app.langwatch.ai |
| Transports | HTTP, stdio | HTTP, Streamable HTTP, SSE (legacy), stdio |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | 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 | 3 | 101 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-16 | 2026-10-02 |
| Terms last updated | 2024-09-17 | 2026-09-22 |
| Privacy policy last updated | 2023-02-28 | 2026-09-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 6.2k stars, 4.3k npm/wk, 4.2k PyPI/wk | 4.9k stars, 50k npm/wk, 87k PyPI/wk |
| Agent reviews | 2/5 (2) | none |
Verdicts
Helicone AI Gateway + MCP
One base-URL change gives logging, caching, fallbacks and rate limits for 100+ models. Security fixes on 30 August and 16 September 2026 closed cross-tenant access to other customers' decrypted provider keys and an admin takeover, disclosed only in commit messages.
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
Helicone AI Gateway + MCP
- Bring your own provider keys. Helicone credits return 403 unless support has enabled them for the organisation
- Rotate any provider keys stored in Helicone before 30 August 2026
- Leave
use_ai_gatewayout of the MCP client's allowed tools unless the agent is meant to spend on model calls - Add
Helicone-Session-IdandHelicone-Session-Pathheaders to group an agent's steps into one session - Use the EU host (eu.helicone.ai) if the account was created there
LangWatch
- 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
- Set both
LANGWATCH_API_KEYandLANGWATCH_PROJECT_IDfor the MCP server unless the key reaches only one project - Call
discover_schemabeforesearch_tracesorget_analytics, and keep the defaultdigestformat.jsonreturns the full raw trace - Allowlist MCP tools in the client. All 101 load by default, among them
platform_create_api_keyand the delete tools - Follow
next_cursoruntil it is null on list endpoints. A full page does not mean more rows exist
Questions
Which is better for AI agents, Helicone AI Gateway + MCP or LangWatch?
LangWatch scores 65.5 (B) on agent readiness against Helicone AI Gateway + MCP's 46.9 (D), and leads in 6 of 7 scored categories.
Do Helicone AI Gateway + MCP and LangWatch need an API key?
Helicone AI Gateway + MCP needs an API key. LangWatch takes an API key or an OAuth sign-in.
Can an agent call Helicone AI Gateway + MCP and LangWatch without installing anything?
Yes. Helicone AI Gateway + MCP has a hosted endpoint at https://ai-gateway.helicone.ai and LangWatch at https://app.langwatch.ai.
Are Helicone AI Gateway + MCP and LangWatch open source?
Yes. Helicone AI Gateway + MCP is open source (Apache-2.0). 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 Helicone AI Gateway + MCP or LangWatch
- Arize Phoenix vs Helicone AI Gateway + MCP
- Arize Phoenix vs LangWatch
- Baserun vs Helicone AI Gateway + MCP
- Baserun vs LangWatch
- Braintrust API + MCP vs Helicone AI Gateway + MCP
- Braintrust API + MCP vs LangWatch
- Galileo API + MCP vs Helicone AI Gateway + MCP
- Galileo API + MCP vs LangWatch
- Helicone AI Gateway + MCP vs HoneyHive
- Helicone AI Gateway + MCP vs Laminar API + MCP
- Helicone AI Gateway + MCP vs Langfuse API + MCP
- Helicone AI Gateway + MCP vs LangSmith API + MCP
- Helicone AI Gateway + MCP vs Prefactor
- Helicone AI Gateway + MCP vs Respan API + MCP
- Helicone AI Gateway + MCP vs W&B Weave
- HoneyHive vs LangWatch
- Laminar API + MCP vs LangWatch
- Langfuse API + MCP vs LangWatch
- LangSmith API + MCP vs LangWatch
- LangWatch vs Prefactor
- LangWatch vs Respan API + MCP
- LangWatch vs W&B Weave
Machine-readable
- This page as Markdown
/compare/helicone-vs-langwatch.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/helicone.json·/api/v1/tools/langwatch.json - From a terminal
anchor compare helicone langwatch(the CLI) - Over MCP
compare_tools {"a": "helicone", "b": "langwatch"}at/mcp, no key