Revert "fix(connectors): request Autumn rewards scopes"

Closed
KI
16d ago
+0-2

Reverts #9176.

Why

Autumn checks requested scopes against our stored dynamic client registration (plugin_oauth_clients), which was registered with the old scope list. Since #9176 deployed, every Autumn connect or reconnect redirects back with:

error=invalid_scope
error_description=The following scopes are invalid: rewards:read, rewards:write

Existing connections keep working, but nobody can connect or reconnect Autumn. This restores connects. A follow-up will update the stored registration when a connector's scopes change, then add the scopes back.

šŸ¤– Generated with Claude Code


Summary by cubic

Reverts the Autumn rewards scopes from #9176 so Autumn connects and reconnects work again.

Autumn validates requested scopes against the stored client registration, which still uses the old scope list, so every connect attempt was rejected with invalid_scope for rewards:read and rewards:write. Existing connections were unaffected. The scopes will be re-added once the stored registration is updated to match.

Summary by CodeRabbit

  • Permissions
    • The Autumn MCP connection no longer requests access to read or write rewards data during OAuth authorization. Other connection permissions are unchanged.