Command Executor MCP Server
The Command Executor server lets DMJBot run shell commands on a machine. The server
starts in a configured work folder, which is just the default working directory
— it is not a sandbox. Commands can cd elsewhere, use absolute paths, or reach
anything the account running the server can access. Fast commands return their output
immediately; commands that take longer than ~3 seconds are detached as background
tasks.
Security note: this server lets DMJBot run arbitrary shell commands with the privileges of the account that runs it — the work folder does not confine them. Install it only on machines where that is acceptable, and only when you need command execution. See Bridge and Devices for how device capabilities are scoped.
What DMJBot can do
execute_command— run a shell command. It starts in the configured work folder but is not restricted to it. Returns output synchronously for fast commands, or a task acceptance plus notifications for slow ones.
This server supports background tasks.
Add the server
This server runs on the machine where the commands should execute, through the DMJBot bridge:
dmjbot-bridge install command
dmjbot-bridge configure command
dmjbot-bridge start
You can run several instances for several folders — give each a distinct Title so DMJBot can tell them apart.
Configuration
| Field | Required | Default | Description |
|---|---|---|---|
| Work Folder | yes | — | Absolute path the server starts in (its default working directory). Commands begin here but are not confined to it. |
| Title | no | Command |
Short label used in the display title and tool descriptions so DMJBot can pick the right instance when several are loaded. |
See also
- Agent — run a specific CLI agent/tool instead of arbitrary commands.
- Git & GitHub — a safer, git/gh-only command wrapper.
- Tools and MCP
- Bridge and Devices