Uplink

What the Uplink MCP server does

The Uplink MCP server connects an MCP client to a real browser session running on a device you control. The paired device can be a phone or laptop, and its browser remains logged in to the sites you want to operate. This lets an AI model drive pages through an existing user session instead of relying on a separate headless browser profile.

The server is intended for browser automation where maintaining a live session matters. It does not ask you to place site credentials into the MCP configuration. The README also describes the browser as a real user session, rather than an automated headless environment that a site may identify.

How it works

After the MCP client connects, Uplink returns a pairing link. Open that link on the device in the Uplink Connect app to establish the connection. Once paired, the model operates the page in the device's live browser session.

During use, the model can observe the page's DOM, the browser's real network traffic, and console output. These observations provide context about what the page contains and how it responds while the model performs an operation. The supplied material does not list individual MCP tool names or describe a separate browser-control API.

Setup and configuration

Install the published npm package as an MCP server in the client configuration:

{
  "mcpServers": {
    "uplink": {
      "command": "npx",
      "args": ["-y", "@uplink-code/mcp"]
    }
  }
}

Before using the Uplink MCP server, authenticate with the Uplink CLI:

npx @uplink-code/cli login

The server reads the credentials written by that CLI login. After adding the server to an MCP client, ask the client to connect, follow the returned pairing link, and open it in Uplink Connect on the target device.

The README names Claude Code, Cursor, and Claude Desktop as compatible MCP clients. It does not document environment variables or additional server configuration options.

Tools and capabilities

• Drive a real browser session on a paired phone or laptop.
• Use the browser's existing logged-in state.
• Observe page DOM content during an interaction.
• Observe network traffic generated by the live page.
• Observe browser console output.
• Connect through an MCP client using a pairing link.

Limitations and notes

Uplink requires a device to pair and a browser session to be available on that device. It is therefore different from a fully isolated headless automation job that runs without a user device. The workflow also depends on the Uplink Connect app for pairing.

Credentials are handled through the Uplink CLI's local sign-in flow rather than being supplied as site credentials in the MCP configuration. The provided material does not specify credential storage details, supported browsers, operating systems, browser actions, or service-level limits.

The package is published as proprietary software by Uplink. Consult the project documentation for the complete workflow and SDK reference.