Zetrix

You run a Zetrix MCP server to interact with the Zetrix blockchain from Claude Desktop. This server exposes a wide set of account, block, transaction, contract, WebSocket, and utility operations that you can access from your MCP client to manage accounts, query chain state, simulate transactions, and subscribe to real-time updates.

How to use

You connect your MCP client to the Zetrix MCP server to perform operations such as querying accounts, checking balances, submitting transactions, calling contracts in sandbox, and receiving real-time updates via WebSocket. Start the server through the standard runtime you configured, then configure your MCP client to point at the Zetrix MCP server using the provided runtime commands. The server is designed to be used in development or production modes, and supports health checks, multi-query, and a broad set of Zetrix-specific endpoints.

How to install

Prerequisites: you need Node.js installed on your machine. Ensure you have npm available to install dependencies and build the project.

# Install dependencies
npm install

# Build the MCP server
npm run build

# Optional interactive setup (if you want to configure during setup)
npm run setup

Configuration and usage notes

You run the Zetrix MCP server locally via a stdio configuration that launches Node to run the server from its built distribution. You can choose between running on the Zetrix mainnet, testnet, or a custom RPC URL. The following runtime configurations show the exact commands you would place in your Claude Desktop MCP configuration to start the server.

{
  "mcpServers": {
    "zetrix_mainnet": {
      "command": "node",
      "args": ["/absolute/path/to/zetrix-mcp-server/dist/index.js"],
      "env": {
        "ZETRIX_NETWORK": "mainnet"
      }
    },
    "zetrix_testnet": {
      "command": "node",
      "args": ["/absolute/path/to/zetrix-mcp-server/dist/index.js"],
      "env": {
        "ZETRIX_NETWORK": "testnet"
      }
    },
    "zetrix_custom": {
      "command": "node",
      "args": ["/absolute/path/to/zetrix-mcp-server/dist/index.js"],
      "env": {
        "ZETRIX_RPC_URL": "https://custom-node.zetrix.com"
      }
    }
  }
}

Usage notes for runtime configuration

• Use the mainnet configuration when you want to connect to the main Zetrix network. - Use the testnet configuration for development and testing against a test network. - Use the custom RPC URL configuration when you want to point the MCP server at a self-hosted or alternate RPC endpoint. - Each entry runs a local Node process that starts the MCP server from its built distribution. - If you run multiple configurations, you can enable/disable them as needed in your Claude Desktop setup.

Security and environment

Protect sensitive information such as private keys or RPC endpoints. Use secure storage for environment values and restrict access to the Claude configuration. When using a custom RPC URL, ensure the endpoint is trusted and supports the required Zetrix APIs.

Troubleshooting tips

If the MCP server does not start, verify that Node.js is installed and the path to the built dist/index.js is correct. Check that the environment variable values are set as shown in the configuration blocks. Use the health check and multi-query endpoints to verify connectivity to the Zetrix node.

Available tools

zetrix_check_health

Check the health status of the Zetrix node and verify connectivity

zetrix_get_account

Retrieve complete account information including balance and metadata

zetrix_get_block

Fetch information about a specific block by height

zetrix_get_latest_block

Retrieve the latest block information

zetrix_get_transaction

Get details for a transaction by its hash

zetrix_submit_transaction

Submit a signed transaction to the Zetrix network

zetrix_call_contract

Call a smart contract in sandbox mode for debugging

zetrix_ws_connect

Connect to WebSocket for real-time updates and subscribe to events

zetrix_ws_subscribe_tx

Subscribe to transaction notifications for specific addresses