Uplink

build.uplinkPublished by uplink.buildv0.1.4Updated Oct 24, 2026

Automate a real, logged-in browser on your own device — no stored credentials, no bot detection.

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

Lets an assistant drive a real, already-logged-in browser session on a paired personal device, observing live DOM, network, and console.

What you can do
Uplink connects an MCP client to a real browser session running on a device you pair, such as your phone or laptop. The assistant drives the page in that live session and can observe the real network traffic, DOM, and console. Pairing happens through a link opened in the Uplink Connect app, and the server reads credentials written by the Uplink CLI after a one-time sign-in.
When to use it
Use it when a task needs a genuine logged-in browser session rather than a headless one, for example interacting with sites that block or flag automated browsers. It suits workflows where you want the assistant to work inside your own existing session on your own device.
Requirements
Runs locally over stdio via npx from the npm package @uplink-code/mcp. Requires Node.js and the Uplink CLI, with a one-time sign-in through the CLI so the server can read the credentials it writes. A device with the Uplink Connect app is needed to complete pairing. Desktop only; no web executable.
Before you install
The assistant acts inside a real, logged-in browser session on your device, so it can view and change data as you would, including anything the session can reach. Credentials are stored by the Uplink CLI and read by this server. Pairing links should only be opened on a device you control.

Installation

In SourceWeft

  1. Open Uplink in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Uplink MCP Server

[npm] [MCP Registry]

Automate a real, logged-in browser on your own device — no stored credentials, no bot detection.

Uplink drives a real device you pair (your phone or laptop), inside its real, logged-in browser session. Unlike headless automation, there are no stored credentials and nothing for a site's bot detection to flag — it's a real user's real session.

Install

Add to any MCP client (Claude Code, Cursor, Claude Desktop, …):

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

Claude Code one-liner:

bash
claude mcp add uplink -- npx -y @uplink-code/mcp

Authenticate

The server reads credentials written by the Uplink CLI. Sign in once:

bash
npx @uplink-code/cli login

Use

  1. Ask your AI client to connect — it returns a pairing link.
  2. Open the link on your device in the Uplink Connect app to pair.
  3. The model drives the page in your live session and observes the real network traffic, DOM, and console.

See the quickstart for the full workflow and SDK reference.

License

Proprietary. © Uplink. See npm for the published package.

Source: README.md at commit 3c65894

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.4LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.