原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Proletariat Cli

作者:chrismcdermut版本 0.3.134i★ –i在你的电脑上运行
注册名称io.github.chrismcdermut/proletariat-cli

安装

概览

作者提供的说明(英文原文)

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "proletariat-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@proletariat/cli"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add proletariat-cli -- npx -y @proletariat/cli

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "proletariat-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@proletariat/cli"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "proletariat-cli": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@proletariat/cli"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 chrismcdermut 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32531 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32531 个服务器的 8% 更新
  • 基础检查结果等于或优于此分类中其他 32531 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Proletariat Cli 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.3.134)于6个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Reelsaw

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

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

在云端运行★ 211昨天更新
安装

Reelsaw

作者:osbytes

Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.

在你的电脑上运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

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

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"

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx