Cyberwarex Council

Cyberwarex Council runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/cyberwarex/cyberwarex-council:1.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e CWX_X_PAYMENT -e CWX_SUBSCRIPTION_KEY -e CWX_COUNCIL_URL ghcr.io/cyberwarex/cyberwarex-council:1.1.2. It reads these environment variables: CWX_X_PAYMENT (secret), CWX_SUBSCRIPTION_KEY (secret) and CWX_COUNCIL_URL; 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": {
    "cyberwarex-council": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CWX_X_PAYMENT",
        "-e",
        "CWX_SUBSCRIPTION_KEY",
        "-e",
        "CWX_COUNCIL_URL",
        "ghcr.io/cyberwarex/cyberwarex-council:1.1.2"
      ],
      "env": {
        "CWX_X_PAYMENT": "<secret>",
        "CWX_SUBSCRIPTION_KEY": "<secret>",
        "CWX_COUNCIL_URL": "<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