Linux and Remote MCP
Drive a Windows AliasMode host from any Linux MCP client.
AliasMode has no native Linux app. Run AliasMode on a Windows host, publish its pinned Remote MCP endpoint through AliasMode Cloud, and control profiles from your Linux MCP client.
Direct answer
Install AliasMode on a Windows host in Cloud mode, copy the pinned device URL from Account & Settings, and add that URL to any OAuth- or bearer-capable MCP client on Linux. There is no native Linux dashboard.
Requirements
- A Windows host with AliasMode running in Cloud mode
- AliasMode Cloud account on the host and the client side
- An MCP client on Linux that supports OAuth or bearer authorization
- The pinned Remote MCP server URL from the host
No native Linux app
AliasMode ships a Windows installer and a macOS source run. There is no native Linux app or local Linux dashboard, and the loopback Local API is not part of a Linux story either. Linux works as the MCP client; the browser host stays a running Windows device.
- List and create profiles on the Windows host
- Open browsers headful or headless on the host
- Run the full Playwright action set in the selected browser
- Check browser status and capture and close browsers safely
Prepare the Windows host
Install and sign in
Install the Windows installer, choose Cloud mode, and sign in with your AliasMode account. Create at least one profile for the automation work.
Copy the pinned server URL
Open Account & Settings, find Remote MCP, and copy the server URL. It addresses this exact Windows installation and never redirects to another device.
https://cloud.aliasmode.com/v1/mcp/devices/<device-id>Keep the host running
An offline host returns an error to clients and does not queue work. Keep AliasMode open, or let the MCP helper start it, and keep the machine awake for the session.
Connect from your Linux client
Most Linux MCP clients accept a remote server URL. Register the pinned URL as a remote MCP server with OAuth authentication; the client registers itself automatically during the consent flow.
{
"mcpServers": {
"aliasmode": {
"url": "https://cloud.aliasmode.com/v1/mcp/devices/<device-id>"
}
}
}Clients that prefer static credentials use connector tokens. Create a connector on the Windows host, pass the token as a bearer credential from the Linux client, and revoke it when the machine is retired.
aliasmode-mcp remote-mcp create --name "Linux workstation"
aliasmode-mcp remote-mcp list
aliasmode-mcp remote-mcp revoke --id <connector-id>Sign in and approve access
The OAuth flow opens the AliasMode consent page. Sign in with the same AliasMode account that owns the Windows device, then select Sign in and allow. The Linux client receives its own revocable OAuth grant — never the Windows device credential or the Settings access key.
Run remote actions from Linux
Ask for profiles, open one, and run page actions exactly as you would locally. The browser windows open on the Windows host; your Linux client only receives tool results such as snapshots and screenshots.
List my AliasMode profiles.
Select the open profile named Research.
Take a page snapshot and summarize the visible headings.Security boundaries
- The pinned URL addresses one device and does not redirect when that device is offline
- OAuth grants and connector tokens are revocable independently of the device credential
- AliasMode Cloud relays the session, so the host can stay behind NAT, but it must be online and signed in
- Revoking a device in Cloud settings stops every client, including previously approved connectors
FAQ
Can a Linux machine run the AliasMode dashboard?
No. There is no native Linux app or dashboard. Linux acts as the MCP client while the browser host stays Windows.
Does the Windows host need a public IP address?
No. AliasMode Cloud relays the Remote MCP session to the pinned device URL, so the host can sit behind NAT, but it must be online and signed in.
Can the Linux client reach the Local API directly?
No. The Local API binds to loopback on the host at 127.0.0.1:50400. Remote MCP over AliasMode Cloud is the supported path from Linux.
Sources and verification
- AliasMode repository · mcp-tunnel.ts — Cloud tunnel that relays MCP sessions to the pinned device (checked September 2026)
- AliasMode repository · cloud-client.ts — pinned Remote MCP device URL format and connector management (checked September 2026)
- Model Context Protocol · MCP authorization specification (checked September 2026)
- AliasMode repository · README — platform scope and runtime components (checked September 2026)
Public product details can change after the check date. Facts are re-checked on a monthly cycle.