fix(auth-transport): forward authenticated users, skip per-tool checks

[vibegui]

Summary

• Authenticated users (browser session or MCP OAuth) are forwarded directly to downstream MCP servers
• Per-tool AccessControl checks are preserved only for API keys
• Fixes "Access denied" when Claude Code CLI calls tools through Mesh connections

The Problem

AuthTransport.authorizeToolCall() ran per-tool permission checks for ALL callers, including authenticated users. For MCP OAuth sessions (Claude Code CLI), the org context wasn't properly resolved, causing AccessControl to deny access.

The Fix

If the caller has a user.id (authenticated via browser session or MCP OAuth), just forward the call — the downstream MCP server handles its own auth. Only run granular AccessControl checks for API keys, where fine-grained permissions are the expected model.

+    // Authenticated users are forwarded directly.
+    // Granular per-tool permission checks only apply to API keys.
+    if (ctx.auth.user?.id && !ctx.auth.apiKey?.id) {
+      return;
+    }

Test plan

• Claude Code CLI can call tools on MCP connections without "Access denied"
• Browser session tool calls continue to work
• API keys with granular permissions still enforce per-tool checks
• Unauthenticated requests still get "Authentication required" error

🤖 Generated with Claude Code

---

Summary by cubic

Authenticated users are now forwarded directly to downstream MCP servers; per-tool checks only run for API keys. Fixes "Access denied" for Claude Code CLI via MCP OAuth over Mesh.

• Bug Fixes
  • Skip per-tool AccessControl when a user.id is present and no API key is used.
  • Keep granular per-tool checks for API keys using apiKey.userId.
  • Unauthenticated requests still return "Authentication required".

^{Written for commit 54d330b. Summary will update on new commits.}

[github-actions]

🧪 Benchmark

Should we run the Virtual MCP strategy benchmark for this PR?

React with 👍 to run the benchmark.

Reaction	Action
👍	Run quick benchmark (10 & 128 tools)

Benchmark will run on the next push after you react.

[github-actions]

Release Options

Should a new version be published when this PR is merged?

React with an emoji to vote on the release type:

Reaction	Type	Next Version
👍	Prerelease	2.187.1-alpha.1
🎉	Patch	2.187.1
❤️	Minor	2.188.0
🚀	Major	3.0.0

Current version: 2.187.0

Deployment

• Deploy to production (triggers ArgoCD sync after Docker image is published)

[cubic-dev-ai]

No issues found across 1 file