Zeta Chain CLI MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    execSync(`${command} zetachain`, { stdio: "ignore" });

  const sourceDir = path.join(examplesDir, chosenExample);

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      - name: Update config.json version
        run: |
          VERSION=${GITHUB_REF#refs/tags/v}
          jq --arg v "$VERSION" '.version = $v' src/config.json > tmp.json && mv tmp.json src/config.json
        env:
          GITHUB_REF: ${{ github.ref }}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

claude mcp add zeta-chain-cli --transport http https://server.smithery.ai/@zeta-chain/cli/mcp

{
  "mcpServers": {
    "zeta-chain-cli": {
      "url": "https://server.smithery.ai/@zeta-chain/cli/mcp"
    }
  }
}

[mcp_servers.zeta-chain-cli]
url = "https://server.smithery.ai/@zeta-chain/cli/mcp"

{
  "mcpServers": {
    "zeta-chain-cli": {
      "url": "https://server.smithery.ai/@zeta-chain/cli/mcp"
    }
  }
}

{
  "mcpServers": {
    "zeta-chain-cli": {
      "url": "https://server.smithery.ai/@zeta-chain/cli/mcp"
    }
  }
}

Endpoints