Uplink

What the Uplink MCP server does

The Uplink MCP server lets an agent pair with a real phone or laptop and run agentic automation in that device’s live, logged-in browser session. Its defining use case is browser work that depends on an existing session, including the account state already present in the browser.

This makes Uplink relevant when an agent needs to act through a browser that is already open and authenticated on a user-controlled device. The available description does not identify specific websites, browser brands, operating systems, or individual MCP tool names, so those details should not be assumed.

How it works

Uplink connects the agent to a physical phone or laptop rather than describing a standalone cloud browser. Automation then runs through the device’s live browser session. Because the session is logged in, the approach is intended for workflows where the browser’s current account context is part of the task.

The source material does not explain the connection protocol, pairing flow, whether the device must remain connected, or how the agent receives browser state. It also does not state whether the phone and laptop use the same workflow. Consult Uplink’s documentation for those implementation details before selecting it for a production workflow.

Setup and configuration

The available material identifies the documentation site at https://docs.uplink.build, but it does not provide installation steps, configuration fields, environment variables, authentication requirements, or client-specific setup instructions. As a result, no reliable setup command or configuration example can be included here.

At a minimum, a use case requires a real phone or laptop and a live, logged-in browser session, because those are central to the stated operating model. The exact pairing process and supported client configuration remain unspecified.

Tools and capabilities

The supported capability described for the Uplink MCP server is agentic automation through a paired device’s live browser session. The source does not list named tools or separate operations, so this reference does not claim support for navigation, clicking, form filling, screenshots, file handling, or any other individual action.

Limitations and notes

Uplink is best evaluated for workflows that require an existing browser login on a real device. The provided description does not establish support for unattended execution, remote cloud browsers, specific websites, particular operating systems, or named MCP clients. It also does not state licensing terms or expose environment-variable requirements. Verify these points in the Uplink documentation before implementation.