Proletariat Cli
Wire your coding agent into Proletariat so it can spawn workers, manage tickets on boards, and run multi-step workflows from the IDE.
Overview
Proletariat CLI is an MCP server for the Build phase that exposes multi-agent spawning, tickets, boards, and workflows to your coding agent.
What is this MCP server?
- stdio MCP package @proletariat/cli (npm) at version 0.3.99
- Multi-agent spawning coordinated through the Proletariat platform
- Ticket and board operations for agent-driven task tracking
- Workflow hooks for chaining autonomous work across agents
- GitHub source under apps/cli in the proletariat monorepo
- Server schema version 2025-12-11; package version 0.3.99
- Single npm package @proletariat/cli with stdio transport
- Repository subfolder apps/cli on github.com/chrismcdermut/proletariat
Community signal: 34 GitHub stars.
What problem does it solve?
One agent thread cannot safely track parallel tasks, handoffs, and board state while you ship features solo.
Who is it for?
Indie builders orchestrating several coding agents with shared tickets and boards on Proletariat.
Skip if: Teams that only need inline chat with no external work tracking or multi-agent platform.
What do I get? / Deliverables
Your agent can create and move tickets, spawn workers, and drive Proletariat workflows directly from MCP tool calls.
- Registered stdio MCP server for Proletariat orchestration
- Agent-callable tools for spawning agents and managing tickets/boards
- Repeatable multi-agent workflows driven from the IDE
Recommended MCP Servers
Journey fit
Orchestration sits in Build because you adopt it while wiring agent stacks and shipping automation, not during early idea research. agent-tooling is the canonical shelf for MCP servers that expose spawn, ticket, and workflow primitives to Claude Code–class agents.
How it compares
MCP orchestration bridge to Proletariat, not a standalone planning or brainstorming skill.
Common Questions / FAQ
Who is Proletariat CLI for?
Solo and small teams using AI coding agents who already use or plan to use Proletariat for multi-agent work, tickets, and boards.
When should I use Proletariat CLI?
Use it during Build when you want your IDE agent to spawn sub-agents, file tickets, and advance workflows without leaving MCP.
How do I add Proletariat CLI to my agent?
Install @proletariat/cli from npm, add a stdio MCP server entry pointing at that package, restart Claude Code or Cursor, and verify tool calls against your Proletariat instance.