ZendIQ MCP Server

What the code does

We read the source, 4 d ago · rules ccca72095570

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.

  return require(path.join(dir, name));

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

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp -- npx -y @zendiq/mcp

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@zendiq/mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp]
command = "npx"
args = ["-y", "@zendiq/mcp"]

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@zendiq/mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp": {
      "args": [
        "-y",
        "@zendiq/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: ZENDIQ_AGENT_NETWORK (Payment network: mainnet (default) or devnet. The free screen tool needs no payment.), AGENT_STATE_DIR (Folder holding payer-mainnet.key.json (any file solana-keygen writes) and the budget ledger. Defaults to ~/.zendiq. Never inside the npm cache.), ZENDIQ_AGENT_BUDGET_FILE (Spend-ceiling ledger every payment is reserved against. Defaults to <state dir>/budget-<network>.json, created by: npx -y @zendiq/mcp budget init 1.00), ZENDIQ_AGENT_KEYPAIR (Devnet only: path to a Solana keypair JSON file holding devnet USDC.). The author declared them in the registry entry; get the values from the project itself.