Claude Design first-party MCP always 403s: transport never attaches design-scoped token, `claude mcp login` OAuth flow is dead, and the error message suggests a nonexistent `/design-login` command
Status Open
Maintainer reply None cached
Activity 11 comments · opened Sep 4, 2026
Environment:
- Claude Code v2.1.261 (latest at time of filing), macOS (Darwin 24.6.0)
- claude.ai Max account with confirmed Claude Design access (web UI works; the MCP itself worked from this machine in early July 2026)
- Server config (user scope):
"claude-design": {"type": "http", "url": "https://api.anthropic.com/v1/design/mcp"}
Symptom:
Connection fails every session with:
FIRST_PARTY_AUTH_REJECTED: api.anthropic.com rejected your claude.ai login for Claude Design (HTTP 403) ... Run /design-login and retry
What I verified:
/design-login— the command the error message recommends — does not exist ("command not found"). Phantom command.- My
claudeAiOauthtoken scopes are[file_upload, inference, mcp_servers, profile, sessions:claude_code]. The server's liveWWW-Authenticateheader demandsscope="user:design:read user:design:write". The standard/loginflow never requests design scopes, and the MCP HTTP transport never attaches any other credential → 403 is guaranteed. (Same root cause as closed issue #69317.) claude mcp login claude-designcannot mint the missing token: the flow hits a decommissioned /authorize endpoint (HTTP 410) and hangs. (Same as closed issue #77620.) The resource metadata athttps://api.anthropic.com/v1/design/.well-known/oauth-protected-resourceadvertiseshttps://claude.ai/v1/design/mcpas the authorization server, but that server publishes no validoauth-authorization-servermetadata (404), so RFC 9728 discovery dead-ends too.- Ruled out local causes: single config scope, no duplicate/shadowed entries, endpoint alive (405/401 on unauthenticated probes), latest CLI, entitled account.
Ask:
Both prior issues (#69317, #77620) were closed without a fix, but the failure is fully reproducible and self-consistent: no token with design scopes can be obtained, and no design-scoped token would be attached if it existed. Please either (a) fix the OAuth flow + token attachment for the claude-design first-party server, or (b) remove the server type and the /design-login suggestion from the error copy so users stop chasing a nonexistent command.
Showing cached comments. Read the full discussion on GitHub ↗
3 Comments
Did you manage to find any solution for this ?
No solution yet. The issue is still fully reproducible on our end — the OAuth flow for Claude Design remains broken as described. We're waiting on Anthropic to fix the token scoping or the
/design-logincommand.same issue,
There seems to be no way to let claude code in the desktop pull a design from claude design direclty.