docs(mcp): platform-integrator runbook for delegated consent (auth gate)#342
Merged
Merged
Conversation
Add docs/mcp/delegated-consent.md — the operational guide for a managing platform to switch MCP human-in-the-loop consent from DEFER to the #330 auth-required gate. Covers the DEFER-vs-gate distinction, the type: user forge.yaml deploy config, detecting a parked call (task auth-required + mcp_auth_required audit event), and driving resume via authenticated POST /mcp/consent {subject, server, granted} — including the grant-before-resume ordering and the no-token contract. Complements the existing configuration.md concept section (linked, not duplicated); linked from the MCP index Related docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docs/mcp/delegated-consent.md— a platform-integrator runbook for switching MCP human-in-the-loop consent from DEFER to the #330 auth-required gate.Written in response to a platform-team request: "how do we deploy
type: userMCP servers and manage the approvals?" The existing configuration.md gate section covers the concept + config fields; this new doc is the operational how-to for the managing platform (a distinct audience), so it links rather than duplicates.Contents
auth.type: user+ref,platform.token_endpoint,required: false, and the runtime invariants.auth-required, themcp_auth_requiredaudit event (with the real field shape), the 10-minute default deadline.POST /mcp/consent {subject, server, granted}, the 200/404/400/409 codes, the grant-before-granted:trueordering, and the no-token contract.SetConsentDelivererseam for push delivery.SubjectTokenStoreswap for cross-replica grants.Verification
configuration.mdanchor resolve (checked against the filesystem).forge-cli/runtime/mcp_authgate.go,forge-core/types/config.go, andforge-core/auth/middleware.go.