Head to head · Agent harnesses · October 2026 research run
Click vs Warp (Warp Agent CLI and the Oz Agent API)
Warp (Warp Agent CLI and the Oz Agent API) scores 58.8 (C) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories. Click leads on agent ergonomics. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Click D
Best for Product teams that want to embed an agent per customer, ticket or document without running the loop, sandbox or browser themselves, with any model.
Ahead on
- Agent ergonomics, 79 against 66
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Warp (Warp Agent CLI and the Oz Agent API) loses 3 points for them
Watch for
No status page, SLA or public changelog found
Warp (Warp Agent CLI and the Oz Agent API) C
Best for Teams that want one agent across an interactive terminal session and API-started cloud runs, including Claude Code and Codex runs on Warp's infrastructure or their own workers.
Ahead on
- Reliability, 52 against 35
- Schema & documentation, 89 against 84
- Security & auth, 52 against 41
- Payments & pricing, 30 against 15
- Maintenance & community, 84 against 25
- Transparency & trust, 69 against 44
Also in its favour
- Open source
Watch for
The warp CLI has no print or headless mode. Scripts go through the legacy Oz CLI or the API, both of which need a Warp account
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Warp (Warp Agent CLI and the Oz Agent API) +59
Click 25
Closed service with no dated changelog. The newest first-hand date is API version 2026-10-19, 30 days before this check, read as within 90 days rather than within 30 since nothing says what shipped then (20). No dated release entries to count (0). Support is by email to the founder, per the terms. No public changelog, issue tracker or community channel was found (5 of 15). No official SDK (0). No public package or CI to check (0). 20 + 0 + 5 + 0 + 0 = 25.
Warp (Warp Agent CLI and the Oz Agent API) 84
Every dated source of the vendor's own looked for. The weekly changelog (per the 18 October check, not re-read on 4 November) dated release 2026.10.15 (v0.2026.10.14.08.27), 20 days before the check (30). Homebrew's warp-agent-cli cask moved to 0.2026.10.21.08.25.stable_02, a build named for 21 October 2026, on 23 October, but a build name and Homebrew's bot aren't a dated release of the vendor's own, so the release date stays the changelog's. The repository's own release tags and stable branches stop at June 2026. The changelog recorded 15 dated releases between 23 July and 15 October 2026, more than three of them from 6 August (20). Issues and pull requests are public on GitHub. The 18 October counts came through shields.io badges and are struck. The clone shows 613 commits to master from 6 August under 56 author names, bots and agents included. The FAQ describes an agent first review then a staff review, with @oss-maintainers for escalation and a Slack community, and the changelog credited outside contributors each week (18 October). Maintainer reply times are unread (12). Official Python and TypeScript SDKs, released 6 October 2026 as 1.0.0 and 2.0.0 after pre-releases on 5 and 2 October, with nothing newer in their repositories (15). CI on every pull request and a checksummed Homebrew cask, but the install script verifies nothing (7). 30 + 20 + 12 + 15 + 7 = 84.
Transparency & trust Warp (Warp Agent CLI and the Oz Agent API) +25
Click 44
Closed service under terms based on the Common Paper Cloud Service Agreement 2.1, dated 12 October 2026, under Delaware law (15 of 30). The privacy statement lists what is collected, names PostHog with session replay for the website and dashboard, and says staff may access service content for support and to improve the service. Retention is "as long as reasonably needed" with no periods. The docs say Click-created sandboxes are deleted with their session (10 of 30). No deprecation policy. The terms promise 30 days' notice of price changes (3 of 20). Providers are described by category, with PostHog the only one named, and processing in the United States and other countries (5 of 20). 15 + 10 + 3 + 5 = 33.
Warp (Warp Agent CLI and the Oz Agent API) 69
The client, including the warp and oz binaries, is AGPL-3.0, an OSI licence, with the UI crates under MIT. The built-in agent harness, the server and Oz orchestration are proprietary, so the part that runs the agent loop is closed. Judgement call (20). The privacy page says Business and Enterprise are covered by zero data retention, the security overview says ZDR applies across all plans and elsewhere mentions it for Enterprise teams, and the legal security page says it is available on the Enterprise plan. The privacy notice gives criteria rather than retention periods. A subprocessor list and a DPA are linked (15). The Oz CLI carries a legacy notice with a promise of guidance before any support change, and the changelog dates renames such as warp-tui to warp, but there is no written deprecation policy or notice period (8). An exhaustive telemetry event table, Rudderstack and Sentry named, and an opt-out in the app's privacy settings. The CLI pages don't describe what the CLI sends or how to switch it off (14). 20 + 15 + 8 + 14 = 57. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.
Reliability Warp (Warp Agent CLI and the Oz Agent API) +17
Click 35
Hosted lines, for the HTTP API. No status page is linked from the site or the docs (0), so no incident history could be read (5). Concurrent session limits are published per plan (2 on Free, 50 on Pro) with body size limits of 16 MiB, but no request rate limits were found (8 of 15). 429 concurrency_limit_exceeded and the 503 codes are documented, the conventions say to retry 503 after a short wait, and request_id makes submissions safe to retry. No Retry-After header is documented (12 of 15). No SLA in the terms, which leave usage limits to Click's discretion (0). The API carries no beta or preview label (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.
Warp (Warp Agent CLI and the Oz Agent API) 52
Local-package reading, as for the other harnesses, although the FAQ says the agent harness runs on Warp's servers. An install script for macOS and Linux and a PowerShell one for Windows, with supported systems stated (macOS, Linux x64 and Arm64, Windows x64 and Arm64), and a warp-agent-cli cask in Homebrew core that carries a SHA-256. The script itself checks no checksum (18). The repository's Warp CI workflow runs cargo nextest, doc tests, clippy and release-compilation checks on every pull request to master. The repository has 21 workflow files on 4 November. Whether CI passes on the default branch could not be read (15). Issue and pull request counts from the 18 October check came through shields.io badges, a third-party copy of GitHub data this run bars, and are struck. The clone shows 613 commits to master from 6 August. How many open issues are crashes or regressions, and how fast they get replies, could not be read. The weekly changelog records crash fixes in most releases, such as two crash fixes on 7 October 2026 (10). Weekly dated releases with versions such as v0.2026.10.14.08.27 and no breaking-change heading. The binary rename from warp-tui to warp on 23 July 2026 sat under Improvements (4). Version 0.x with date-based numbers. A stable channel is named and the CLI pages carry no beta label (5). Not scored on this reading. Per the 18 October check, not re-read on 4 November, status.warp.dev has components for the agent harness and cloud execution, and logged scheduled cloud agents unavailable for about 2.5 hours on 16 October and session sharing degraded for about 4.75 hours on 30 September 2026. The docs say Warp has no formal SLA. 18 + 15 + 10 + 4 + 5 = 52. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.
Payments & pricing Warp (Warp Agent CLI and the Oz Agent API) +15
Click 15
No x402, MPP or L402. The only 402 is card_verification_required (0). Plan prices are public, Free at $0 and Pro at $199 a month with stated allowances, but no per-unit price (15). The Free plan exists, but writes return 402 until a card is verified in the dashboard (0). A person signs up in a browser, verifies a card and creates the key (0). 0 + 15 + 0 + 0 = 15.
Warp (Warp Agent CLI and the Oz Agent API) 30
Harness reading of the published rubric, scored on the Warp plan the agent needs. No payment protocol (0). Plan prices are public, and Warp-provided inference is billed at public API rates on paid plans, but the agent-hour platform rate and compute rate for cloud runs were not on the pricing page (10). Free is $0 and includes Warp Agent CLI access, but no bundled Warp inference, so the agent runs only with purchased usage or your own provider key. Whether sign-up asks for a card was not tested (10). A person signs in through a browser or device code, and API keys are created by hand in the Oz web app or the Warp app (0). 0 + 10 + 10 + 0 = 20. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Agent ergonomics Click +13
Click 79
Entries can be read by min_entry_id and max_entry_id, get_state returns one snapshot, and lists take limit, so responses stay small (20 of 25). Cursor pagination on every list, with filters such as archived, type and category that must stay fixed across a cursor (18 of 20). Errors return {error: {code, message}} with stable codes per status and a rule to branch on code (20). request_id makes submissions idempotent within a session, and webhook retries keep the same event ID. Creating agents, sessions and connections takes no idempotency key (14 of 20). Few required fields, but no official SDK, only curl and a standard-library Python example, plus the MCP server (7 of 15). 20 + 18 + 20 + 14 + 7 = 79.
Warp (Warp Agent CLI and the Oz Agent API) 66
Harness reading, adapted to a harness driven by a pipeline. MCP servers are attached per run with --mcp or the mcp_servers config, and profiles gate MCP calls, but no per-tool disabling or deferred tool loading was found (12). The API lists runs with limit, cursor, sort_by, state, task_status and name, and returns a normalised conversation and a timeline per run. The warp CLI has no print mode or JSON output and the Oz CLI's run output is described only as printed tool calls (12). RFC 7807 errors with codes such as insufficient_credits and budget_exceeded, a retryable flag, and since 7 October 2026 unattended CLI runs end as blocked instead of hanging when the agent asks for input. No CLI exit codes are documented (16). Follow-ups, interrupts and cancels by run or conversation ID, conversation_id to continue a run, and warp --resume. No idempotency key on run creation (14). Python and TypeScript SDKs with retries and timeouts, but a cloud run needs an environment ID and a Warp account with usage, and the warp CLI itself can't be driven headless (12). 12 + 12 + 16 + 14 + 12 = 66. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.
Security & auth Warp (Warp Agent CLI and the Oz Agent API) +11
Click 41
Platform API keys are revocable, but each has full access to its tenant, including key management. The MCP server's OAuth tokens through WorkOS carry scopes for the MCP endpoint only (20 of 30). Tool grants limit each agent to named tools, and sessions can override grants, but approvals are left to the customer's application and no read-only key was found (8 of 20). Agents read web pages, browser content and MCP results. The docs tell users to keep secrets out of messages and keep MCP tools from returning stored secrets, but give no prompt-injection guidance (3 of 15). Every top-level and nested tool call is recorded and listed per session, and webhook deliveries can be listed (10 of 15). No security.txt (404), disclosure policy or certification found (0). 20 + 8 + 3 + 10 + 0 = 41.
Warp (Warp Agent CLI and the Oz Agent API) 52
Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. The FAQ says the built-in harness runs server-side, so prompts, file contents and command output pass through Warp. The privacy page says AI interactions and console inputs may be collected unless Help improve Warp is off, and the security overview says data collection is on by default for Free and paid teams and off on Business and Enterprise. The opt-out is documented in the desktop app's settings, not for the CLI. Personal and agent keys can expire after 1, 30 or 90 days, and provider keys stay in the device's secure storage (14). Per-action permissions with always_ask, agent_decides and always_allow, edits always shown as a diff under agent_decides, a default denylist and child agents asking first. Auto-approve bypasses the user's denylist by default, and no local OS sandbox is documented. Cloud runs use a Docker sandbox as a non-root user with passwordless sudo (11). No prompt-injection guidance was found in the CLI, platform or factory pages read, and secret redaction is off by default (4). Cloud runs record transcripts, tool calls and logs, the API returns timelines and conversations, the app has a Network Log, and the Enterprise Analytics API can filter tool calls for audit (11). SECURITY.md names security@warp.dev and private GitHub advisories, SOC 2 Type II is stated with a trust centre and a subprocessor list. No security.txt and no bug bounty were found, and the GitHub advisory list was not read (12). 14 + 11 + 4 + 11 + 12 = 52. Warp's terms bar any robot, scraper or other automated means to access its Services, so this run pauses its hosts and the readings from warp.dev pages are per the 18 October check, not re-read on 4 November.
Score by category
| Category | Weight | Click | Warp (Warp Agent CLI and the Oz Agent API) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 52 | Warp (Warp Agent CLI and the Oz Agent API) +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 89 | Warp (Warp Agent CLI and the Oz Agent API) +5 |
| Agent ergonomics | 13% | 79 | 66 | Click +13 |
| Security & auth | 14% | 41 | 52 | Warp (Warp Agent CLI and the Oz Agent API) +11 |
| Payments & pricing | 10% | 15 | 30 | Warp (Warp Agent CLI and the Oz Agent API) +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 84 | Warp (Warp Agent CLI and the Oz Agent API) +59 |
| Transparency & trust | 7% | 44 | 69 | Warp (Warp Agent CLI and the Oz Agent API) +25 |
| Negative events | ≤15 | 0 | -3 | |
| Total | D 48.6/100 | C 58.8/100 |
Facts side by side
| Fact | Click | Warp (Warp Agent CLI and the Oz Agent API) |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | Warp |
| Hosted endpoint | https://api.useclick.ai/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 | Mixed. The client, including the warp and oz binaries, is AGPL-3.0 with the warpui_core and warpui crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0 |
| Tools exposed | 23 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-10-15 |
| Terms last updated | 2026-10-12 | 2025-10-07 |
| Privacy policy last updated | 2026-10-12 | 2026-08-18 |
| 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 | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | none | 3.3/5 (4) |
How the scores have moved
Verdicts
Click
Click's API is described by a public OpenAPI 3.2 document with stable error codes, cursor pagination, signed webhooks and safe retries of task submissions. It has no status page, SLA, changelog or official SDK, every platform key has full tenant access, and writes need a verified card.
Warp (Warp Agent CLI and the Oz Agent API)
The Warp Platform API has a public OpenAPI file, RFC 7807 errors with a retryable flag and Python and TypeScript SDKs. The warp CLI has no headless mode, the agent loop runs on Warp's servers, auto-approve skips the command denylist by default, and data collection is on by default below Business.
Before you call either
Click
- Send a unique
request_idwith each submission and reuse it when you retry, so a task doesn't run twice - Branch on
error.code, not the message. Retry 503 codes after a short wait - If you get
429 concurrency_limit_exceeded, put an idle session in standby to free its slot - Read a submission until it is
done,cancelledorfailed, then fetch the answer entry it names - Grant each agent only the tools it needs. Approvals and budgets are left to your application
Warp (Warp Agent CLI and the Oz Agent API)
- For unattended work, call
POST https://app.warp.dev/api/v1/agent/runswithAuthorization: Bearer $WARP_API_KEY. ThewarpCLI is interactive only - Use an agent key, scoped to one cloud agent and given an expiry, for CI rather than a personal key. Keys are created in the Oz web app or the Warp app
- Set
auto_approve_bypasses_command_denylist = falseunder[agents.warp_agent.other]before startingwarp --auto-approve - Read
codeandretryablein error bodies. A 429resource_unavailablemeans capacity is full and the platform retries the task itself - Pin a version with
WARP_TUI_VERSIONat install, or setgeneral.autoupdate_enabled = false, because script installs update themselves in the background
Questions
Which is better for AI agents, Click or Warp (Warp Agent CLI and the Oz Agent API)?
Warp (Warp Agent CLI and the Oz Agent API) scores 58.8 (C) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories. Click leads on agent ergonomics.
Can an agent call Click and Warp (Warp Agent CLI and the Oz Agent API) without installing anything?
Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for Warp (Warp Agent CLI and the Oz Agent API).
Are Click and Warp (Warp Agent CLI and the Oz Agent API) open source?
No open-source release is listed for Click. Warp (Warp Agent CLI and the Oz Agent API) is open source (Mixed. The client, including the `warp` and `oz` binaries, is AGPL-3.0 with the `warpui_core` and `warpui` crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0).
Other comparisons with Click or Warp (Warp Agent CLI and the Oz Agent API)
- Agent Zero vs Click
- Agent Zero vs Warp (Warp Agent CLI and the Oz Agent API)
- Aider vs Click
- Aider vs Warp (Warp Agent CLI and the Oz Agent API)
- Amp vs Click
- Amp vs Warp (Warp Agent CLI and the Oz Agent API)
- Antigravity CLI vs Click
- Antigravity CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Auggie CLI vs Click
- Auggie CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- AXLR vs Click
- AXLR vs Warp (Warp Agent CLI and the Oz Agent API)
- boxes.dev vs Click
- boxes.dev vs Warp (Warp Agent CLI and the Oz Agent API)
- Claude Code vs Click
- Claude Code vs Warp (Warp Agent CLI and the Oz Agent API)
- Click vs Cline
- Click vs Conductor
- Click vs Crush
- Click vs Cursor CLI
- Click vs DeepSeek Harness (dsh)
- Click vs dsh-superagent (DeepSeek)
- Click vs Devin
- Click vs Droid CLI
- Click vs Pi
- Click vs Emdash
- Click vs Friday
- Click vs Gemini CLI
- Click vs GitHub Copilot CLI
- Click vs goose
- Click vs Harness²
- Click vs HarnessRouter
- Click vs Jules
- Click vs Junie CLI
- Click vs Kilo Code CLI
- Click vs Kimi Code CLI
- Click vs Kiro CLI
- Click vs Letta
- Click vs mini-swe-agent
- Click vs MiniMax Code
- Click vs Mistral Vibe CLI
- Click vs Muse Code
- Click vs OpenAI Agents API
- Click vs OpenAI Codex
- Click vs OpenCode
- Click vs OpenHands
- Click vs OpenMausBot
- Click vs Orca
- Click vs Paseo
- Click vs Prime Agent
- Click vs Qoder CLI
- Click vs Qwen Code
- Click vs Mirror CLI
- Click vs Rovo Dev CLI
- Click vs Sculptor
- Click vs T3 Code
- Click vs Traycer
- Click vs Unstoppable
- Click vs Verdent
- Click vs Vibe-Trading
- Cline vs Warp (Warp Agent CLI and the Oz Agent API)
- Conductor vs Warp (Warp Agent CLI and the Oz Agent API)
- Crush vs Warp (Warp Agent CLI and the Oz Agent API)
- Cursor CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- DeepSeek Harness (dsh) vs Warp (Warp Agent CLI and the Oz Agent API)
- dsh-superagent (DeepSeek) vs Warp (Warp Agent CLI and the Oz Agent API)
- Devin vs Warp (Warp Agent CLI and the Oz Agent API)
- Droid CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Pi vs Warp (Warp Agent CLI and the Oz Agent API)
- Emdash vs Warp (Warp Agent CLI and the Oz Agent API)
- Gemini CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- GitHub Copilot CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- goose vs Warp (Warp Agent CLI and the Oz Agent API)
- Harness² vs Warp (Warp Agent CLI and the Oz Agent API)
- HarnessRouter vs Warp (Warp Agent CLI and the Oz Agent API)
- Jules vs Warp (Warp Agent CLI and the Oz Agent API)
- Junie CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Kilo Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Kimi Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Letta vs Warp (Warp Agent CLI and the Oz Agent API)
- mini-swe-agent vs Warp (Warp Agent CLI and the Oz Agent API)
- MiniMax Code vs Warp (Warp Agent CLI and the Oz Agent API)
- Mistral Vibe CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Muse Code vs Warp (Warp Agent CLI and the Oz Agent API)
- OpenAI Agents API vs Warp (Warp Agent CLI and the Oz Agent API)
- OpenAI Codex vs Warp (Warp Agent CLI and the Oz Agent API)
- OpenCode vs Warp (Warp Agent CLI and the Oz Agent API)
- OpenHands vs Warp (Warp Agent CLI and the Oz Agent API)
- Orca vs Warp (Warp Agent CLI and the Oz Agent API)
- Paseo vs Warp (Warp Agent CLI and the Oz Agent API)
- Prime Agent vs Warp (Warp Agent CLI and the Oz Agent API)
- Qoder CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Qwen Code vs Warp (Warp Agent CLI and the Oz Agent API)
- Mirror CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Rovo Dev CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Sculptor vs Warp (Warp Agent CLI and the Oz Agent API)
- T3 Code vs Warp (Warp Agent CLI and the Oz Agent API)
- Traycer vs Warp (Warp Agent CLI and the Oz Agent API)
- Verdent vs Warp (Warp Agent CLI and the Oz Agent API)
- Vibe-Trading vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Warp (Warp Agent CLI and the Oz Agent API)
- Clawboo vs Warp (Warp Agent CLI and the Oz Agent API)
- CLI Manager vs Warp (Warp Agent CLI and the Oz Agent API)
- Friday vs Warp (Warp Agent CLI and the Oz Agent API)
- Harness vs Warp (Warp Agent CLI and the Oz Agent API)
- herdr vs Warp (Warp Agent CLI and the Oz Agent API)
- OpenMausBot vs Warp (Warp Agent CLI and the Oz Agent API)
- Paperclip vs Warp (Warp Agent CLI and the Oz Agent API)
- Parallax vs Warp (Warp Agent CLI and the Oz Agent API)
- Unstoppable vs Warp (Warp Agent CLI and the Oz Agent API)
Machine-readable
- This page as Markdown
/compare/click-agents-vs-warp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/warp.json - From a terminal
anchor compare click-agents warp(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "warp"}at/mcp, no key