What are the build requirements?
The server requires the Rust `nightly` build channel (edition 2024). Build with `cargo build` for development or `cargo build --release` for deployment.
@drewstaylor
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 for wrapping CosmWasm contract query and execute entry point messages into formats that can be broadcast by a signer. It works with any CosmWasm contract and is intended for developers building MCP servers that enable AI agents to interact with on-chain contracts.
Requires Rust on the nightly channel. Adapt the template to your contract by updating Cargo.toml with your contract dependency, feature‑gating entry points, replacing imports in src/server.rs, and setting deployed contract addresses in src/contract.rs. Optionally customize LLM instructions, enable custom tool schemas, and choose a transport mode (stdio, SSE, or HTTP‑streamable). Build with cargo build --release. Connect to Claude Desktop via stdio, or to LangGraph via @langchain/mcp-adapters.
The server requires the Rust `nightly` build channel (edition 2024). Build with `cargo build` for development or `cargo build --release` for deployment.
Update `Cargo.toml` with your contract’s dependency, ensure entry points are feature‑gated for library mode, replace the contract import in `src/server.rs` with your own `QueryMsg` and `ExecuteMsg`, and update the deployed contract addresses in `src/contract.rs`. Optional steps include enabling custom tool schemas and customizing LLM instructions.
Three transport modes are supported: **stdio** (default), **SSE** (Server‑Side Events), and **HTTP‑streamable** (a newer standard for remote MCP servers). The mode can be set in the server configuration.
For stdio mode, set the `command` in `claude_desktop_config.json` to the path of the release binary. For WSL or VM setups, use the VM executable as the command and provide run arguments to the binary path.
Add detailed doc comments (triple‑slash `///`) to your contract’s `QueryMsg` and `ExecuteMsg` variants. The `schemars` crate emb

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
Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.

Multi-zone MCP server for GKE/EKS/AKS: Python tools from git, NeMo guardrails, SSO, autoscaling.

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.
Comments