Skip to content

chore(mcp-compat): explain MCP consent flow (backend b422749..042aab7) - #30

Open
ditto-mcp-maintainer[bot] wants to merge 1 commit into
mainfrom
mcp-maintenance/terms-consent-042aab7
Open

ditto-mcp-maintainer[bot] wants to merge 1 commit into
mainfrom
mcp-maintenance/terms-consent-042aab7

Conversation

@ditto-mcp-maintainer

Copy link
Copy Markdown

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

  • Explain that the plugin should use consent_status/request_consent to relay an owner consent link and wait for acceptance.
  • Preserve the plugin's MCP-only auth path; do not require CLI installation.

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.

@ditto-mcp-maintainer

Copy link
Copy Markdown
Author

Please regenerate/update plugins/ditto/shared-skills.lock.json and any source/generated artifacts using the documented shared-skills workflow. The edited generated plugins/ditto/skills/ditto-memory/SKILL.md no longer matches the recorded hashes; validate fails at scripts/shared_skills.py verify --host plugins --repo . with Generated skill or generator differs from recorded hashes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants