How do I install io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp?

io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp?

io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp actively maintained?

io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp is actively maintained — last commit was 5 days ago.

io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp

MCP server for safe AI agent runtime upgrades: regression catalog + snapshot diff + rollback.

8 tools GitHub

No known CVEs

No license

Actively maintained

Last commit 5d ago

Works with most clients

Transport: stdio

8 tools · ~541 tok

Grade B · 0.3% of 200K ctx

Edit this pageView history

AI / ML DevOps

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-temurkhan13-openclaw-upgrade-orchestrator-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-temurkhan13-openclaw-upgrade-orchestrator-mcp)](https://mcppedia.org/s/io-github-temurkhan13-openclaw-upgrade-orchestrator-mcp)

Read me

What io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp does

MCP server for safe AI agent runtime upgrades — version-aware regression catalog, pre/post snapshot diffing, step-by-step upgrade + rollback guides. Captures deployment state before upgrade, re-runs detection checks after, surfaces new_failures (caused by the upgrade) separately from unchanged_failures (pre-existing) and recovered (fixed by the upgrade). Read-only by design — never executes the upgrade itself; the operator retains full agency. v1.0 ships with the OpenClaw regression catalog (8

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

67/100across 5 weighted dimensions

How we score →

0255075100

−33

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Inventory

Tools (8)

Click any tool to inspect its schema.

~541 tokens total

Inventory

Resources (3)

upgrade://current

Current version info

upgrade://current

upgrade://snapshots

Every stored snapshot

upgrade://snapshots

upgrade://catalog

Full regression catalog

upgrade://catalog

Inventory

Prompts (2)

plan-upgrade

Walks through the upgrade decision for a target version

verify-upgrade

Walks through post-upgrade verification against a pre-upgrade snapshot

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp safe to use?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What can io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp do?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp provides 8 tools: current_version, available_upgrades, pre_upgrade_snapshot, upgrade_guide, post_upgrade_verify and 3 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp actively maintained?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp is actively maintained — last commit was 5 days ago.

Similar servers

Others in ai-ml / devops

View all →

Memory MCP Server98

Persistent memory using a knowledge graph

85.9k 5

Mcp Gitlab96

MCP server for using the GitLab API

1.5k 12

Context Mode95

Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.

15.1k 6

Gemini Cli95

An open-source AI agent that brings the power of Gemini directly into your terminal.

104.3k 8

MCP Security Weekly

Get CVE alerts and security updates for io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

AI / ML DevOps

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-temurkhan13-openclaw-upgrade-orchestrator-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-temurkhan13-openclaw-upgrade-orchestrator-mcp)](https://mcppedia.org/s/io-github-temurkhan13-openclaw-upgrade-orchestrator-mcp)

Read me

What io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp does

MCP server for safe AI agent runtime upgrades — version-aware regression catalog, pre/post snapshot diffing, step-by-step upgrade + rollback guides. Captures deployment state before upgrade, re-runs detection checks after, surfaces new_failures (caused by the upgrade) separately from unchanged_failures (pre-existing) and recovered (fixed by the upgrade). Read-only by design — never executes the upgrade itself; the operator retains full agency. v1.0 ships with the OpenClaw regression catalog (8

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

openclaw-upgrade-orchestrator-mcp

MCP server for safe AI agent runtime upgrades — version-aware regression catalog, pre/post snapshot diffing, step-by-step upgrade + rollback guides. Captures deployment state before upgrade, re-runs detection checks after, surfaces new_failures (caused by the upgrade) separately from unchanged_failures (pre-existing) and recovered (fixed by the upgrade). Read-only by design — never executes the upgrade itself; the operator retains full agency. v1.0 ships with the OpenClaw regression catalog (8 entries grounded in real field reports); the same machinery accepts a custom catalog for any AI runtime via Custom MCP Build adapters. Keywords: AI runtime upgrade, regression detection, safe deployment, version-specific bug catalog, AI agent ops.

What it does

Production AI runtime upgrades — OpenClaw, Claude Code, agent harnesses, runtime servers — carry recurring regressions that you only find after upgrading. Recent examples:

The "claw tax." Anthropic announced standard Claude subscriptions would no longer cover usage through external "claw" harnesses like OpenClaw — forcing those workloads onto metered API billing — without a clean upgrade path. r/AI_Agents thread on the OpenClaw creator suspension (201 pts, April 12 2026) walks through the structural conflict.
OpenClaw 2026.4.8 brought a CPU-spike bug. 2026.4.23-26 broke Discord on_message. 2026.4.30+ surfaced OOM under sustained 200k-token contexts. The pattern: upgrade on Friday, hit a new failure mode on Tuesday, spend Wednesday-Thursday excavating release notes + field reports.
Claude Code itself has documented compaction failures at 48% context usage (GitHub Issue #23751) and the "1M context window does not work as marketed" complaint (GitHub Issue #35296) — recurring upgrade regressions in the underlying runtime, not just OpenClaw.
HERMES.md detection (the billing routing bug) is itself an upgrade regression — Anthropic added detection logic that fires false positives, and operators only discover it when they're already $200 deep in unintended API charges.

This MCP server moves the regression excavation upfront — before the upgrade, not after — and verifies the post-upgrade state by diffing against a snapshot you took beforehand. Read-only by design: never executes the upgrade itself; the operator retains full agency.

> claude: should I upgrade my 2026.4.23 deployment?
[MCP tools: current_version + available_upgrades]

Current: 2026.4.23
Recommended target: 2026.5.2 (no CRITICAL regressions in path)

Available upgrades:
  2026.4.24-.26  HIGH    R-73421 Discord-receive breakage
  2026.4.27       —      clean
  2026.4.30       HIGH    R-OOM-DURING-LARGE-CONTEXT (unfixed)
  2026.5.1-.2     HIGH    R-OOM + R-LOG-ROTATION-DROP (unfixed)

> claude: walk me through upgrading to 2026.4.27.
[MCP tool: upgrade_guide]

2026.4.23 → 2026.4.27 — proceed with mitigations applied.

Applicable known regressions:
  R-41372 (HIGH)  — Cron --session web-sea

... [View full README on GitHub](https://github.com/temurkhan13/openclaw-upgrade-orchestrator-mcp#readme)

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

67/100across 5 weighted dimensions

How we score →

0255075100

−33

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Inventory

Tools (8)

Click any tool to inspect its schema.

~541 tokens total

Inventory

Resources (3)

upgrade://current

Current version info

upgrade://current

upgrade://snapshots

Every stored snapshot

upgrade://snapshots

upgrade://catalog

Full regression catalog

upgrade://catalog

Inventory

Prompts (2)

plan-upgrade

Walks through the upgrade decision for a target version

verify-upgrade

Walks through post-upgrade verification against a pre-upgrade snapshot

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp safe to use?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What can io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp do?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp provides 8 tools: current_version, available_upgrades, pre_upgrade_snapshot, upgrade_guide, post_upgrade_verify and 3 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp actively maintained?: io.github.temurkhan13/openclaw-upgrade-orchestrator-mcp is actively maintained — last commit was 5 days ago.