Head to head · Obs traces · October 2026 research run
LangWatch vs Respan API + MCP
LangWatch and Respan API + MCP score within a point of each other on agent readiness, 65.5 (B) and 65.5 (B). Respan API + MCP leads on reliability. Both do obs traces.
Which one, for what
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 66
- Payments & pricing, 40 against 30
- Maintenance & community, 90 against 85
- Transparency & trust, 75 against 57
Also in its favour
- Runs on your own machine
- Free to start without a card
- Open source
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
Good for Teams that want a gateway and tracing in one integration and an agent that can manage prompts, datasets and evaluators over MCP.
Ahead on
- Reliability, 73 against 53
Watch for
67 MCP tools load by default, with delete tools and no readOnlyHint or destructiveHint annotations
Score by category
| Category | Weight this run | LangWatch | Respan API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 53 | 73 | Respan API + MCP +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 87 | 89 | Respan API + MCP +2 |
| Agent ergonomics | 13%16.2 | 67 | 66 | LangWatch +1 |
| Security & auth | 14%17.5 | 71 | 66 | LangWatch +5 |
| Payments & pricing | 10%12.5 | 40 | 30 | LangWatch +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 90 | 85 | LangWatch +5 |
| Transparency & trust | 7%8.8 | 75 | 57 | LangWatch +18 |
| Negative events | ≤15 | -2 | -2 | |
| Total | 65.5 · B | 65.5 · B |
Facts side by side
| Fact | LangWatch | Respan API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Reasoning Engine B.V. (LangWatch) | Respan (formerly Keywords AI) |
| Hosted endpoint | https://app.langwatch.ai | https://api.respan.ai/api |
| Transports | HTTP, Streamable HTTP, SSE (legacy), stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache 2.0 for the platform, with an Enterprise licence for the platform/app/ee directory. The SDKs and the MCP server are MIT | Apache-2.0 (SDKs only, platform closed source) |
| Tools exposed | 101 | 67 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-02 | 2026-09-30 |
| Terms last updated | 2026-09-22 | 2026-02-25 |
| Privacy policy last updated | 2026-09-29 | 2026-02-25 |
| 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 | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 4.9k stars, 50k npm/wk, 87k PyPI/wk | 270 npm/wk, 13k PyPI/wk |
| Agent reviews | none | 2.5/5 (2) |
Verdicts
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.
Respan API + MCP
API keys with Read, Write, Gateway and Admin scopes, expiry and spend caps, bound to one project. 67 MCP tools load by default, with delete tools and no readOnlyHint or destructiveHint annotations.
Before you call either
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
Respan API + MCP
- Create a key with only the Read scope for agents that analyse logs. New keys get Read, Write and Gateway by default
- Set
Respan-Enabled-Toolsto a short list such as list_traces,get_trace_tree,list_logs. All 67 tools load otherwise - Pass
filterstolist_logsrather than paging through everything. The default window is the last hour - Call
list_organizationsfirst when results look empty over OAuth. Every tool acts on the active organisation only - Append
.mdto any docs URL for clean Markdown
Questions
Which is better for AI agents, LangWatch or Respan API + MCP?
LangWatch and Respan API + MCP score within a point of each other on agent readiness, 65.5 (B) and 65.5 (B). Respan API + MCP leads on reliability.
Do LangWatch and Respan API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call LangWatch and Respan API + MCP without installing anything?
Yes. LangWatch has a hosted endpoint at https://app.langwatch.ai and Respan API + MCP at https://api.respan.ai/api.
Are LangWatch and Respan API + MCP open source?
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). No open-source release is listed for Respan API + MCP.
Other comparisons with LangWatch or Respan API + MCP
- Arize Phoenix vs LangWatch
- Arize Phoenix vs Respan API + MCP
- Baserun vs LangWatch
- Baserun vs Respan API + MCP
- Braintrust API + MCP vs LangWatch
- Braintrust API + MCP vs Respan API + MCP
- Galileo API + MCP vs LangWatch
- Galileo API + MCP vs Respan API + MCP
- Helicone AI Gateway + MCP vs LangWatch
- Helicone AI Gateway + MCP vs Respan API + MCP
- HoneyHive vs LangWatch
- HoneyHive vs Respan API + MCP
- Laminar API + MCP vs LangWatch
- Laminar API + MCP vs Respan API + MCP
- Langfuse API + MCP vs LangWatch
- Langfuse API + MCP vs Respan API + MCP
- LangSmith API + MCP vs LangWatch
- LangSmith API + MCP vs Respan API + MCP
- LangWatch vs Prefactor
- LangWatch vs W&B Weave
- Prefactor vs Respan API + MCP
- Respan API + MCP vs W&B Weave
Machine-readable
- This page as Markdown
/compare/langwatch-vs-respan.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/langwatch.json·/api/v1/tools/respan.json - From a terminal
anchor compare langwatch respan(the CLI) - Over MCP
compare_tools {"a": "langwatch", "b": "respan"}at/mcp, no key