Remote MCP for your computers and devices
Model Context Protocol gives an AI client a structured tool interface. MapleMCP extends that idea across a remote account and enrolled endpoints, so one authorized MCP connection can reach the devices that belong to that account.
Local MCP versus remote MCP
| Question | Local MCP | MapleMCP remote MCP |
|---|---|---|
| Where does the tool server live? | Usually on the same computer as the AI client. | The public MCP endpoint authenticates the account and relays allowed tool calls to enrolled endpoints. |
| Can the AI client be on another device? | Not without adding some remote transport of your own. | Yes. Remote transport is part of the MapleMCP design. |
| How are multiple endpoints handled? | Often one local connection per machine. | The account exposes its enrolled devices and the selected device receives the operation. |
| What limits an operation? | The local MCP server and OS permissions. | Account authorization, per-device capability policy, agent path/policy rules, and OS permissions. |
The MapleMCP path
The client connects to MapleMCP over its public HTTPS MCP endpoint and completes account authorization.
The MCP surface returns only devices available to the authenticated account rather than exposing a global machine list.
MapleMCP checks the requested capability against the device's policy before relaying an allowed operation.
The installed agent performs the operation with its configured local privileges and returns the result through MapleMCP.
Why this matters for multi-device work
A developer might need a Windows workstation, a Linux build box, and a homelab server during the same conversation. A support technician might need to inspect one customer's enrolled PC and then another. A phone may expose a different tool set than a desktop. MapleMCP keeps those endpoints distinct while making them addressable from one authenticated integration.
Boundaries are part of the protocol surface
- Enrollment is explicit; installing the software alone does not silently authorize the device.
- Capabilities are selected per device.
- Desktop file tools are restricted by configured allowed directories.
- Windows and Linux agents run under configured users rather than treating MCP as automatic administrator access.
- Android tools appear only when the required operating-system permissions are available.
Common questions
What is remote MCP?
Remote MCP is an MCP tool service reached over a network rather than only through a local process. In MapleMCP, the remote MCP endpoint authenticates an account and connects the AI client to explicitly enrolled devices behind that account.
Is MapleMCP just an SSH wrapper?
No. Terminal execution is one capability. MapleMCP also exposes structured file, search, process, diagnostic, and mobile tools with device-specific capability controls.
Does one MCP connection expose every MapleMCP customer?
No. The public MCP surface is filtered by the authenticated account and its authorizations.
Do I need a separate MCP connection for each computer?
The MapleMCP model is designed so one authorized account connection can list and target multiple enrolled endpoints.
Related MapleMCP guides
Install the agent, approve the enrollment in your account, and enable only the capability groups you intend to use.
DownloadsReview permissions