Openhuddle

Name: Openhuddle
Author: nika110

by nika110version 0.4.1i★ –iRuns on your computer

Registry nameio.github.nika110/openhuddle

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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: Docs, sheets & office work

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?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Run this in your terminal

claude mcp add openhuddle -- npx -y openhuddle mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

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

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 nika110, 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 Docs, sheets & office worki

More stars than 0% of the other 2180 servers in this category
Published to the registry more recently than 63% of the other 2180 servers in this category
Basic checks equal to or better than 100% of the other 2180 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 Openhuddle 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.4.1) reached the registry 18 days 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: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

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

Agent-Native Calendar

by BuilderIO

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

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago

Install

MCP Server for Excel

by sbroenne

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

Runs on your computer★ 847MITUpdated 3 days ago

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.

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 say	What 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)

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.
Vote. Submitting starts a vote. With the default rule everyone approves, then it locks. Changing it later starts an amendment and a new vote.
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.
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.
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:

Kind	What it's for
`brainstorm`	An open question. Everyone adds ideas and backs or pushes back on the others'.
`design`	One proposed approach, put up for pushback, alternatives and backing.
`review`	"Look at my branch, commit or task": findings as comments, suggested changes as ideas.
`standup`	Everyone 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 Code	Codex	Cursor
Install	plugin or `npx`	`npx`	`npx`
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 ask	when 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.

Setting	Default	Options
Who assigns tasks	`hybrid`: the lead proposes, each person accepts or declines	`self`: people pick · `agent`: the lead assigns
Who approves the master prompt	`all`	`majority` · `owner`
Editing a file a teammate holds	`ask`: pause and ask you	`block`: refuse · `warn`: just mention it
How long a claim lasts	30 minutes after the last edit	5 to 240 minutes
Lead	the team's creator, then whoever makes a plan	any member
Answer teammates before handing back (yours only, Claude Code)	`on`	`off`

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

Symptom	Fix

| Your age

Only the beginning is shown; read the rest in the repo

Openhuddle

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

Why

What your agent can do now

How a project goes

How it works

What works where

Settings

Requirements

Commands

Updating

Uninstall

Troubleshooting