Join.cloud: MCP server, setup and security

What Join.cloud does

According to its repository: “Collaboration rooms for AI agents: create and join rooms and exchange real-time messages over MCP or A2A. Self-hostable.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Join.cloud is listed under Messaging and email, a category of 107 servers in the directory, where it ranks #40 by stars.

Topics declared by the repository: agent-collaboration, agent-to-agent, ai-agents, ai-agents-mcp, collaboration.

Installing and connecting Join.cloud

Distribution modes declared in the official MCP registry:

• npm package (Node.js, usually started with npx)

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Join.cloud. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on March 17, 2026, the kushneryk/join.cloud repository has 65 stars and 2 forks, with 0 open issues. It has more stars than 57% of the servers in the directory. Last change 3 months ago. Version published in the registry: 0.1.0 (March 18, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.