Xenarch MCP

Xenarch MCP runs locally from a Node.js package published to the npm registry: @xenarch/agent-mcp version 1.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @xenarch/agent-mcp@1.3.1. It reads these environment variables: XENARCH_PRIVATE_KEY (secret), XENARCH_RPC_URL, XENARCH_NETWORK and XENARCH_MAX_PAYMENT_USD; set them in the client's configuration for this server.

Xenarch MCP runs locally from a Node.js package published to the npm registry: @xenarch/agent-mcp version 1.1.0. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL. It reads these environment variables: XENARCH_PRIVATE_KEY (secret), XENARCH_RPC_URL, XENARCH_NETWORK, XENARCH_MAX_PAYMENT_USD, PORT and TRANSPORT (required); set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "xenarch-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@xenarch/agent-mcp@1.3.1"
      ],
      "env": {
        "XENARCH_PRIVATE_KEY": "<secret>",
        "XENARCH_RPC_URL": "<value>",
        "XENARCH_NETWORK": "<value>",
        "XENARCH_MAX_PAYMENT_USD": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect