RFC: deliver molecule-platform-mcp as an entitlement-gated MCP plugin (retire the special concierge image) #3045
Reference in New Issue
Block a user
Delete Branch "rfc/platform-mcp-as-plugin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Draft RFC for CTO sign-off. Routes the concierge's management MCP through the working plugin channel (existing
MCPServerAdaptor, issue #847) instead of the broken asset/baked-image channel.Why: the concierge is currently vanilla Claude Code in prod — generic system prompt, only the
a2aMCP, nocreate_workspace. Root cause: the on-box config is a 218-byte CP-regenerated stub with noprompt_files/mcp_servers; the asset channel never lands the identity. The plugin channel (which deliversseo-allskills) works.Proposal:
molecule-platform-mcpbecomes an entitlement-gated MCP-server plugin declared by the platform-agent template;npx @molecule-ai/mcp-serverlaunched viasettings-fragment.json→ no baked image needed. Org-admin token stays core-injected (referenced, never embedded). Privilege gating (org-root only) is load-bearing.Full doc:
docs/design/rfc-platform-mcp-as-plugin.md. Open questions for CTO in §6. Arch + entitlement change → CTO sign-off requested before building.🤖 Generated with Claude Code
APPROVED. 5-axis review on head
7e8e1779.Correctness: as an RFC, the document accurately frames the observed concierge failure mode, separates the plugin-delivery proposal from orthogonal provider-pin/config-stub work, and explicitly marks CTO sign-off/open questions before implementation.
Robustness/security: the load-bearing security constraint is clearly stated: molecule-platform-mcp must be org-root/kind=platform only, the org-admin token remains core-injected and referenced rather than embedded, and privileged-plugin install should be audited. The RFC does not pretend this is safe without that entitlement gate.
Performance/readability: it calls out the
npxcold-start tradeoff as an open CTO question, and the rollout/non-goals are readable enough for architecture review. No runtime code changes are introduced.CI note: CI / all-required is green; remaining failures are review/SOP gate bookkeeping.
APPROVED on current head
7e8e1779. Genuine review: this is a draft RFC/design document only, adding docs/design/rfc-platform-mcp-as-plugin.md; no runtime code, workflow, or entitlement implementation changes. The RFC clearly states it needs CTO sign-off before implementation, identifies the production concierge MCP delivery failure, proposes plugin-channel delivery via existing MCPServerAdaptor, and calls out the load-bearing org-root entitlement/secret-separation constraints plus open CTO questions. Security/robustness concerns are explicitly framed as requirements rather than silently implemented. Performance/readability: no code path impact; document is clear and scoped.