Repository navigation
chore(mcp-compat): explain MCP consent flow (backend b422749..042aab7) - #30
Open
ditto-mcp-maintainer[bot] wants to merge 1 commit into
Open
ditto-mcp-maintainer[bot] wants to merge 1 commit into
ditto-mcp-maintainer[bot] wants to merge 1 commit into
Conversation
Author
|
Please regenerate/update |
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
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.
Why
Backend MCP tool/protocol change in ditto-assistant/backend@042aab7 (range b422749..042aab7) requires this repo to stay compatible.
Triggering backend change
The MCP now enforces Terms and AI-processing consent and registers consent_status/request_consent for an account owner to accept.
What changed here
Provenance
Opened by the Ditto MCP-extensions maintenance automation. Run state and prior runs live in the dedicated mcp-extensions-maintainer knowledge graph and ditto-assistant/ditto-backend-ops-log ledger. A separate reviewer agent will review this PR with fresh context.
Setup / migration notes
None.