Feature request · Permissions & security · Blocks work
Offer MCP write scopes on the initial consent screen
1 source thread · first seen 2026-09
Summary
The initial OAuth challenge lists only baseline scopes, leaving some write permissions unavailable when a client loses the step-up challenge. The requester wants all optional MCP scopes offered up front, or an admin setting to enable that behavior.
- Affects
- MCP users connecting through OAuth clients
- Workaround
- Reconnect and rely on the client to carry the scope from a 403 insufficient_scope challenge; this does not work for the reported client flow.
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“users can't grant write access at all”