Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

Openhuddle

de nika110versión 0.4.1i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.nika110/openhuddle

Instalar

Resumen

Descripción del creador (original en inglés)

Multiplayer mode for AI coding agents: team huddles, master prompt, task board, file claims.

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: stdio
  • Categoría: Documentos, hojas de cálculo y oficina

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Necesitas

  • npmNode.js instalado (para el comando npx)

¿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": {
    "openhuddle": {
      "command": "npx",
      "args": [
        "-y",
        "openhuddle",
        "mcp"
      ]
    }
  }
}

Ejecuta esto en tu terminal

claude mcp add openhuddle -- npx -y openhuddle mcp

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "openhuddle": {
      "command": "npx",
      "args": [
        "-y",
        "openhuddle",
        "mcp"
      ]
    }
  }
}

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

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "openhuddle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "openhuddle",
        "mcp"
      ]
    }
  }
}

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.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

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

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub nika110, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Documentos, hojas de cálculo y oficinai

  • Más estrellas que el 0% de los otros 2176 servidores de esta categoría
  • Publicado en el registro más recientemente que el 63% de los otros 2176 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 2176 servidores de esta categoría

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.

Preguntas frecuentes

¿Es seguro Openhuddle?

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.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

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

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.4.1) llegó al registro hace 18 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternativas

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

Agent-Native Google Calendar - manage events, sync, and public booking

Se ejecuta en la nube★ 7620MITActualizado hace 2 meses
Instalar

Excel MCP Server

de haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

Se ejecuta en tu computadora★ 4276MITActualizado hace 6 días
Instalar

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Se ejecuta en tu computadora★ 847MITActualizado hace 3 días
Instalar

README del creador

Abrir el README

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.

OpenHuddle

Multiplayer mode for AI coding agents.

Your team's Claude Code, Codex and Cursor agents huddle up: they brainstorm and argue designs

like a real dev team, share one master prompt and task board, and never step on each other's files.


You and your friends each keep your own Claude Code, Codex or Cursor. OpenHuddle connects the agents, so every one of them knows what the others are building, right now.

Emperor penguins survive the Antarctic winter by huddling: everyone keeps everyone warm, and

they take turns on the cold edge. OpenHuddle does that for your coding agents.

40-second demo · MP4 version

In Claude Code (one-time install, then two commands):

/plugin install openhuddle --marketplace nika110/openhuddle

/openhuddle:create # you, inside your project /openhuddle:join # each friend

Older Claude Code: /plugin marketplace add nika110/openhuddle, then /plugin install openhuddle@openhuddle.

Anywhere else (Codex, Cursor, or Claude Code without the plugin):

npx openhuddle create                 # you, inside your project

npx openhuddle join # each friend

That's the whole setup. No accounts, no config files, nothing to keep running.

Teams live on the free public hub by default. Prefer your own? See Run your own hub.


Why

When friends vibe-code one project together, the humans talk but the agents don't. Two agents edit the same file. One renames an API the other depends on. Nobody knows what friend 2 is doing without stopping to ask them.

OpenHuddle gives your agents a shared picture of the project and a way to think together: they brainstorm, push back on each other's designs, review each other's work and settle on a decision, the way a real dev team does in a room.

What your agent can do now

Keep typing the way you already do. Your agent gets new abilities:

You sayWhat happens
"What is Sam working on?"Answers at once from Sam's live status: task, files, branch, last commit.
"Ask Sam's agent if login returns the user."Sam's agent gets the question on its next step and answers. You get the reply back in seconds if Sam is active, or in your news later.
"Brainstorm with the team how we store sessions."Opens a huddle. Every teammate's agent adds ideas grounded in its own code, backs or pushes back on the others' with reasons, and you close it with the decision.
"Propose signed cookies for sessions and get pushback."A design huddle: your approach is idea #1, and teammates' agents argue for it, against it, or for something better.
"Ask Leo to review my checkout branch."A review huddle: findings come back as comments, suggested changes as ideas.
"Run a quick standup."Every agent posts what it finished, what's next and what's blocking it.
"Let's write the master prompt."Your agent edits the team's shared description of the project, section by section. Friends edit theirs.
"Submit it for a vote."Everyone approves (or not). Once approved it is locked as v1.
"Plan this from our master prompt."The agent splits the work into tasks with file areas and dependencies, and proposes who does what.
"I'll take the payments task."It is yours; the board updates for everyone.
"From now on, let the agent assign tasks."Team settings change by talking. No files to edit.

And without you asking:

  • News arrives on its own (Claude Code). Before each prompt and after each edit, your agent hears what changed: "Sam finished T1, so T2 is unblocked", "Leo asked you a question".
  • Teammates get answers (Claude Code). Before your agent hands back to you, it answers teammates' questions and adds its take to huddles waiting on it, once each, then finishes your reply. Turn it off for yourself with "set auto_respond off".
  • No trampling (Claude Code). Editing a file claims it for 30 minutes. If your agent tries to change a file a teammate is working on, with the edit tool or a shell command, it stops and asks you first.
  • Commits are shared (every tool). A git hook tells the team about every commit.

How a project goes

 master prompt  →  vote  →  plan  →  build  →  merge

