io.github.faulkj/legion

io.github.faulkj/legion

MCP-native LLM councils for debates, juries, blind panels, refinement, and custom deliberation.

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "legion": {
      "command": "npx",
      "args": [
        "-y",
        "legion-mcp@0.8.0"
      ],
      "env": {
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "DEFAULT_API_KEY": "<your DEFAULT_API_KEY>",
        "ALLOW_NO_MODELS": "<your ALLOW_NO_MODELS>",
        "OPENAI_API_KEY": "<your OPENAI_API_KEY>",
        "MAX_ROUNDS": "5",
        "DYNAMIC_ROLES": "true",
        "LOG_LEVEL": "info",
        "ASYNC_TOOLS": "false",
        "TRUST_PROXY_AUTH": "false"
      }
    }
  }
}
Environment variables
  • MCP_TRANSPORTrequiredRun the installed package over MCP stdio (the binary defaults to HTTP).
  • DEFAULT_API_KEYsecretDefault provider or gateway key for model files that omit apiKey.
  • ALLOW_NO_MODELSrequiredBoot 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_KEYsecretOptional. 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_ROUNDSMaximum discussion rounds accepted by a council run.
  • DYNAMIC_ROLESAllow callers to define ad-hoc council roles inline.
  • LOG_LEVELLogging verbosity. Logs are written to stderr for stdio safety.
  • ASYNC_TOOLSRun councils in the background: council tools return a job handle and poll/cancel tools are exposed. Jobs live in process memory only.
  • TRUST_PROXY_AUTHBind async jobs to the caller named by X-MS-CLIENT-PRINCIPAL-* headers. Only safe behind an ingress that strips client-supplied copies.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
0.8.0
Registry
active
Published
10/6/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that io.github.faulkj/legion is listed here — it’s also the link we check for a free listing.

io.github.faulkj/legion — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-faulkj-legion?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="io.github.faulkj/legion — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![io.github.faulkj/legion — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-faulkj-legion?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.