SSOT: align TS admin MCP schemas/client with base MCP contract #21
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Parent: internal#638. Related: internal#598.\n\nThe TS admin MCP server has its own platform client, global PLATFORM_URL, and tool schema surface. internal#598 covers delegate_task schema drift; this ticket covers the broader base-contract alignment.\n\nScope:\n- Consume or generate from canonical MCP schema bundle instead of hand-maintaining universal Molecule tool schemas.\n- Align delegate/delegation naming and parameter semantics per internal#598.\n- Add tests for target/platform URL handling where tools operate on external/multi-platform workspaces.\n- Add drift gate for schema bundle changes.\n\nAcceptance:\n- Universal Molecule MCP schema is generated or imported from the canonical owner.\n- Deprecated aliases are explicit and time-boxed.\n- CI catches schema drift.
Phase landed: PR #22 added the base MCP target resolver subpath and PR #24 fixed future Gitea npm publish auth. @molecule-ai/mcp-server@1.1.1 is published in the Gitea npm registry. Remaining schema/client alignment beyond target resolution should stay tracked separately if needed.
Follow-up landed: PR #25 exports EXTERNAL_WORKSPACE_MCP_TOOLS from @molecule-ai/mcp-server/external-workspace-tools and v1.2.0 published successfully through the fixed Gitea workflow. Claude channel PR #18 now consumes that schema SSOT; post-merge channel CI is green.