Uplink
Automate a real, logged-in browser on your own device — no stored credentials, no bot detection.
Links
README
From the repo.
Uplink MCP Server
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.
- npm:
@uplink-code/mcp - Registry name:
build.uplink/uplink - Docs: https://docs.uplink.build
Install
Add to any MCP client (Claude Code, Cursor, Claude Desktop, …):
{
"mcpServers": {
"uplink": {
"command": "npx",
"args": ["-y", "@uplink-code/mcp"]
}
}
}
Claude Code one-liner:
claude mcp add uplink -- npx -y @uplink-code/mcp
Authenticate
The server reads credentials written by the Uplink CLI. Sign in once:
npx @uplink-code/cli login
Use
- Ask your AI client to connect — it returns a pairing link.
- Open the link on your device in the Uplink Connect app to pair.
- 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.
Config for your environment
Replace {MCP_ENDPOINT_URL} with this MCP’s endpoint URL (from its repo or docs above). No API key — you connect directly.
Tool
OS
Config file: ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "{MCP_ENDPOINT_URL}"
}
}
}Paste into mcpServers in the config file. Restart Cursor after saving.
If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.