Implementation: Session 60.2: How to enable external access to Cloud MCP for...
Documentation for Sessions
⚙️ Implementation: Session 60.2: How to enable external access to Cloud MCP for...
Date: 2026-01-23
Time: 00:00:46 UTC
Session: editor2-60.4
Agent: backend
Confidence: 95%
Status: ✅ Documented
📋 Decision Context
Question:
Session 60.2: How to enable external access to Cloud MCP for Claude Cowork?
Task: Not specified
🎯 Decision Made
Chosen:
Add JwtOrApiKeyGuard to tool-calling endpoints
Options Considered:
- No alternatives documented
💭 Reasoning
API Key authentication was already implemented (ProjectApiKeyGuard, JwtOrApiKeyGuard) in Session 59.1 but not wired to endpoints. Changed mcp-gateway.controller.ts: (1) Removed class-level @UseGuards(JwtAuthGuard), (2) Added @UseGuards(JwtOrApiKeyGuard) to tools, tools/call, preflight, usage endpoints, (3) Kept @UseGuards(JwtAuthGuard) on project management endpoints (create/list/update require login). This allows external projects to authenticate with X-MCP-API-Key + X-MCP-Project-Id headers.
📁 Files Involved
apis/backend-ai-api/src/app/mcp-gateway/mcp-gateway.controller.tsapis/backend-ai-api/src/app/mcp-gateway/guards/project-api-key.guard.ts
🔗 Related
- Decision ID:
dev_1769126443252_6bzd057 - Session: 60
- Workspace: editor2
Auto-generated by MCP Smart Consolidation