Skip to main content
MCP · RemoteCommand

Remote computer tools for Claude and MCP clients

RemoteCommand can relay compatible MCP tool requests to an enrolled computer. Its dedicated Claude connection is not yet publicly available.

Availability: Dedicated Claude connection: coming soon. Availability is not the same as general remote MCP capability.

Install the device agent

On a supported Windows, macOS or Linux computer with a supported Node.js LTS release, run the agent and complete browser pairing.

Guide

How it works

  1. Install the device agent

    On a supported Windows, macOS or Linux computer with a supported Node.js LTS release, run the agent and complete browser pairing.

    npx -y @lhtsoft/remotecommand-agent@latest
  2. Choose allowed actions

    Set the allowed folders and start with the recommended Standard permissions. Terminal and Docker access require separate permissions.

  3. Use a compatible client

    The dedicated Claude integration is labeled Coming soon. Other clients with custom remote MCP and OAuth support can follow the manual setup steps.

OAuth and device approval

Client authorization and local device enrollment are separate steps. An MCP connection does not override a device's operation policy or allowed folders.

Avoid excessive permissions

Terminal commands run under the local OS account and are not limited to the configured file folders. Use restricted credentials and enable terminal access only when necessary.

Frequently asked questions

Is the Claude-specific connector currently available?

No. The current product interface labels the dedicated connection Coming soon.

Where can I find a working MCP endpoint?

The documented endpoint is https://api.remotecommand.app/mcp. Your client must support remote Streamable HTTP MCP and the authentication flow.

Next step

See manual MCP configuration