Skip to main content
Glama
temurkhan13

openclaw-upgrade-orchestrator-mcp

by temurkhan13
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENCLAW_VERSION_FILENoPath to the version file, used by 'openclaw-system' backend. Default: ~/.openclaw/version
OPENCLAW_GATEWAY_CONFIGNoPath to the gateway config, used by 'openclaw-system' backend. Default: ~/.openclaw/gateway.yaml
OPENCLAW_UPGRADE_BACKENDNoBackend to use: 'mock' or 'openclaw-system'. Defaults to 'mock'.mock
OPENCLAW_UPGRADE_SNAPSHOT_DIRNoDirectory 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription
plan-upgradeWalk operator through deciding + planning an upgrade
verify-upgradeWalk operator through post-upgrade verification using a pre-upgrade snapshot

Resources

Contextual data attached and managed by the client

NameDescription
Current OpenClaw versionDetected current version + detection method
Stored snapshotsAll pre/post snapshots persisted by the backend
Regression catalogFull known-regression catalog (all versions)

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/temurkhan13/openclaw-upgrade-orchestrator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server