What transport modes does the server support?
The template supports three transport modes: stdio (default), sse (server‑side events), and http‑streamable.
@archway-network
Basic information
MCP server template for CosmWasm smart contract projects
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
A Rust-based MCP (Model Context Protocol) server template that wraps query and execute entry point messages from any CosmWasm smart contract so they can be broadcast by a signer. It is designed for developers who want to enable AI agents to interact with their CosmWasm contracts via MCP tools.
Build the project using the Rust nightly channel (rustup default nightly) and run cargo build or cargo build --release. To customize the template for your own contract, update the contract dependency in Cargo.toml, modify src/server.rs to import your contract’s QueryMsg and ExecuteMsg, and set the deployed contract addresses in src/contract.rs. Optional steps include enabling MCP tools for custom types, customizing LLM instructions in src/instruction.rs, and choosing a transport mode (stdio, sse, or http-streamable).
The template supports three transport modes: stdio (default), sse (server‑side events), and http‑streamable.
It provides six tools: `list_contract_deployments`, `list_nft_collections`, `list_query_entry_points`, `build_query_msg`, `list_tx_entry_points`, and `build_execute_msg`.
Build a release binary, then point the MCP server’s `command` in `claude_desktop_config.json` to the binary path. No run arguments are required for stdio mode. For WSL users, execute the VM as the command and pass the binary path in `args`.
Add doc comments (triple‑slash `///`) to your contract’s `msg::QueryMsg` and `msg::ExecuteMsg` types. These comments are embedded into JSON schemas by schemars, helping the LLM interpret entry points correctly.
The project requires the Rust `nightly` toolchain because it uses edition 2024. Build with `cargo build` for development or `cargo build --release` for deployment.

ArtiBot Cloud MCP (Zhijiangyun 智匠云) — cloud MCP server for robot manipulation data & GPU workloads. 15 tools: robot fleet management, data collection & video recording, post-processing pipelines, and benchmark evaluation

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP

Open-source Next.js + Supabase CMS with a per-site MCP server: scaffold a site, then create pages, posts, navigation, media and SEO from Claude, Cursor or any MCP client. Streamable HTTP with a bearer token you mint in y
Comments