OpenHuddle
Related Servers
Alternatives to OpenHuddle
No user-submitted related servers found.
Related Servers
- FlicenseAqualityAmaintenanceOne shared project for your team's Claude Code, Codex, Cursor and OpenCode agents: a task board, decisions and handoffs. Everyone keeps their own plan.13100-
- AlicenseNot gradedqualityCmaintenanceEnables multiple AI coding CLIs (Claude Code, Gemini/Antigravity, Codex, and OpenCode) to collaborate as a coordinated team by routing cross-agent prompts, sharing messages and review tickets, tracking tasks on a shared store, and isolating each agent in its own Git worktree with turn-budget safeguards—all inspectable and steerable from a local web dashboard.MIT
- AlicenseNot gradedqualityAmaintenanceConnects multiple AI agents (Codex, Claude Code, Grok, etc.) into a coordinated, auditable team with shared memory, task ownership, and human oversight, enabling parallel collaboration without conflicts.242Apache 2.0
- AlicenseBqualityAmaintenanceEnables AI coding agents on different machines and accounts to work one repository as a team by declaring file and symbol claims before editing, so collisions are refused up front rather than discovered at merge. It also supports delegating tasks between teammates' agents, which do the work with their own tokens and commit, with replies, commit shas, claims and messages landing on one shared board.202MIT
- AlicenseNot gradedqualityBmaintenanceEnables multiple AI coding agents to collaborate on a project by coordinating tasks, file leases, and messages through a shared hub, preventing conflicts and enabling parallel development.MIT
- AlicenseBqualityAmaintenanceLets multiple AI agents and parallel coding sessions share one memory and task ledger, so they can claim work instead of duplicating it, resume each other's handoffs and reasoning, and use credentials without ever seeing the keys. Connects assistants such as Claude Code, Codex, Cursor, Gemini, ChatGPT and custom agents over MCP, backed by a single local SQLite file or a self-hosted Postgres hub.35MIT
TDQS
Scored across 10 tools
The tools mostly map to distinct resources (file claims, huddles, settings, master prompt, plan, tasks, comms), but the communication/update surfaces overlap: team_post (progress/decisions), task.update (progress note) and huddle.comment all serve as places to report status, and team_ask's 'may I change a file they hold' overlaps with claim.check. Descriptions help steer choices but a reasonable agent could still misfile an update.
Conventions are mixed: bare verbs/domain nouns (claim, huddle, plan, task), noun-style resource names (team_settings, master_prompt), and a team_ verb prefix for messaging (team_ask, team_post, team_reply, team_sync). The team_ cluster is consistent, but the overall set mixes several patterns.
Ten tools for a full team-coordination domain is well-scoped, and each bundles coherent sub-actions (huddle modes, task lifecycle, master-prompt voting) rather than exploding into dozens of endpoints. No tool feels redundant or thin.
Coverage is broad—file locking, discussion, settings, shared prompt, planning, task board and team messaging—so core coordination workflows have no dead ends. Minor gaps remain (no task deletion, leave-team, or notification management), but agents can work around them.