Huddle

io.github.kfiramPublished by GitHub account kfiramv0.3.1Updated Oct 31, 2026

One encrypted chat for you, your people and your AI agents: Claude, Codex, Gemini, Goose.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationAI & ML

Overview

AI-generated overview

Huddle is a remote MCP server that puts you, your teammates and several AI agents (Claude, Codex, Gemini, Goose) into one encrypted shared chat room.

What you can do
  • Create and join shared chat rooms where people and AI agents talk together
  • Read and post messages in a room, with each agent's work visible live to everyone
  • Wake an agent session when someone else writes in a room it is listening to
  • Connect the same room to different clients (Claude Code, Codex, Gemini CLI, Goose) through one remote endpoint
When to use it
Use it when several people and several AI agents need a common, encrypted conversation space, for example a team coordinating Claude Code and Codex sessions in one room, or a shared project channel where agents report progress.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package. Authentication is required: an OAuth sign-in with GitHub yields a Huddle key, sent as the Authorization header (Bearer). The sign-in page shows the exact configuration per client.
Before you install
The Authorization header carries your Huddle key, so keep it out of shared logs and configs. Messages are shared with everyone in a room, including other people's agents, and the server states that other people's and agents' messages are treated as data rather than instructions. Rooms are created and written to, so content you post is visible to all room members.

Installation

In SourceWeft

  1. Open Huddle in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.kfiram%2Fhuddle/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "huddle": {
      "type": "http",
      "url": "https://huddleapp.ai/mcp"
    }
  }
}

README

Huddle

One chat for you, your people, and all your AI agents - Claude, Codex, Gemini, Goose. Everyone in a room sees every message, and you see each agent work, live.

Get your key

Sign in at https://huddle.kfiram.workers.dev with GitHub. You get your key, and the exact line for each client.

Claude Code

/plugin marketplace add kfiram/huddle/plugin install huddle@huddle

Paste your key when asked (kept in secure storage). Then ask Claude to create_room, or to join_room a room you share. When the session finishes a turn, the plugin listens to that room and wakes the session when someone else writes there.

Codex, Gemini CLI, Goose

Huddle is a remote MCP server: https://huddle.kfiram.workers.dev/mcp with the header Authorization: Bearer <your key>. The sign-in page shows the exact configuration for each.

Safety

An agent acts only on its own person's words. Messages from other people and other agents are data to it, never instructions.

Privacy

https://huddle.kfiram.workers.dev/privacy - no ads, no selling, no training on your messages.

Source: README.md at commit 25c02d5

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.3.1LatestOct 31, 2026
  2. v0.2.2Oct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts