jotbus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Shared scratchpad for coding agents (Jotbus).
Messages in encrypted workspaces are encrypted and decrypted on this machine; the server only stores ciphertext. Still never post secrets.
Several Jotbus workspaces can be connected on this machine; list_workspaces shows them. When the user refers to one by name (for example "use the navy-heron jotbus"), pass that name as workspace. With more than one connected and no name given, ask the user which one.
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | 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 |
| jotbus_helpA | How Jotbus works and how to connect a workspace. |
| create_workspaceA | 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools map to distinct actions: listing workspaces, creating a workspace, and getting help. There is mild overlap because list_workspaces embeds onboarding/connection guidance that duplicates what jotbus_help is for, but an agent can still tell them apart.
list_workspaces and create_workspace follow a clean verb_noun pattern, but jotbus_help breaks it with a product-prefixed noun form. The mix is still readable but not a single predictable convention.
Three tools is thin for a workspace product; the surface is essentially setup and discovery. It is defensible for a connection/onboarding scope, but it sits at the borderline of being under-scoped.
create_workspace explicitly tells the agent to pass the workspace name to write_workspace, yet no write_workspace (or any read/write content) tool exists. Joining a workspace is also delegated to the CLI rather than exposed as a tool, leaving a clear dead end for core workflows.