Zetachain MCP Server

Created By
Zetachain Developer8 months ago
An MCP server that connects ZetaChain CLI into your editor. Query balances, send cross-chain transactions, and manage universal contracts directly through MCP.
Overview

what is Zetachain MCP Server?

Zetachain MCP Server is a command-line interface (CLI) tool that connects ZetaChain CLI into your editor, allowing users to query balances, send cross-chain transactions, and manage universal contracts directly through the MCP.

how to use Zetachain MCP Server?

To use the Zetachain MCP Server, you can run it without installation using the command: npx zetachain@next new, or install it globally with npm install -g zetachain@latest. You can also start a local multi-chain development environment with a single command.

key features of Zetachain MCP Server?

  • Scaffold new ZetaChain universal apps from templates.
  • Spin up a local multi-chain development environment (EVM, Solana, etc.) in one command.
  • Query cross-chain fees, contracts, balances, and tokens.
  • Make cross-chain calls between various blockchains like Solana, Sui, Bitcoin, and TON.
  • Transfer supported tokens across connected chains.

use cases of Zetachain MCP Server?

  1. Developing and testing multi-chain applications.
  2. Managing cross-chain transactions and balances.
  3. Interacting with various blockchain networks from a single CLI.

FAQ from Zetachain MCP Server?

  • What are the prerequisites for using Zetachain MCP Server?

You need Node.js ≥ 18 and Git for template cloning. Docker is optional for localnet.

  • Can I run Zetachain MCP Server without installation?

Yes! You can use the command npx zetachain@next new to run it without installation.

  • How do I get help with commands?

You can use --help with any command to get detailed documentation.

Server Config

{
  "mcpServers": {
    "zetachain": {
      "command": "npx",
      "args": [
        "-y",
        "zetachain",
        "mcp"
      ]
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
Zetachain Developer
Star
-
Language
-
License
-
Category

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