MCP OAuth consent

Route: /mcp-auth?txn=<uuid>

Scenario: You ran claude mcp login mushi (or Cursor / VS Code MCP auth). The hosted MCP redirected your browser here to approve access.

OAuth consent for MCP clients (MCP auth spec):

1. Hosted MCP /oauth/authorize records a pending transaction and 302s here.
2. Page loads GET /v1/mcp-oauth/request?txn=… — client name + requested access.
3. Pick a project (owner/admin) → Approve.
4. POST /v1/mcp-oauth/approve mints a revocable mcp-oauth API key and redirects to the client callback with the authorization code.

Sibling flow for the CLI: CLI device auth (mushi login).

Related pages

• MCP — tool catalogue and deeplink install
• Connect hub — one-click MCP lane without OAuth
• CLI device auth — terminal login approval