ZetaChain logo

ZetaChain

  • Overview

    • Overview

  • Blockchain

    • Blockchain

  • Validators

    • Validators

  • Proposals

    • Proposals

  • Utilities

    • Utilities

  • Statistics

    • Statistics

  • Assets

    • Assets

  • Gas tracker

    • Gas tracker

  • MCP

    • MCP

  • Verify Contract

    • Verify Contract

mainnet

zetachain_7000-1

Latest Block

‌
‌

exploreme

Network

Home

Socials

WebsiteTwitterGithubDiscord

Help

Help centerBug report
Backend: —Frontend: v4.6.1-dev0908.1

Powered by

STAKEME
Beta

This section is currently in development and may change.

ZetaChain Agent Kit

MCPEVM + Cosmos

Explore ZetaChain through AI agents or the terminal. Query on-chain data, prepare transfers, deploy contracts and work with Cosmos staking from one workspace.

Download Agent KitRead guide GitHub

Checking server and loading tools…

Two ways to use

Subscription

No MCP API key

Connect Claude Code, Cursor or Codex using your existing AI plan.

  • Ready-to-use HTTP MCP configurations
  • Wallet, transfer, deployment and staking skills
  • Live EVM and Cosmos tools
Claude Code setupCursor setupCodex setup

AI SDK

Developers

Build programmatic TypeScript agents with the Vercel AI SDK and your own provider API key.

  • Anthropic and OpenAI providers
  • Runnable network and transaction examples
  • Separate preparation, signing and broadcast
AI SDK docs

Quick Start

Download the kit and open the extracted folder in your client. It includes Claude Code, Cursor and Codex configurations. For an existing workspace, add this HTTP server to your MCP settings:

{
  "mcpServers": {
    "zetachain": {
      "type": "http",
      "url": "https://zetachain.exploreme.pro/api/mcp"
    }
  }
}

Claude Code: .mcp.json · Cursor: .cursor/mcp.json. For Codex, register the same endpoint:

codex mcp add zetachain --url https://zetachain.exploreme.pro/api/mcp

Try asking: “Show the latest ZetaChain EVM blocks.” The kit also includes wallet, transfer, deployment and staking skills.

Architecture

Your client queries the remote MCP server. Transactions are prepared unsigned, reviewed and signed locally, then submitted to ZetaChain.

You · chat or code

Claude Code · Cursor · Codex · AI SDK

Public wallet address, chain data and unsigned transaction details

Signer · local

Review and sign with the local EVM CLI or your external wallet.

Keys stay outside MCP requests

MCP server · remote

Query EVM and Cosmos data, prepare transactions and broadcast signed payloads.

ZetaChain mainnet · chain 7000

Signing & security

MCP does not need your private key. The SDK agent can query data and prepare transactions; signing and broadcast are separate actions you review.

Local EVM wallet

Create a development wallet and keep its key in a local file. The signer validates chain, sender, value and fees before asking you to confirm.

npm run wallet
npm run kit -- sign prepared.json signed.json
npm run kit -- broadcast signed.json

The key file is unencrypted. Keep it and signed transaction files out of chat and shared folders.

External wallet

Use your own wallet to review and sign EVM transactions or Cosmos staking messages. Submit only the signed payload to MCP.

  • EVM: signed transaction hex
  • Cosmos: signed transaction bytes in base64
  • Cosmos uses azeta: 1 ZETA = 1018 azeta
Read the signing guide