How it works
Register a computer
Install Node.js LTS (22, 24 or 26) and run the agent. Sign in through the browser, confirm the matching one-time device code, and choose allowed folders and permissions.
npx -y @lhtsoft/remotecommand-agent@latestConfigure the remote MCP endpoint
In a client supporting custom remote MCP with OAuth, add this Streamable HTTP endpoint. For Cursor, the following mcp.json shape is documented.
{ "mcpServers": { "remotecommand": { "url": "https://api.remotecommand.app/mcp" } } }Authorize and verify
Complete the OAuth sign-in and permission consent in your MCP client, then call list_devices. Your agent must remain online to execute requests.
list_devices
Endpoint and protocol
Remote MCP endpoint: https://api.remotecommand.app/mcp. Remote client configuration differs by provider; support for OAuth and custom endpoints must be checked in that client's current settings.
Permissions still apply
Authorizing the MCP client alone does not enable unrestricted execution. Local folder and operation policies, optional approvals and the selected device determine what runs.
Frequently asked questions
Why can I connect but not run a command?
The device may be offline or terminal access may be disabled. Check the device status, allowed folders, command policy and whether an approval is required.
Do I need to expose a port on my computer?
The documented Node agent initiates outbound HTTPS/WSS connections to the service; it does not require opening a public inbound port for normal setup.