molecule-ai/molecule-mcp-server
49
0
Fork 0
Code Issues 2 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

management MCP/CLI cannot migrate workspace compute provider (canvas can) #64

New Issue
Closed
opened 2026-06-15 02:08:08 +00:00 by devops-engineer · 0 comments
devops-engineer commented 2026-06-15 02:08:08 +00:00
Member
Copy Link
Copy Source

Gap

The canvas can migrate a workspace's compute provider across clouds (AWS ↔ Hetzner ↔ GCP), but the management MCP server and CLI cannot. This is a real capability gap: an operator driving the platform through the MCP/CLI has no way to trigger or observe a cross-cloud provider migration.

update_workspace exposes the workspace tier but has no provider field, so there is no existing path to change a workspace's compute provider through these tools.

Control-plane contract to wrap (CP-admin auth)

Start a migration — POST /cp/admin/workspaces/:id/migrate-provider

{ "from": "aws", "to": "hetzner", "confirm": true }

→ 202 { "status": "migration_started", "workspace_id": "…", "from": "aws", "to": "hetzner" }

  • to is required; one of aws|hetzner|gcp.
  • from is required by CP; one of aws|hetzner|gcp (must differ from to).
  • confirm:true is mandatory — a real migration mutates two clouds; without it CP returns 400.
  • from_instance_id is required by CP for non-AWS (Hetzner/GCP) sources; optional for AWS (CP resolves the real instance from EC2 tags).
  • Runs asynchronously (~15-20 min).

Read status — GET /cp/admin/workspaces/:id/migrate-provider (alias …/migration-status)

→ 200 { "migration": { "state", "from_provider", "to_provider", "detail", … }, "terminal": <bool> }

States: snapshotting → provisioning_target → target_healthy → retiring_source → completed (terminal also includes failed, rolled_back). 404 when the workspace has never been migrated.

Proposed fix

  • MCP server: add migrate_workspace_provider (inputs: workspace_id, to [required], from?, confirm?, from_instance_id?) and get_workspace_migration_status tools, wired through the existing CP-admin HTTP-client + tool-registration pattern.
  • CLI: add molecule workspace migrate-provider --to <p> [--from <p>] <workspace_id> and a migration-status subcommand via the existing cpAdminClient() helper.

Follow-up PRs will close this issue.

## Gap The canvas can migrate a workspace's compute provider across clouds (AWS ↔ Hetzner ↔ GCP), but the management MCP server and CLI cannot. This is a real capability gap: an operator driving the platform through the MCP/CLI has no way to trigger or observe a cross-cloud provider migration. `update_workspace` exposes the workspace **tier** but has **no provider field**, so there is no existing path to change a workspace's compute provider through these tools. ## Control-plane contract to wrap (CP-admin auth) **Start a migration** — `POST /cp/admin/workspaces/:id/migrate-provider` ```json { "from": "aws", "to": "hetzner", "confirm": true } ``` → `202 { "status": "migration_started", "workspace_id": "…", "from": "aws", "to": "hetzner" }` - `to` is required; one of `aws|hetzner|gcp`. - `from` is required by CP; one of `aws|hetzner|gcp` (must differ from `to`). - `confirm:true` is mandatory — a real migration mutates two clouds; without it CP returns 400. - `from_instance_id` is required by CP for non-AWS (Hetzner/GCP) sources; optional for AWS (CP resolves the real instance from EC2 tags). - Runs asynchronously (~15-20 min). **Read status** — `GET /cp/admin/workspaces/:id/migrate-provider` (alias `…/migration-status`) → `200 { "migration": { "state", "from_provider", "to_provider", "detail", … }, "terminal": <bool> }` States: `snapshotting → provisioning_target → target_healthy → retiring_source → completed` (terminal also includes `failed`, `rolled_back`). `404` when the workspace has never been migrated. ## Proposed fix - **MCP server**: add `migrate_workspace_provider` (inputs: `workspace_id`, `to` [required], `from?`, `confirm?`, `from_instance_id?`) and `get_workspace_migration_status` tools, wired through the existing CP-admin HTTP-client + tool-registration pattern. - **CLI**: add `molecule workspace migrate-provider --to <p> [--from <p>] <workspace_id>` and a `migration-status` subcommand via the existing `cpAdminClient()` helper. Follow-up PRs will close this issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
merge-queue
PR ready for admin merge
 tier:low
one repo/file group; revertable
 tier:medium
Touches deploy chain / release / multi-repo; manager+ approval
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-mcp-server#64
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?