AI access with MCP: how it works

The Model Context Protocol (MCP) is an open standard that lets AI assistants call tools. WECOMMANDER is a remote MCP server: your AI client adds one URL, signs in with your account, and gets tools to read files, run commands and manage servers on the machines of your workspace, with your limits and approvals applied to every call.

One URL for all your machines

https://wecommander.app/mcp

Every AI client that supports remote MCP servers over HTTPS can use it: Claude (web, desktop and Claude Code), ChatGPT, Cursor, VS Code and others. Sign-in uses OAuth with your WECOMMANDER account; clients that only take a bearer token can use an API access key instead.

What happens on a tool call

  1. The AI calls a tool, for example process_exec with a command and a device.
  2. The gateway checks the caller's role, the arguments, the device's AI permissions and the safety net.
  3. A read runs directly. A high-risk action waits for a person's approval of that exact action, unless the device allows it (an allowed command or full trust).
  4. The gateway sends the action to the device's agent over its outbound encrypted connection. The agent checks it again: allowed folders, its own switches and, for high-risk actions, the signed approval.
  5. The result comes back with secrets masked, and the call is written to the audit log.

Two ways to connect a server

AgentSSH (Hybrid Access)
What is installed on the serverThe WECOMMANDER agent (Windows, macOS, Linux)Nothing
PathServer → outbound connection → wecommander.appwecommander.app → the app on your computer → SSH to the server
Works while your computer is offYesNo: your computer and the app must be on
Folder limitAllowed folders enforced on the deviceNone: a command reaches everything the SSH user can
Run as rootLinux only, with two keysThrough sudo -n when the computer allows sudo for that server and an admin turns it on
ToolsThe full setCommands, files over SFTP, overview, disk, processes, cleanup, process signals, timers and cron, Docker
AI permissionsTrust level, allowed commands, safety netThe same, plus read-only sharing that refuses every change

Choose the agent for always-on or autonomous work and tight folder limits; choose SSH to try quickly or where nothing can be installed. Hybrid Access is available from the Windows, macOS and Linux apps.

What the AI sees

devices_list lists agent devices; targets_list lists every place the AI can act on (agent devices and shared SSH servers) with each one's trust level, run as, safety net and supported tools, so the AI knows whether it is root and whether an action will need approval.

Limits that always apply