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
MCP server that lets Claude Code, Cursor or Codex ask you for API keys on a local page and write them to .env. The agent only ever sees key names.

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

Free, public vulnerability feed for coding agents. One deduplicated entry per CVE, GHSA or OSV id, merged from the CVE List, GitHub Advisories, OSV, NVD, CISA KEV, EPSS and Exploit-DB. check_stack scans a lockfile for kn


Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci
Comments