CosmWasm MCP Server Template

Created By
archway-networka 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 specific CosmWasm contract. Key steps include updating the Cargo.toml file, ensuring your contract can be built as a library, and modifying the server configuration files.

Key Features of the CosmWasm MCP Server Template?

  • Supports multiple transport modes (stdio, sse, http-streamable)
  • Provides tools for listing contract deployments, NFT collections, and query entry points
  • Allows customization of server instructions and tool descriptions for better AI interaction

Use Cases of the CosmWasm MCP Server Template?

  1. Building a custom MCP server for a specific 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?

  • Can I use this template with any CosmWasm contract?
    Yes, this template is designed to work with any CosmWasm contract by making necessary adjustments.

  • What programming language is used?
    The project is built using Rust.

  • Is there any documentation available?
    Yes, detailed instructions are provided in the project repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
archway-network
Star
0
Language
Rust
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago