CosmWasm MCP Server

Created By
adairrra year ago
A Model Context Protocol (MCP) server that provides tools for interacting with CosmWasm smart contracts.
Overview

What is CosmWasm MCP Server?

CosmWasm MCP Server is a Model Context Protocol (MCP) server that provides tools for interacting with CosmWasm smart contracts, enabling AI agents to manage and interact with blockchain-based contracts programmatically.

How to use CosmWasm MCP Server?

To use the CosmWasm MCP Server, you need to build the server using Rust, configure it in your Claude Desktop settings, and then interact with it through chat commands.

Key features of CosmWasm MCP Server?

  • Tools for managing and interacting with CosmWasm smart contracts.
  • Built using Rust for performance and reliability.
  • Integration with Claude Desktop for easy interaction.

Use cases of CosmWasm MCP Server?

  1. Querying smart contract states.
  2. Incrementing values in smart contracts.
  3. Retrieving balances from blockchain accounts.

FAQ from CosmWasm MCP Server?

  • What programming language is used for the server?

The server is written in Rust.

  • How do I configure the server?

You need to add the server configuration to your Claude Desktop config file.

  • Can I use this server for any blockchain?

Currently, it is designed for CosmWasm smart contracts.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
adairrr
Star
1
Language
Rust
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)

2 days ago