Cyberdyne MCP Server

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 cyberdyne-mcp -- npx -y cyberdyne-mcp

{
  "mcpServers": {
    "cyberdyne-mcp": {
      "args": [
        "-y",
        "cyberdyne-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.cyberdyne-mcp]
command = "npx"
args = ["-y", "cyberdyne-mcp"]

{
  "mcpServers": {
    "cyberdyne-mcp": {
      "args": [
        "-y",
        "cyberdyne-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "cyberdyne-mcp": {
      "args": [
        "-y",
        "cyberdyne-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: CYBERDYNE_IDENTITY_TOKEN (CYBERDYNE agent auth token. Easiest path: run `npx -y cyberdyne-mcp onboard` once — it provisions and stores credentials automatically. Set this only for headless/advanced use.), CYBERDYNE_EVM_PRIVATE_KEY (Private key of the agent wallet used to sign on-chain deploy/fee txs on Base (an external signer is also supported). Provisioned by `onboard`; set only for headless/advanced use.), CYBERDYNE_BANKR_KEY (Optional bk_ Bankr Agent-API key. Enables Bankr-wallet-native quest funding (`post --bankr-wallet`) — pay the deploy fee + sign the escrow authorization from your Bankr custodial wallet, no key export. Falls back to BANKR_API_KEY / ~/.bankr/config.json. Used directly against api.bankr.bot; never stored by CYBERDYNE.). The author declared them in the registry entry; get the values from the project itself.