MCP integration
Register buster7 as a tool for your agents
b7 mcp is a mode that offers buster7's operations as MCP tools. Register it
with Claude Code or Codex and the agent can make its own terminals, type into
them, and read the screen. The tools are the CLI underneath, so everything
CLI (b7) can do is available over MCP too.
Registering it
codex mcp add buster7 -- /path/to/server/target/debug/b7 mcp
claude mcp add buster7 -s user -- /path/to/server/target/debug/b7 mcp--server / --token are global options of b7 and can be passed here. When
they are omitted, the connection is resolved in the same order as the CLI, so
if you have set the connection in the app, no arguments are needed.
codex mcp add buster7 -- b7 mcp --server 127.0.0.1:8787 --token mytokenThe tools it offers (21)
| Tool | What it does |
|---|---|
status / server_status | A summary of the server and the sessions; the connection in use |
list_sessions / new_session / kill_sessions | List, create, and stop sessions |
send_input / resize / read_screen / search_screen | Drive and read the terminal |
chat | Send to the chat, and read its history |
list_projects / add_project / remove_project / pin_project / order_projects | Projects |
list_workspaces / new_worktree / remove_worktree | Workspaces |
list_files / read_file / list_dirs | Files and directories |
read_screen alone returns its content as plain text (the same shape as the
CLI's b7 read). Everything else is one line of JSON.
How failures come back
When the server refuses something, the exchange does not stop there. The tool answers in this shape, and the agent can read the body and fix it itself.
{"content":[{"type":"text","text":"{\"error\":{...}}"}],"isError":true}How an agent uses buster7
- Create a terminal with
new_session - Send an instruction with
send_input - Read the progress and the result with
read_screen/search_screen - Clean up with
kill_sessions
The sessions it makes also appear on the app's board, so a human can watch the work being handed over on the same screen.