DMJBot - Personal AI Assistant

Devices

Wiki

Devices

A device is any machine you connect to DMJBot so the bot can do work on it — your laptop, a desktop, a home server, a cloud instance, even some IoT hardware. Connecting a device lets DMJBot use the tools (MCP servers) running on that machine: manage files, run code, drive other AI agents like Claude Code or Copilot, reach a local database, and so on.

You can connect several devices to the same bot and use them at once — for example a server and a desktop — and move data and tasks between them.

How a device connects

A device is connected with the DMJBot Bridge — a small application you install on the machine. The bridge exposes the MCP servers running on that device to the bot. Once it is running, you add the device in Settings → Devices and connect it using the connect URL shown there.

Installing and running the bridge, plus the full command reference, is covered on the DMJBot Bridge page.

Security of your devices

Connecting a device does not give DMJBot full access to it. The bridge exposes only the MCP servers you explicitly install and configure.

Important rules:

  • Only installed MCP servers are accessible. Nothing else on the device is exposed.
  • File access is limited by the MCP server configuration. For example, if you install only a File Storage MCP server and configure one folder, DMJBot can access only that folder and not other files.
  • Command execution is not available by default. If you want DMJBot to run commands on the device, you must install an MCP server that explicitly allows command execution.
  • For strict security control, use only your own MCP servers and do not use packaged servers.

Security is defined by your MCP server set and each server's configuration. If a capability is not provided by an installed MCP server, DMJBot cannot use it.

Managing devices

Devices are managed in Settings → Devices, where you can:

  • Add a new device and get the connect URL for the bridge.
  • See which devices are connected and their status.
  • See and control which MCP servers each device exposes.

See also