Collusion MCP Server

A multi-agent MCP engine for technical design orchestration. Give it a task, and three AI agents — each representing a different perspective

Local serverstdioPython

What is the Collusion MCP server?

If you already use Collusion, the collusion mcp server is the piece that lets your assistant work with it directly. A multi-agent MCP engine for technical design orchestration. Give it a task, and three AI agents — each representing a different perspective (Business Value, Technical Architecture, Security & Compliance) — independently generate.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Roadmap — See ROADMAP.md for the full public roadmap covering v0.4.0 through v1.0.0+

Installation

The server ships on PyPI as collusion-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Credentials and setup notes

Configuration is passed through the environment: DEEPSEEK_API_KEY, OPENAI_API_KEY, LLM_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Collusion's toolset — Roadmap — is a fair guide to whether it matches your workflow. It is maintained by nideweilaiya; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
RoadmapSee [ROADMAP.md](ROADMAP.md) for the full public roadmap covering v0.4.0 through v1.0.0+.

How to install the Collusion MCP server

{
  "mcpServers": {
    "collusion": {
      "command": "uvx",
      "args": ["collusion-mcp"],
      "env": {
        "DEEPSEEK_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value",
        "LLM_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
DEEPSEEK_API_KEYCredential the server authenticates with.Yes
OPENAI_API_KEYCredential the server authenticates with.Yes
LLM_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Collusion to Roadmap.

Frequently asked questions

It connects Collusion to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Roadmap) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Collusion directly.