Local Model Context Protocol

Your MCP client. Your folders. Your approval.

Let a trusted MCP client inspect files, make hash-checked edits or propose durable copy/move plans. BobCommander starts read-only, with explicit folder grants and no network listener.

Version requirements: local MCP needs 2.48.0 or later; GUI-approved plans need 2.49.0 or later. Version 2.47.0 does not contain MCP. This guide does not imply these versions are already published on Stable.

Start safely

Connect over local stdio.

Install the Experimental MSI or extract the complete ZIP, including its Mcp runtime folder. Create the local workspace first. No account, API key, Azure resource or background service is required.

In a client using an mcpServers configuration, use an absolute CLI path:

The example uses an extracted ZIP. For MSI, point command to C:\Program Files\BobCommander Experimental\bobcommander.exe on a standard Windows installation, and use that same installation's desktop for plan approval. Use the actual Program Files location if Windows is installed elsewhere.

{
  "mcpServers": {
    "bobcommander": {
      "command": "C:\\Tools\\BobCommander\\bobcommander.exe",
      "args": ["mcp", "--root", "C:\\Workspace"]
    }
  }
}

For VS Code, use the same definition under servers instead of mcpServers and add "type": "stdio". Client configuration locations vary. The MCP client starts the process; launching it alone in a terminal is not an interactive chat.

Repeat --root for up to 16 existing local directories. There is no implicit home-folder or whole-machine grant. Tool paths must preserve the configured root's spelling and case. UNC/device paths, alternate streams, symlinks, junctions and other reparse points are rejected.

Independent permissions

Expose only the tools you need.

Read: 6 tools

Configuration, metadata, bounded directory listing, paged UTF-8 reads, filename/content search and SHA-256 hashing. Enabled by default inside the granted roots.

Write: +5 tools

--allow-write enables hash-checked writes and literal edits, folder creation and single-file copy/move. Existing destinations are not blindly overwritten.

Processes: +5 tools

--allow-execute enables owned process sessions, input/output and stop controls. Programs run with your full user privileges, not in a root sandbox. They can change data outside the roots.

--allow-plans independently adds 8 plan tools. All options together expose 24 tools. Disabled tools are absent from discovery; a client cannot broaden grants. Edit launch arguments and reconnect to change permissions.

Tool names by permission
  • Read: get_config, get_file_info, list_directory, read_file, search_files, hash_file.
  • Write: write_file, edit_block, create_directory, copy_file, move_file. For existing-file edits, pass the current expectedSha256 returned by a read; stale hashes must be reread, not forced.
  • Processes: start_process, read_process_output, write_process_input, list_processes, stop_process. Sessions belong to this connection; this is not system-wide process management.
  • Plans: create_plan, preview_plan, list_plans, apply_plan, get_plan_job, pause_plan_job, resume_plan_job, cancel_plan_job.
Plan, preview, apply

Propose through MCP. Approve in the desktop.

Start the matching 2.49.0-or-later desktop in the same Windows user/session. Close an older running desktop first. Use plan-only arguments; direct write and process execution are not needed:

["mcp", "--root", "C:\\Workspace", "--allow-plans"]
  1. Call create_plan with the example below. The destination directory must already exist. Retain the returned plan ID.
  2. Call preview_plan with planId. Inspect exact source/destination paths, hashes, sizes, root grants, free-space snapshots and the approval deadline.
  3. Call apply_plan with planId. This only opens Commands > MCP operation plans; it does not approve or execute anything.
  4. In the desktop, review the complete proposal, acknowledge the risks and explicitly click Approve and apply. There is no MCP approval tool or token.
  5. Monitor get_plan_job; use pause_plan_job, resume_plan_job or cancel_plan_job. Reconnect with the same or broader roots and use list_plans to recover recent IDs.
{
  "operations": [
    {
      "kind": "copy",
      "source": "C:\\Workspace\\report.txt",
      "destinationDirectory": "C:\\Workspace\\Reviewed"
    }
  ]
}

Plans support 1-32 regular-file copies/moves, up to 512 MiB combined. They preserve filenames, never overwrite and initially expire after one hour. No recursive directory plans, general delete or universal rollback. Completed steps remain after cancellation or failure. Approved jobs persist in the desktop queue and can outlive the MCP connection.

Security and troubleshooting

Consent is not an operating-system sandbox.

  • Use trusted clients and narrow, operator-owned roots excluding BobCommander's application data. Full-user execution, broad writes, UI automation or queue tampering can bypass application-level consent. Use a restricted account or VM for stronger isolation.
  • If no MCP command exists, check the installed version and CLI path. Keep the entire packaged runtime; do not copy only the companion executable or flatten its dependencies.
  • If plan calls fail, check that the matching desktop is running in the same user/session. A newer CLI does not upgrade an older running desktop. Plan requests can time out while persisting; inspect list_plans before retrying.
  • If a source hash changes, read/preview again rather than forcing execution. On ambiguous recovery, inspect source, destination and partial files manually; completed work is not automatically undone.
  • Desktop file formats and permission checks still apply. This is not complete Desktop Commander feature parity: there are no dedicated Office/PDF, archive or synchronization MCP tools in this release.

Review the client configuration and Experimental testing precautions before granting access.