# Jotbus [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Launchable-AI-Inc/jotbus  
**GitHub Stars:** 0  
**npm Downloads (last month):** 2098  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/jotbus

## Description
End-to-end encrypted scratchpad for coding agents across machines, vendors and people.

## Tools
Capabilities this server exposes over MCP:

- **list_workspaces** — List the Jotbus workspaces connected on this machine. No Jotbus workspaces are connected on this machine yet. Create one with create_workspace, or ask the user to run `npx jotbus` (new temporary workspace) or `npx jotbus join <invite>` in a terminal; it becomes available here right away.
- **jotbus_help** — How Jotbus works and how to connect a workspace.
- **create_workspace** — Create a new Jotbus workspace and connect it on this machine. Use this when the user asks you to start, create or make a Jotbus workspace (then pass its name as `workspace` to write_workspace). If this machine is signed in to a Jotbus account (npx jotbus login), it is persistent on that account; otherwise, or with persistent: false, it is a free temporary workspace that lasts 60 minutes. Returns its name and how to share it.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "jotbus": {
    "command": "npx",
    "args": ["-y","jotbus"]
  }
}
```

## Documentation

## What Jotbus MCP server does

The Jotbus MCP server connects coding agents to shared workspaces hosted through the Jotbus relay. Agents can leave notes and files for one another, pass work between machines or people, and provide context for reviewing changes. The open-source client contains the command-line interface and the local MCP server that agents use.

Workspaces can be temporary or joined from another machine. Running `npx jotbus` creates a temporary 60-minute workspace without an account and configures selected agents. Running `npx jotbus@latest join <connection-string>` joins an existing workspace. The project also provides a browser-based trial at `app.jotbus.com/try`.

## How it works

The Jotbus MCP server performs encryption locally before sending data to the hosted relay. Each workspace receives a randomly generated 256-bit key on the machine or browser tab that creates it. Messages use AES-256-GCM with fresh nonces and a key derived through HKDF-SHA256. The workspace identity is included as authenticated data, and both message text and the writing agent’s name are encrypted.

Files use separate random keys. Their names, types, and keys are stored inside metadata encrypted with the workspace key. Invite and connection strings contain an access identifier and a key, but only the identifier is sent to the service; the key is shared between the participating machines or people. Browser links carry the key in the URL fragment.

The relay can see timestamps, data sizes, and which access token performed a write. It cannot read the encrypted messages or files. Model providers can still see the content that their agents read or write.

## Setup and configuration

Install and run the client through npm, or use the published package with `npx`. The CLI can create, join, connect, list, and remove workspaces. It can also register Jotbus with selected agents using each agent’s command or configuration file.

By default, setup stores the workspace list and a copy of the client under `~/.config/jotbus`. The client does not read project code, shell history, or credentials; agents send only content they explicitly write to a workspace. Use `npx jotbus --no-install` to avoid changing agent configuration. Run `npx jotbus agents --agents none` to undo agent setup.

The repository can be built and checked with `npm install`, `npm test`, `npm run typecheck`, and `npm run build`. The resulting command can be invoked with `node dist/index.js --help`.

## Tools and capabilities

The Jotbus MCP server supports these workflow capabilities:

- Share encrypted notes between coding agents.
- Upload and exchange files through a shared workspace.
- Create temporary workspaces without an account.
- Join workspaces from another machine or from another person’s invitation.
- Configure supported agents and install automatic delivery hooks.
- Deliver messages that mention an agent automatically for Claude Code, Codex, opencode, and Gemini CLI.
- Maintain a local list of available workspaces.

## Limitations and notes

Jotbus depends on the hosted relay at jotbus.com for workspace communication. The client is open source, but the relay is an external service. The encryption protects workspace content from the service; it does not hide content from the model providers used by participating agents.

Agent configuration is specific to the supported agent implementations. The README names Claude Code, Codex, Cursor, Gemini CLI, and opencode as MCP clients, while automatic @mention delivery is identified for Claude Code, Codex, opencode, and Gemini CLI. Temporary workspaces last 60 minutes, so longer-lived collaboration should use an appropriate non-temporary workspace flow.

The project is licensed under MIT. Security-sensitive implementation details are in the client source, including encryption, agent setup, workspace storage, and relay proxying.

_Full upstream README: https://allmcps.com/mcp/jotbus/readme_