Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Agent orchestration platform - multi-agent spawning, tickets, boards, and workflows
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"proletariat-cli": {
"command": "npx",
"args": [
"-y",
"@proletariat/cli"
]
}
}
}Run this in your terminal
claude mcp add proletariat-cli -- npx -y @proletariat/cliPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"proletariat-cli": {
"command": "npx",
"args": [
"-y",
"@proletariat/cli"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"proletariat-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@proletariat/cli"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account chrismcdermut, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.134) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
██████╗ ██████╗ ██████╗ ██╗ ███████╗████████╗ █████╗ ██████╗ ██╗ █████╗ ████████╗
██╔══██╗██╔══██╗██╔═══██╗██║ ██╔════╝╚══██╔══╝██╔══██╗██╔══██╗██║██╔══██╗╚══██╔══╝ ██████╔╝██████╔╝██║ ██║██║ █████╗ ██║ ███████║██████╔╝██║███████║ ██║ ██╔═══╝ ██╔══██╗██║ ██║██║ ██╔══╝ ██║ ██╔══██║██╔══██╗██║██╔══██║ ██║ ██║ ██║ ██║╚██████╔╝███████╗███████╗ ██║ ██║ ██║██║ ██║██║██║ ██║ ██║ ╚═╝ ╚═╝ ╚═╝ ╚═════╝ ╚══════╝╚══════╝ ╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝╚═╝ ╚═╝ ╚═╝
Agent orchestration platform for AI labor. Spin up workers for all work, on demand.
Themed agents, including billionaires - Finally, they work for us.
⚠️ Beta Software — Under active development. Commands and APIs may change between versions, and bugs are actively being squashed.
Let's get you shipping Book a call - I'm happy to help you get prlt running or chat feedback, ideas, multi-agent workflows, and the future of work/labor (and economic labor theory..)
prlt is an agent orchestration platform for AI labor. Spin up workers on demand, coordinate multi-agent development from one CLI. Isolated workspaces, secure containers, persistent state.
brew install chrismcdermut/proletariat/prlt # macOS (Homebrew)
npm install -g @proletariat/cli # any platform (npm)
prlt new prlt ticket create --title "Add OAuth" --category feature prlt work spawn # Interactive: select tickets, environment, action
Agent spawns in its own branch, writes code, opens PR. You review and merge.
Why prlt?
--json mode lets AI agents drive the CLI programmatically.brew install chrismcdermut/proletariat/prlt # Install (Homebrew, recommended)
npm install -g @proletariat/cli # Install (npm, all platforms)
prlt new # Create HQ, add repos, choose theme prlt ticket create --title "Add OAuth" --category feature prlt work spawn # Interactive: select tickets, environment, action
Workflow Diagram (click to expand)
sequenceDiagram
participant You participant prlt participant Agent participant GitHub
You->>prlt: prlt ticket create You->>prlt: prlt work spawn prlt->>prlt: Create branch prlt->>prlt: Create workspace prlt->>Agent: Spawn agent Agent->>Agent: Read ticket Agent->>Agent: Write code Agent->>GitHub: Commit Agent->>GitHub: Open PR Agent->>prlt: Update status prlt->>You: PR ready You->>GitHub: Review & approve
Spawn agents to implement, groom, or review—not just write code.
prlt work guides you through project and ticket selection:
Choose your operation—start a single agent, batch spawn, or watch a column:
Select tickets to spawn, grouped by priority:
| Problem | Solution |
|---|---|
| Agents conflict with each other's changes | Isolated - Each agent gets its own git branch and worktree |
| Agents run unsandboxed on your machine | Secure - Docker containers, sandboxed from your host (looking into host sandbox options) |
| You lose track of who's doing what | Trackable - All state in one SQLite database, one CLI |
| Sessions die when you close a window | Durable - Tmux sessions persist, detach/reattach anytime |
| Context scattered across chat windows | Structured - Tickets with requirements, acceptance criteria |
| Starting agents is heavyweight | Ephemeral - Spawn on demand, they work, they PR, they're done |
| Context lost between agent runs | Persistent - Tickets accumulate context, hand off between agents |
brew install chrismcdermut/proletariat/prlt
Works on both Apple Silicon (arm64) and Intel (x86_64) Macs. No compiler needed.
Upgrade:
brew update
brew upgrade prlt
npm install -g @proletariat/cli
pnpm install -g @proletariat/cli
pnpm 10+ note: pnpm 10 blocks native addon build scripts by default. If
prltfails with a native module error after install, runpnpm approve-buildsin the global store and reinstall, or usenpm/brewinstead.
Verify:
prlt --version
prlt includes a built-in MCP server with 100+ tools. Add it to your AI client:
Claude Code (~/.claude.json):
{
"mcpServers": { "prlt": { "command": "prlt", "args": ["mcp-server"] } } }
Cursor / Other clients (via npx):
{
"mcpServers": { "prlt": { "command": "npx", "args": ["-y", "@proletariat/cli", "mcp-server"] } } }
Listed on: MCP Registry | npm
Workspace (HQ)
├── Projects │ ├── Epics → Tickets │ └── (references a Workflow) ├── Workflows → Phases → Statuses (can be shared across projects) ├── Specs (can span projects) ├── Actions (reusable templates) ├── Agents │ ├── Staff (persistent, named) │ └── Temp (ephemeral, per-ticket) └── Executions (running sessions) ├── Docker │ ├── Tmux session │ ├── Terminal or Background display │ └── Safe or YOLO permissions └── Host ├── Tmux session ├── Terminal or Background display └── Safe or YOLO permissions
| Entity | Description |
|---|---|
| Project | Groups tickets and epics, references a workflow |
| Epic | Work container with lifecycle (draft → active → complete) |
| Ticket | Individual work item with requirements and acceptance criteria |
| Spec | Static documentation (can span projects, linked to epics) |
| Workflow | Status flow configuration (can be shared across projects) |
| Phase | Stage in a workflow |
| Status | Ticket state within a phase |
| Action | Reusable prompt/action templates |
| Agent (Staff) | Persistent named agent with dedicated workspace |
| Agent (Temp) | Ephemeral agent spawned for a single ticket |
| Execution | Running agent session on a ticket |
| Display | Terminal (new tab) or Background (detached) |
A workflow defines how tickets move through your process. Projects reference a workflow, and multiple projects can share the same one.
Kanban Workflow
├── Backlog # New tickets land here ├── In Progress # Agent working (prlt work spawn) ├── Review # PR ready (prlt work ready) └── Done # Merged (prlt work complete)
Scrum Workflow ├── Backlog ├── Sprint │ ├── To Do │ ├── In Progress │ └── In Review └── Done
Tickets flow through statuses as work progresses. Agents automatically move tickets when they start work, open PRs, or complete tasks.
Each agent gets a copy of all repos (repo scoping coming soon). Work happens on isolated branches.
my-project/
├── .proletariat/ │ └── workspace.db # Tickets, executions, state ├── repos/ │ ├── frontend/ # Your repos │ ├── backend/ │ └── infra/ └── agents/ ├── staff/ │ └── alice/ # Named agent with persistent workspace │ ├── frontend/ │ ├── backend/ │ └── infra/ └── temp/ ├── agent-abc123/ # Ephemeral: Working on TKT-042 (OAuth) │ ├── frontend/ # All repos on branch: feat/TKT-042-oauth │ ├── backend/ │ └── infra/ └── agent-def456/ # Ephemeral: Working on TKT-043 (API) ├── frontend/ # All repos on branch: feat/TKT-043-api ├── backend/ └── infra/
Themes control how agents are named. Staff agents use theme names directly (e.g., bezos, camry). Ephemeral agents add an adjective prefix (e.g., bold-bezos, keen-camry). Currently ephemeral names also include a number suffix (bold-bezos-1), but this will be removed soon.
Built-in Themes:
| Theme | Description | Example Names |
|---|---|---|
billionaires | Tech founders & executives (default) | musk, gates, bezos |
toyotas | Toyota vehicle models | camry, supra, tacoma |
companies | Major tech companies | stripe, vercel, linear |
_billionaires_ — Finally, they work for us.
Theme Commands:
prlt agent themes list # List available themes
prlt agent themes set billionaires # Set active theme prlt agent themes create mytheme # Create custom theme prlt agent themes add-names mytheme # Add names to custom theme
Themes are selected during prlt new.
Run without flags—get guided prompts:
$ prlt ticket create
? Title: Add password reset ? Description: Email-based password reset flow ? Priority: P1 ? Category: feature
✓ Created TKT-043
View ticket details with prlt ticket:
Add --json for machine-readable output:
$ prlt work start --json
{
"prompt": { "type": "list", "message": "Select ticket to work on:", "choices"
Only the beginning is shown; read the rest in the repo