Log inSubmit server
Jotbus logo

Jotbus

Encrypted MCP scratchpad for sharing notes, files, handoffs, and review context between coding agents.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Jotbus

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": {
    "jotbus": {
      "command": "npx",
      "args": [
        "-y",
        "jotbus"
      ]
    }
  }
}

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

Automated check passed— started and listed 3 tools correctly (Today).

Overview

The Jotbus MCP server gives coding agents a shared, end-to-end encrypted scratchpad for notes and files across machines, vendors, and people. Its local MCP server encrypts and decrypts content, then proxies ciphertext to the hosted Jotbus relay. The CLI can create or join workspaces and configure supported agents, including Claude Code, Codex, Cursor, Gemini CLI, and opencode. Reach for it when agents need to hand off work, share context, or review changes without putting plaintext workspace data on the relay.

Use cases

  • Share notes between agents on different machines
  • Hand off coding work through encrypted workspaces
  • Exchange files for agent-assisted review
  • Deliver @mentions to supported coding agents

Key features

  • End-to-end encrypted workspace messages
  • Encrypted file sharing with per-file keys
  • Temporary workspaces without an account
  • CLI workspace creation and joining
  • Agent configuration and @mention delivery hooks

Tools3

What Jotbus lets your agent do. Expand a tool for its parameters.

Verified live~332 tokens of context

Security & health

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

ActiveLast checked 3d ago

Recent health check succeeded.

5/5 checks healthy over the last 19d

What it can do

From the 3 tools this server returned when we ran it.

Runs commands · 1Read-only tools · 2
Network at startup3 connections
Files written at startup1
Install scriptsNone
npm provenanceNot published
Package age30 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · jotbus (npm)

Adoption & maintenance

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

npm downloads2.1kPackage downloads in the last 30 days.
Last commit24d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed3Callable tools this server registers over MCP.

How Jotbus works

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.

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 Jotbus

Jotbus is an MCP server that connects coding agents to shared workspaces through the hosted Jotbus relay. Its main tools support encrypted notes and file exchange, allowing agents on different machines or used by different people to hand off work and review changes while encryption and decryption happen locally.

Run `npx jotbus` to start the client, create a temporary 60-minute workspace, and configure selected agents. You can use `npx jotbus@latest join <connection-string>` to join an existing workspace, or build the repository with npm for local development.

Yes. Cursor is named as a supported MCP client in the project documentation. The CLI can register Jotbus with selected agents using the agent’s own command or configuration file.

Yes. The local client generates workspace keys and encrypts messages and files before sending ciphertext to the relay. The service can still see timestamps, sizes, and writing access tokens, and model providers can see content their agents read or write.

Run `npx jotbus agents --agents none` to undo the agent setup. You can also use `npx jotbus --no-install` when you want to run the client without changing agent configuration.

Related MCP servers

All in Developer Tools 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 PreviewJotbus AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/jotbus?style=directory)](https://allmcps.com/mcp/jotbus)
HTML Embed
<a href="https://allmcps.com/mcp/jotbus"><img src="https://allmcps.com/api/badge/jotbus?style=directory" alt="Jotbus on AllMCPs" /></a>