> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uplink.build/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Drive Uplink from any MCP-capable AI client (Claude Code, Cursor, Windsurf, etc.)

The Uplink MCP server lets an LLM in Claude Code, Cursor, or Windsurf pair a real mobile device, drive its browser, and inspect the network traffic that the page produces — useful for reverse-engineering how a consumer website actually works.

## Get going

Register the endpoint with your client once. In Claude Code that's one command:

```bash theme={null}
claude mcp add --transport http uplink https://api.uplink.build/mcp
```

Other clients take the same URL as a couple of lines of config — see [Installation](/mcp/installation). The first time you use it, your client opens Uplink Console for you to grant access, and refreshes its own token from then on.

<CardGroup cols={2}>
  <Card title="Other clients" icon="download" href="/mcp/installation">
    Cursor, and anything else that speaks streamable-HTTP MCP.
  </Card>

  <Card title="Your first session" icon="comments" href="/mcp/first-session">
    What to say to pair a device and start driving it.
  </Card>
</CardGroup>

## When to reach for it

<CardGroup cols={2}>
  <Card title="Reverse-engineering" icon="binoculars">
    Have an AI assistant drive a logged-in mobile session and observe the real API calls a site makes.
  </Card>

  <Card title="Investigative automation" icon="magnifying-glass-chart">
    Ad-hoc "show me how X works" workflows without writing a script first.
  </Card>

  <Card title="AI agent prototyping" icon="robot">
    Test an automation idea interactively before committing it to a JavaScript SDK script.
  </Card>

  <Card title="Live debugging" icon="bug">
    Ask the model to drive a flow and surface the network requests or console logs that broke.
  </Card>
</CardGroup>

## How it works

```mermaid theme={null}
sequenceDiagram
  participant Client as Claude Code / Cursor
  participant MCP as Uplink MCP
  participant Relay as Uplink Relay
  participant Device as Paired Device

  Client->>MCP: start a session
  MCP->>Relay: create session
  Relay-->>MCP: session id, pairing code
  MCP-->>Client: pairing page + code
  Client->>Device: scan QR or type the code
  Device->>Relay: register as worker
  Client->>MCP: drive the page
  MCP->>Device: navigate, click, evaluate
  Device-->>MCP: network events, results
  MCP-->>Client: structured response
```

## Next steps

<CardGroup cols={2}>
  <Card title="Tool reference" icon="list" href="/mcp/tools">
    What your client is calling underneath, for when you need to look.
  </Card>

  <Card title="Revoke access" icon="shield-halved" href="/mcp/revoking-access">
    Cut off an AI client's access from Uplink Console.
  </Card>
</CardGroup>