Legion MCP Server

What the code does

We read the source, 6 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.

этот файл ставится пользователю, но в репозитории его нет

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

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

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

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

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

This one needs environment variables set before it will start: MCP_TRANSPORT (Run the installed package over MCP stdio (the binary defaults to HTTP).), DEFAULT_BASE_URL (Default OpenAI Responses-compatible API root for model files that omit baseUrl.), DEFAULT_API_KEY (Default provider or gateway key for model files that omit apiKey.), ALLOW_NO_MODELS (Boot without any config/models/*.json. The package ships only key-free examples, which the scanner ignores, so this must stay true until a real model file exists beside the working directory.), OPENAI_API_KEY (Optional. A model file's apiKey may be "env:VAR" to read the key from an environment variable named VAR at startup; name those variables here as needed. The bundled gpt example reads this one.), MAX_ROUNDS (Maximum discussion rounds accepted by a council run.), TOKEN_BUDGET (Optional soft cumulative token budget for a council run.), DYNAMIC_ROLES (Allow callers to define ad-hoc council roles inline.), LOG_LEVEL (Logging verbosity. Logs are written to stderr for stdio safety.), ASYNC_TOOLS (Run councils in the background: council tools return a job handle and poll/cancel tools are exposed. Jobs live in process memory only.), TRUST_PROXY_AUTH (Bind async jobs to the caller named by X-MS-CLIENT-PRINCIPAL-* headers. Only safe behind an ingress that strips client-supplied copies.). The author declared them in the registry entry; get the values from the project itself.