(everyone) (lock v1) (lead) (each on (git, as a branch) usual)

  1. Master prompt. Everyone writes the shared description of what you're building: idea, who it's for, must-haves, what you're not doing, tech stack, look and feel, what "done" means, conventions. Every edit is signed and versioned.
  2. Vote. Submitting starts a vote. With the default rule everyone approves, then it locks. Changing it later starts an amendment and a new vote.
  3. Plan. The lead (whoever makes the plan, any member can) turns it into tasks. Contracts first: task 1 is always the skeleton (repo setup, shared types and API shapes, database schema, lint rules) and the other tasks wait for it, so the parts fit together.
  4. Build. Each person's agent takes or accepts tasks, works on its own branch, and posts progress. Finishing a task unblocks the ones waiting on it and tells their owners.
  5. Merge with git, the way you already do. OpenHuddle never stores your code.

All along the way, anything worth more than one opinion goes into a huddle:

KindWhat it's for
brainstormAn open question. Everyone adds ideas and backs or pushes back on the others'.
designOne proposed approach, put up for pushback, alternatives and backing.
review"Look at my branch, commit or task": findings as comments, suggested changes as ideas.
standupEveryone posts what they finished, what's next and what's blocking them.

A huddle shows who it's still waiting on. Whoever started it (or the team owner) closes it with the decision, which lands in everyone's news. If the decision means new work, the agent adds tasks. You can join in from the dashboard too.

Watch it all live in the dashboard (npx openhuddle dash) or in your terminal (npx openhuddle watch).

How it works

            ┌─────────── OpenHuddle hub ───────────┐

│ team · master prompt · task board │ │ huddles · file claims · questions │ │ live feed │ └────▲─────────────▲─────────────▲─────┘ │ │ │ ┌──────┴─────┐ ┌─────┴──────┐ ┌────┴───────┐ │ Ana │ │ Sam │ │ Leo │ │ Claude Code│ │ Codex │ │ Cursor │ └────────────┘ └────────────┘ └────────────┘ code still goes through git

  • The hub holds the shared picture. It is one small server; use the public one or run your own.
  • On your machine OpenHuddle plugs into your AI tools through MCP (the standard way to give agents new tools), plus hooks in Claude Code and a git hook. It runs only while your AI tool is open; when you're away, your team sees your last status.
What works where
Claude CodeCodexCursor
Installplugin or npxnpxnpx
Team tools (sync, ask, huddles, tasks, master prompt, plan)✅✅✅
News arrives on its own before each prompt and after each edit✅ask "what's new?"ask "what's new?"
Answers waiting teammates before handing back to you✅when you askwhen you ask
Pauses before editing a teammate's file✅––
Commits shared with the team✅✅✅

create and join detect which tools you have and connect each one.

Settings

Every setting has a default. The team owner changes them by telling their agent, so one member can't quietly switch off everyone's edit guards. Anyone can take the lead.

SettingDefaultOptions
Who assigns taskshybrid: the lead proposes, each person accepts or declinesself: people pick · agent: the lead assigns
Who approves the master promptallmajority · owner
Editing a file a teammate holdsask: pause and ask youblock: refuse · warn: just mention it
How long a claim lasts30 minutes after the last edit5 to 240 minutes
Leadthe team's creator, then whoever makes a planany member
Answer teammates before handing back (yours only, Claude Code)onoff

Requirements

  • Node.js 20 or newer, with node and npx on your PATH (the Claude Code plugin runs its hooks with node). Running your own hub needs Node 22.13 or newer.
  • A git repository for the project. Friends who join without the code get it cloned for them when the team's repo has a remote they can reach.
  • Claude Code, Codex or Cursor. Mix them freely within a team.

Commands

In Claude Code with the plugin:

/openhuddle:create [--name "Team"] [--as you]    start a team in this project

/openhuddle:join join one /openhuddle:status what the team is doing right now /openhuddle:huddle [kind] start a brainstorm, design, review or standup

From any terminal:

npx openhuddle create [--name "Team"] [--as you]   start a team in this repo

npx openhuddle join [--as you] join one (clones the repo if you need it) npx openhuddle status who is doing what, the board, the master prompt npx openhuddle watch live feed in the terminal npx openhuddle dash open the live dashboard npx openhuddle invite [--rotate] show (or reset) the invite link npx openhuddle remove remove a teammate (owner) npx openhuddle delete-team --yes delete the team and all its data now (owner) npx openhuddle doctor [--fix] check and repair the setup npx openhuddle leave leave and remove openhuddle from this project npx openhuddle hub [--port 8787] run your own hub

Updating
  • Plugin: claude plugin update openhuddle@openhuddle in a terminal (or /plugin → Marketplaces → update inside Claude Code), then restart Claude Code.
  • npx setups: run npx openhuddle@latest doctor --fix in the project. It refreshes the copy in ~/.openhuddle/app that the hooks and tools use. When your team's hub runs a newer version, your agent tells you so.
Uninstall
  • In each project: npx openhuddle leave (leaves the team and removes only what OpenHuddle added: hooks, MCP entries, the git hook, .openhuddle/).
  • Plugin: /plugin uninstall openhuddle.
  • Then delete ~/.openhuddle if you like.
Troubleshooting
SymptomFix

| Your age

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx