Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Proletariat Cli

by chrismcdermutversion 0.3.134i★ –iRuns on your computer
Registry nameio.github.chrismcdermut/proletariat-cli

Install

Overview

Description from the maker (original English)

Agent orchestration platform - multi-agent spawning, tickets, boards, and workflows

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

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/cli

Open in Cursor

Or copy the settings yourself

Paste 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.

Open in VS Code

Or copy the settings yourself

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.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account chrismcdermut, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32466 servers in this category
  • Published to the registry more recently than 8% of the other 32466 servers in this category
  • Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Proletariat Cli safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.134) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

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.

██████╗ ██████╗  ██████╗ ██╗     ███████╗████████╗ █████╗ ██████╗ ██╗ █████╗ ████████╗

██╔══██╗██╔══██╗██╔═══██╗██║ ██╔════╝╚══██╔══╝██╔══██╗██╔══██╗██║██╔══██╗╚══██╔══╝ ██████╔╝██████╔╝██║ ██║██║ █████╗ ██║ ███████║██████╔╝██║███████║ ██║ ██╔═══╝ ██╔══██╗██║ ██║██║ ██╔══╝ ██║ ██╔══██║██╔══██╗██║██╔══██║ ██║ ██║ ██║ ██║╚██████╔╝███████╗███████╗ ██║ ██║ ██║██║ ██║██║██║ ██║ ██║ ╚═╝ ╚═╝ ╚═╝ ╚═════╝ ╚══════╝╚══════╝ ╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝╚═╝ ╚═╝ ╚═╝

Seize the means of production - Ship 100x.

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..)


TLDR

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)

or

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?

  • Isolated - Each agent gets its own git branch. No conflicts.
  • Secure - Docker containers, sandboxed from your host.
  • Durable - Tmux sessions persist. Close window, agent keeps working.
  • Trackable - One database, one CLI, all your agents.
  • Ephemeral - Spawn agents on demand. They work, they PR, they're done.
  • Structured - Tickets provide structured context, not freeform chat.
  • Persistent - Tickets accumulate context over time. Hand off between agents.
  • Agent-native - --json mode lets AI agents drive the CLI programmatically.

Quick Start

brew install chrismcdermut/proletariat/prlt  # Install (Homebrew, recommended)

or

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

Agent creates PR → You review → Merge → Done

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.

Interactive Menus

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:


Deep Dive

ProblemSolution
Agents conflict with each other's changesIsolated - Each agent gets its own git branch and worktree
Agents run unsandboxed on your machineSecure - Docker containers, sandboxed from your host (looking into host sandbox options)
You lose track of who's doing whatTrackable - All state in one SQLite database, one CLI
Sessions die when you close a windowDurable - Tmux sessions persist, detach/reattach anytime
Context scattered across chat windowsStructured - Tickets with requirements, acceptance criteria
Starting agents is heavyweightEphemeral - Spawn on demand, they work, they PR, they're done
Context lost between agent runsPersistent - Tickets accumulate context, hand off between agents
Installation
Homebrew (recommended)
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 / pnpm (all platforms)
npm install -g @proletariat/cli

or

pnpm install -g @proletariat/cli

pnpm 10+ note: pnpm 10 blocks native addon build scripts by default. If prlt fails with a native module error after install, run pnpm approve-builds in the global store and reinstall, or use npm / brew instead.

Verify:

prlt --version
MCP Server

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

Data Model
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

EntityDescription
ProjectGroups tickets and epics, references a workflow
EpicWork container with lifecycle (draft → active → complete)
TicketIndividual work item with requirements and acceptance criteria
SpecStatic documentation (can span projects, linked to epics)
WorkflowStatus flow configuration (can be shared across projects)
PhaseStage in a workflow
StatusTicket state within a phase
ActionReusable prompt/action templates
Agent (Staff)Persistent named agent with dedicated workspace
Agent (Temp)Ephemeral agent spawned for a single ticket
ExecutionRunning agent session on a ticket
DisplayTerminal (new tab) or Background (detached)
Example Workflow

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.

Workspace Structure

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/

Agent Naming Themes

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:

ThemeDescriptionExample Names
billionairesTech founders & executives (default)musk, gates, bezos
toyotasToyota vehicle modelscamry, supra, tacoma
companiesMajor tech companiesstripe, 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.

Three Ways to Use Commands
1. Interactive (Humans)

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:

2. JSON Mode (AI Agents)

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

Ask PopNx