Reach any machine.
Through one link.

1. 1

   Generate the install command

   In the dashboard, press “Connect a machine” and pick who should be able to reach it.

2. 2

   Run it on the target machine

   The agent installs itself as a service and registers with your account.

3. 3

   Open the console link

   That is it. A person, a terminal or a connected MCP client can use it.

# run this on the machine you want to connect
$ curl -fsSL https://linkport.example/i/<token> | sudo sh

✓ agent connected: gateway-01
✓ ssh published: https://linkport.example/s/9m…c4

On start, linkport-agent opens an outbound encrypted connection to the edge and proxies only the local addresses you published. The first connection publishes ssh:127.0.0.1:22 by default.

Turn on PUBLIC LINK, set a password and share the URL. The password can be changed without changing the address. For people who work with you regularly, leave the channel on account access instead, and grant them by email.

HTTP services get their own link. Publish a local port from the machine page and the edge proxies requests to it at /h/<link_id>/. WebSocket upgrades are opt-in per link.

The browser console is the zero-install path. linkport Terminal is the desktop one: Windows, macOS and Linux. It signs in with a short code you confirm here, then holds a cabinet session on the device. Through a linkport tunnel it opens a full SSH session (keys and host checks stay in the app) instead of a browser PTY.

The installer is public. Using the app requires an active Pro or Team subscription. Free accounts can download it; the window will stop at a paywall until a plan is prepaid.

The linkport MCP server exposes machines and connections through a scoped API token. The agent only gets the operations you allowed, and the command policy on each machine still applies: a denied command returns 403 and never reaches the shell.

Files move the same way. The agent reads and writes them itself, over the same control channel — no sshd login, no machine credentials on the server — so this works on end-to-end encrypted machines too. Every operation is written to the audit log, and on a Read Only machine everything that would change a file returns 403 while reading keeps working.

Inline content is capped at 8 MiB, since it travels inside the request. For anything larger, write_file takes a local_path and streams the file straight through — nothing buffers it whole, so the size is bounded only by the target's disk, and the bytes never pass through the model.

local_path reads the disk of the MCP server itself. On the hosted server that is ours, not yours, so it is switched off there. To send your own files, install linkport-mcp locally and run it over stdio — your client launches it, there is no listening socket, and it still talks to linkport for the machines themselves. The account page prints a ready config for Cursor, Claude Desktop and the local install once you create a key.

Recording is set on your account and can be overridden per machine, under Settings → Session recording. Three modes:

Recordings live under the machine's Activity tab. Because command filtering reads a byte stream, input typed inside a full-screen program is not parsed into the command list; a full session recording is the complete record.