Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Agent orchestration platform - multi-agent spawning, tickets, boards, and workflows
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"proletariat-cli": {
"command": "npx",
"args": [
"-y",
"@proletariat/cli"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add proletariat-cli -- npx -y @proletariat/cliPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"proletariat-cli": {
"command": "npx",
"args": [
"-y",
"@proletariat/cli"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"proletariat-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@proletariat/cli"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub chrismcdermut, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.3.134) llegó al registro hace 6 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
██████╗ ██████╗ ██████╗ ██╗ ███████╗████████╗ █████╗ ██████╗ ██╗ █████╗ ████████╗
██╔══██╗██╔══██╗██╔═══██╗██║ ██╔════╝╚══██╔══╝██╔══██╗██╔══██╗██║██╔══██╗╚══██╔══╝ ██████╔╝██████╔╝██║ ██║██║ █████╗ ██║ ███████║██████╔╝██║███████║ ██║ ██╔═══╝ ██╔══██╗██║ ██║██║ ██╔══╝ ██║ ██╔══██║██╔══██╗██║██╔══██║ ██║ ██║ ██║ ██║╚██████╔╝███████╗███████╗ ██║ ██║ ██║██║ ██║██║██║ ██║ ██║ ╚═╝ ╚═╝ ╚═╝ ╚═════╝ ╚══════╝╚══════╝ ╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝╚═╝ ╚═╝ ╚═╝
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"
Solo se muestra el principio; lee el resto en el repo