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.
CosmWasm MCP Server Template
@drewstaylor
基本情報
CosmWasm MCP Server Template について
MCP server template for CosmWasm smart contract projects
CosmWasm MCP Server Template の設定
CosmWasm MCP Server Template のツール
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
概要
What is CosmWasm MCP Server Template?
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.
How to use CosmWasm MCP Server Template?
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.
Key features of CosmWasm MCP Server Template
- Wraps CosmWasm query and execute entry points
- Generates JSON schemas for AI agents
- Supports stdio, SSE, and HTTP‑streamable transports
- Customizable LLM instructions and tool descriptions
- Works with any CosmWasm contract via template adaptation
- Provides 6 default MCP tools for contract interaction
Use cases of CosmWasm MCP Server Template
- Building MCP servers for CosmWasm smart contracts
- Enabling AI agents to query and transact with on‑chain contracts
- Automating contract interactions in LangGraph or Claude Desktop
- Creating custom tooling for marketplace, NFT, or multi‑contract systems
よくある質問
How do I adapt the template to my own contract?
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.
What transport modes are supported?
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.
How do I connect the server to Claude Desktop?
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.
How can I improve AI accuracy when using the server?
Add detailed doc comments (triple‑slash `///`) to your contract’s `QueryMsg` and `ExecuteMsg` variants. The `schemars` crate emb
「開発者ツール」の他のコンテンツ
Agent Conductor
icohangar-opsAgent conductor — AGENTS.md contract parser, SKILL.md registry, CHP decision engine over MCP
Yocoolab
YocoolabMCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools
1
Foremerge
naw103Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.
50
The Bridge
The BridgeComplete, hosted login, teams, billing and feature flags for your SaaS app, set up by your AI assistant: sign-in and SSO, customer teams and roles, plans and usage limits on Stripe, and feature flags. OAuth sign-in, no A
Mcp-Warden
ermolukLocal-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.
4
コメント