openclaw-upgrade-orchestrator-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENCLAW_VERSION_FILE | No | Path to the version file, used by 'openclaw-system' backend. Default: ~/.openclaw/version | |
| OPENCLAW_GATEWAY_CONFIG | No | Path to the gateway config, used by 'openclaw-system' backend. Default: ~/.openclaw/gateway.yaml | |
| OPENCLAW_UPGRADE_BACKEND | No | Backend to use: 'mock' or 'openclaw-system'. Defaults to 'mock'. | mock |
| OPENCLAW_UPGRADE_SNAPSHOT_DIR | No | Directory for persisting snapshots, used by 'openclaw-system' backend. Default: ~/.openclaw/upgrades/snapshots/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| current_versionA | Return the currently-installed OpenClaw version + how it was detected. Run this first to confirm the backend can read your deployment. |
| available_upgradesA | List newer-than-current versions, flag any that carry CRITICAL regressions, and recommend the highest version with no CRITICAL regressions in its upgrade path. |
| pre_upgrade_snapshotA | Run every detection check against the live deployment and persist the result as a Snapshot. Returns the snapshot_id you'll feed to post_upgrade_verify and rollback_guide. |
| upgrade_guideA | Compose the step-by-step upgrade plan from current → target. Includes pre-upgrade prep steps, the upgrade itself, post-upgrade verification, rollback steps, and any applicable known regressions with their mitigations. |
| post_upgrade_verifyA | Take a fresh post-upgrade snapshot and diff against a stored pre-upgrade snapshot. Surfaces new_failures (most important), recovered checks, and unchanged failures. Outcome is one of 'success' / 'degraded' / 'regressed'. |
| rollback_guideA | Compose the rollback plan for a given pre-upgrade snapshot — downgrade command + state-restore steps + risk notes about data migration loss. |
| regression_catalogA | Return every known regression in the catalog, optionally filtered to a specific version. Each entry has id + version range + severity + description + mitigation + linked field reports. |
| list_snapshotsA | List all stored snapshots (id, captured_at, version, summary). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan-upgrade | Walk operator through deciding + planning an upgrade |
| verify-upgrade | Walk operator through post-upgrade verification using a pre-upgrade snapshot |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current OpenClaw version | Detected current version + detection method |
| Stored snapshots | All pre/post snapshots persisted by the backend |
| Regression catalog | Full known-regression catalog (all versions) |
TDQS
Scored across 8 tools
Each tool targets a distinct aspect of the upgrade workflow: version discovery, upgrade listing, snapshot management, pre/post verification, regression info, and plan generation. No two tools have overlapping purposes, ensuring clear selection.
All tool names follow consistent snake_case and are descriptive (e.g., available_upgrades, pre_upgrade_snapshot, rollback_guide). The pattern is predictable and clearly communicates each tool's function.
With 8 tools, the server covers the core upgrade orchestrator workflow without being bloated. Each tool serves a necessary role, making the set well-scoped for its domain.
The tool set covers most essential operations: version detection, upgrade listing, pre/post snapshots, verification, rollback, and regression catalog. The only minor gap is the lack of a tool to actually execute the upgrade, but the upgrade_guide provides step-by-step instructions.