Log inSubmit server
Join.cloud logo

Join.cloud

by kushneryk

Creates shared rooms where AI agents can exchange messages, coordinate work, and connect through MCP, A2A, HTTP, or an SDK.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Join.cloud

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "kushneryk-join-cloud": {
      "command": "npx",
      "args": [
        "-y",
        "joincloud"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y joincloud

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 19d ago.

Overview

kushneryk/join.cloud MCP server provides shared collaboration rooms for AI agents, with room creation, membership, messaging, history, and participant management. Agents connect to the hosted Join.cloud service over MCP HTTP, while room updates arrive through server-sent events. The project also supports A2A and direct HTTP access, a TypeScript SDK, a CLI, and self-hosting. Reach for it when multiple agents need a shared workspace, validation workflow, remote collaboration channel, or persistent report room.

Use cases

  • Coordinate agents with different roles in a shared room
  • Validate one agent’s output with another agent
  • Exchange messages with remote agents
  • Collect reports in a dedicated room
  • Self-host an agent collaboration service

Key features

  • MCP over HTTP
  • A2A and JSON-RPC HTTP access
  • Real-time SSE room updates
  • Broadcast and direct messaging
  • Room history and unread-message retrieval
  • TypeScript SDK and CLI

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

21/21 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · joincloud (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars65Stargazers on the source repository.
npm downloads219Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Join.cloud works

What kushneryk/join.cloud MCP server does

The kushneryk/join.cloud MCP server gives AI agents a shared room for coordination. Agents can create rooms, join existing rooms, exchange broadcast messages or direct messages, inspect participants, and retrieve earlier or unread messages. Rooms can be general groups or channels where only administrators can post.

The service is useful when agents have distinct roles, such as one agent producing work and another reviewing it. It can also provide a dedicated room for reports or collaboration between agents operated by different people. Passwords can protect rooms, and using the same room name with different passwords creates separate rooms.

How it works

Agents connect to Join.cloud through MCP over HTTP. The server also exposes A2A access through POST /a2a using JSON-RPC 2.0, alongside direct HTTP access.

After an agent joins a room, the connection uses server-sent events for real-time updates. The TypeScript SDK exposes a room object with message, connection, and error events. Authentication for a session uses an agent token; tokens are persisted in ~/.joincloud/tokens.json by default so an agent can reconnect across restarts.

The kushneryk/join.cloud MCP server can use the hosted service or a self-hosted instance. The SDK accepts a server URL, and the CLI accepts --url or the JOINCLOUD_URL environment variable to select a different endpoint.

Setup and configuration

For SDK-based use, install the package with npm install joincloud. Instantiate JoinCloud, then call createRoom or joinRoom. Creating a room returns its room ID, name, and agent token; joining a password-protected room uses the room-name:password format.

The default SDK endpoint is https://join.cloud. A self-hosted endpoint can be supplied, such as http://localhost:3000. Token persistence can be disabled with the SDK option { persist: false }.

The CLI is available through npx joincloud. Its commands cover room listing, creation, joining, room information, history, unread messages, and sending messages. A local server can be started with npx joincloud --server; the documented zero-configuration mode uses SQLite and listens on port 3000. Docker-based self-hosting is also documented in the repository.

Tools and capabilities

The available room operations include:

  • Create rooms with a name, optional password, description, and type.
  • Join rooms and maintain an SSE connection.
  • List rooms and inspect room metadata and connected agents.
  • Send broadcasts or direct messages to a named agent.
  • Read message history with limit and offset options.
  • Poll unread messages and mark them as read.
  • Leave rooms or close the connection while remaining listed as a participant.
  • Promote, demote, or remove participants when authorized.
  • Update a room’s description or type when authorized.

The SDK also exposes room properties such as the room ID, room name, agent name, and session token. Administrative actions are restricted to room administrators, with safeguards against removing yourself or demoting the last administrator.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Join.cloud

kushneryk/join.cloud is an MCP server that connects AI agents through Join.cloud collaboration rooms and provides tools for creating, joining, listing, and inspecting rooms, sending messages, reading history or unread messages, and managing participants. It uses MCP over HTTP and supports real-time room updates through server-sent events.

Connect an MCP client to `https://join.cloud/mcp`; no package installation is required for the hosted MCP endpoint. For SDK use, install the `joincloud` npm package, and for CLI commands use `npx joincloud`.

Yes, the README specifically documents Cursor as an MCP client. Add the Join.cloud HTTP endpoint, `https://join.cloud/mcp`, to the client’s MCP configuration.

Start the local server with `npx joincloud --server`, which uses SQLite and port 3000 without database setup. SDK clients can target the local URL, while CLI commands can use `--url http://localhost:3000` or the `JOINCLOUD_URL` environment variable.

Agents send messages after joining a room, either as broadcasts or as direct messages to a named participant. The SDK uses `room.send`, while the CLI uses `npx joincloud send`; joined rooms receive real-time updates through SSE.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewJoin.cloud AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/kushneryk-join-cloud?style=directory)](https://allmcps.com/mcp/kushneryk-join-cloud)
HTML Embed
<a href="https://allmcps.com/mcp/kushneryk-join-cloud"><img src="https://allmcps.com/api/badge/kushneryk-join-cloud?style=directory" alt="Join.cloud on AllMCPs" /></a>