The
thurbox-mcp
binary exposes Thurbox configuration over the
Model Context Protocol
. It shares the same SQLite database as the TUI — changes appear immediately via
PRAGMA data_version
polling.
Atomic replacement:set_roles
deletes all existing roles and replaces them in a single transaction. To add a role,
include all existing roles plus the new one.
MCP server configuration
Tool
Description
list_mcp_servers
List MCP servers for a project
set_mcp_servers
Set MCP servers for a project
Session management
Tool
Description
list_sessions
List sessions, optionally filtered by project
get_session
Get a session by UUID
delete_session
Soft-delete a session (TUI cleans up tmux/worktree)
restart_session
Queue a session restart (TUI processes the command)
restore_session
Restore a soft-deleted session
Scheduled commands
Tool
Description
schedule_command
Schedule text to be sent to a session at a future time
list_scheduled_commands
List pending scheduled commands, optionally by session
The TUI includes a built-in Admin session that auto-configures
thurbox-mcp
as an MCP server. Claude Code discovers the config automatically, enabling
conversational management inside the TUI.
How it works
On startup, Thurbox creates an admin directory at
~/.local/share/thurbox/admin/
A
.mcp.json
is written pointing to the
thurbox-mcp
binary
An "Admin" project is pinned at index 0 with a yellow
⚙
prefix
A single admin session spawns with all MCP tools pre-allowed
Restrictions
Cannot be edited (
Ctrl+E
shows an error)
Cannot be deleted (
Ctrl+D
shows an error)
Cannot have additional sessions created
The admin session cannot be closed (
Ctrl+C
shows an error)
Example usage
In the Admin session, use natural language:
Admin session
"Set up developer and reviewer roles for the my-app project.
Developer should have acceptEdits mode with git auto-approved.
Reviewer should be plan-only with read access."