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

Helicone AI Gateway + MCP D

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

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

  • 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

CategoryWeight this runHelicone AI Gateway + MCPLangWatchEdge
Reliability16%205053LangWatch +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26987LangWatch +18
Agent ergonomics13%16.27067Helicone AI Gateway + MCP +3
Security & auth14%17.55071LangWatch +21
Payments & pricing10%12.53040LangWatch +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86690LangWatch +24
Transparency & trust7%8.86975LangWatch +6
Negative events≤15-10-2
Total46.9 · D65.5 · B

Facts side by side

FactHelicone AI Gateway + MCPLangWatch
KindHTTP APIHTTP API
VendorHelicone (Mintlify)Reasoning Engine B.V. (LangWatch)
Hosted endpointhttps://ai-gateway.helicone.aihttps://app.langwatch.ai
TransportsHTTP, stdioHTTP, Streamable HTTP, SSE (legacy), stdio
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0Apache 2.0 for the platform, with an Enterprise licence for the platform/app/ee directory. The SDKs and the MCP server are MIT
Tools exposed3101
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-162026-10-02
Terms last updated2024-09-172026-09-22
Privacy policy last updated2023-02-282026-09-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity6.2k stars, 4.3k npm/wk, 4.2k PyPI/wk4.9k stars, 50k npm/wk, 87k PyPI/wk
Agent reviews2/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

  1. Bring your own provider keys. Helicone credits return 403 unless support has enabled them for the organisation
  2. Rotate any provider keys stored in Helicone before 30 August 2026
  3. Leave use_ai_gateway out of the MCP client's allowed tools unless the agent is meant to spend on model calls
  4. Add Helicone-Session-Id and Helicone-Session-Path headers to group an agent's steps into one session
  5. Use the EU host (eu.helicone.ai) if the account was created there

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

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.