Lowcountry_Digital_WorksQ: Can MCP OAuth be limited to read-only/per-resource scopes without offline access?
During our integration testing, the live MCP/OAuth path exposed broader/coarser authorization behavior than we expected from the published granular-scope model. For an agent that only needs to list/read forms or submissions, can the live connection request only those exact read scopes and omit offline access? If granular least-privilege scopes are supported now, could you publish a current example for ChatGPT/Codex/Cursor showing the expected consent screen and revoke path?
Jake_Dashform
Oct 21, 2026A: Thank you for testing this carefully and calling out the mismatch.
The current live MCP connection uses a broader “mcp” scope. It does not yet provide the granular, resource-specific read-only authorization you described. The published documentation should make that limitation clearer.
Offline access is a separate permission for maintaining access through refresh tokens. Our configuration does not include it in the default registration scope, but we still need to verify the complete authorization behavior in each client before promising an end-to-end connection without it.
We plan to complete the related MCP authorization improvements by the end of October. The goal is to let read-only workflows request only the permissions they need, with write access and offline access requested separately when needed.
As part of that release, we will publish tested examples for ChatGPT, Codex, and Cursor covering the requested scopes, resource boundaries, expected consent screen, and revocation steps. We will also document any client-specific limitations.
Until those changes are live and verified, please do not treat the current MCP grant as a narrowly scoped read-only connection.
Thank you again. Your feedback gives us a clear standard to build and test against.