useChainRegistryLABSCO SUMMARY
A Starship config written and checked for you, with the Interchain library guides alongside.
Starship configurations are where interchain test setups usually stall. Generating one and then verifying it before a run turns a trial-and-error loop into two calls. Note this is the Hyperweb platform server — generating an MCP server from a chain is a different project.
What it is
A server for Hyperweb's Interchain developer stack; the project docs list eight tools. Three cover the Starship testing framework: writing a configuration from what you describe, verifying one you already have, and setting the environment up. The other five give usage examples and migration help for Chain Registry, Interchain Kit (including moving off CosmosKit) and InterchainJS (including moving off CosmJS).
What you get
- generateStarshipConfig — produce a Starship configuration
- verifyStarshipConfig — check an existing configuration before you run it
- setupStarship — set the Starship environment up
Requirements
npx and the package @hyperweb/mcp-server, run over stdio. No credentials.
Setup effort
One command — npx -y @hyperweb/mcp-server@latest
USE CASES
01
Standing up a test network configuration
Describe what you need and get a Starship configuration back instead of writing the YAML.
02
Catching a broken configuration before the run
Verify the file first, rather than finding out when the network fails to come up.
03
Getting the environment ready
Run the setup step so Starship has what it needs before the first launch.
04
Adjusting a configuration you inherited
Verify what is there, regenerate the part that is wrong, and verify again.
8 tools
Listed in project docs. Your client may show a different list.
useInterchainKitmigrateFromCosmosKitToInterchainKituseInterchainjsmigrateToInterchainjssetupStarshipgenerateStarshipConfigverifyStarshipConfigBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation. The GitHub README table lists only the three Starship tools; the project docs list all 8.
Requires
- Node.js (v20 or higher)
- pnpm (v10 or higher)
- Any IDE or editor that supports MCP protocol, for example Cursor, Windsurf or Claude Desktop
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @hyperweb/mcp-server@latestMCP Clients
Cursor, Claude Desktop
JSON
{
"mcpServers": {
"hyperweb-mcp-server": {
"command": "npx",
"args": [
"-y",
"@hyperweb/mcp-server@latest"
]
}
}
}Any MCP client — Windows
ANY MCP CLIENT — WINDOWS · JSON
{
"mcpServers": {
"hyperweb-mcp-server": {
"command": "cmd",
"args": [
"/k",
"npx",
"-y",
"@hyperweb/mcp-server@latest"
]
}
}
}
