CosmWasm MCP Server Template

Created By
drewstaylora year ago
MCP server template for CosmWasm smart contract projects
Overview

What is CosmWasm MCP Server Template?

The CosmWasm MCP Server Template is a project template designed for building MCP servers that can interact with CosmWasm smart contracts. It provides a structured way to wrap query and execute entry point messages for broadcasting by a signer.

How to Use the CosmWasm MCP Server Template?

To use this template, clone the repository and follow the steps to customize it for your own CosmWasm contracts. You will need to update the Cargo.toml file, ensure your contract can be built as a library, and modify the server configuration files accordingly.

Key Features of the CosmWasm MCP Server Template?

  • Supports multiple transport modes: stdio, sse, and http-streamable.
  • Provides tools for listing contract deployments, NFT collections, and building query/execute messages.
  • Customizable for various CosmWasm contracts with easy integration steps.

Use Cases of the CosmWasm MCP Server Template?

  1. Building a server for a new CosmWasm contract.
  2. Integrating with AI agents for enhanced contract interaction.
  3. Developing multi-contract systems with shared functionalities.

FAQ from CosmWasm MCP Server Template?

  • What programming language is used?

    The template is built using Rust.

  • Is there a license for this project?

    Yes, it is licensed under the Apache-2.0 license.

  • Can I use this template for any CosmWasm contract?

    Yes, it is designed to work with any CosmWasm contract with the necessary modifications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
drewstaylor
Star
1
Language
Rust
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

32 minutes ago