MCP server for Cosmos SDK chain migration (v50+ -> v54)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cosmos-migration-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Cosmos SDK Migration MCP Server An MCP (Model Context Protocol) server for migrating Cosmos SDK chains from `v0.50+` to `v0.54`. This repository packages the migration server, the YAML migration specs, the orchestration guide, and the bundled upgrade-doc resources it exposes over MCP. ## Install ```bash pip install cosmos-migration-mcp ``` Or for local development: ```bash git clone https://github.com/cosmos/cosmos-sdk-migration-mcp.git cd cosmos-sdk-migration-mcp pip install -e . ``` ## Run The package exposes a `cosmos-migration-mcp` console script: ```bash cosmos-migration-mcp ``` You can also run it as a module: ```bash python -m cosmos_migration_mcp ``` ## Claude Desktop Add to `claude_desktop_config.json`: ```json { "mcpServers": { "cosmos-migration": { "command": "cosmos-migration-mcp" } } } ``` ## Claude Code ```bash claude mcp add cosmos-migration -- cosmos-migration-mcp ``` ## Reference - **[Canonical Cosmos SDK Upgrade Guide](https://github.com/cosmos/cosmos-sdk/blob/main/UPGRADING.md)** — The official upstream source for breaking changes and migration instructions for all Cosmos SDK versions. > This MCP server bundles snapshots of the v0.54 upgrade documentation and migration specs. Always consult the canonical upstream guide for the latest information and breaking changes. ## Tools | Tool | Description | |---|---| | `scan_chain_tool` | Detect SDK version and which specs apply to a chain | | `get_migration_plan` | Preview all changes without modifying files | | `apply_spec` | Apply a single spec, including go.mod edits, arg rewrites, and special cases | | `verify_spec_tool` | Run verification checks for one spec | | `verify_all_specs` | Run verification for an explicit spec list or for currently detectable specs | | `verify_build` | Run `go build ./...` and return structured results | | `run_go_mod_tidy` | Run `go mod tidy` and return structured results | | `run_tests` | Run `go test ./...` and return structured …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.