---
title: Bridge — QuickDeploy AI desktop app
description: Install the QuickDeploy AI Bridge (MCP Client Bridge) via CLI, winget, an agent prompt, or a direct GitHub download, then connect deployed capabilities to your local MCP clients.
---

# Bridge (MCP Client Bridge)

Bridge is QuickDeploy AI's secure browser-to-native handoff for MCP server
configuration. It connects capabilities you deploy on the marketplace to the
AI apps already on your machine — VS Code, Cursor, Claude Desktop, and ChatGPT
Desktop — without hand-editing any JSON config.

The always-on core is the `qdai-bridged` daemon (macOS, Linux, Windows, WSL).
The desktop window, the CLI, and the browser extension are all thin clients of
its local IPC API. The daemon only makes outbound connections and never writes
a config file without your explicit approval.

## Install

Pick one method. Every path ends with a one-time device enrollment.

### Install through the CLI

The fastest path on any OS. The installer drops the `qdai-bridged` daemon.

- macOS / Linux / WSL:

  ```sh
  curl -fsSL https://quickdeploy.ai/bridge/install.sh | sh
  ```

- Windows (PowerShell):

  ```powershell
  irm https://quickdeploy.ai/bridge/install.ps1 | iex
  ```

### Install through winget (Windows)

```powershell
winget install QuickDeployAI.MCPClientBridge
```

Requires Windows 10 (1809+) or Windows 11.

### Install with an agent prompt

Paste this prompt into Claude Code, Cursor, Codex, or any terminal-capable
agent. It runs the same CLI install, verifies it, and enrolls the device:

```text
Install and enroll the QuickDeploy AI Bridge daemon on this machine.

1. Detect the operating system.
2. Install the daemon:
   - macOS / Linux / WSL:  curl -fsSL https://quickdeploy.ai/bridge/install.sh | sh
   - Windows (PowerShell): irm https://quickdeploy.ai/bridge/install.ps1 | iex
3. Verify the install:    qdai-bridged status
4. Link this device (opens a browser sign-in): qdai-bridged enroll
5. Enable autostart so the daemon survives reboot: qdai-bridged service install

Then run "qdai-bridged status" again and report the daemon, enrollment, and relay
status. Do not edit any MCP client config files by hand — the Bridge applies
signed, verified patches and asks for approval before writing.
```

### Direct download (GitHub release)

Download the latest signed `.msix` from GitHub Releases (tagged
`mcp-client-bridge-v*`) and run it:

<https://github.com/QuickDeployAI/monorepo/releases?q=mcp-client-bridge&expanded=true>

Choose `McpClientBridge-<version>-x64.msix` on Intel/AMD or the `-arm64.msix`
build on ARM.

## After install: link your device

```sh
qdai-bridged enroll
```

`qdai-bridged enroll` opens your browser to sign in and link the device. Enable
autostart with `qdai-bridged service install` so the daemon survives a reboot.

## How to use it

1. **Install & enroll** — install via any method above, then run `qdai-bridged enroll`.
2. **Click Connect** — choose Connect on a capability in the marketplace or
   dashboard; the intent reaches your device instantly over the daemon's relay.
3. **Approve & go** — review the proposed change, pick the target client, and
   approve. Bridge patches the config and the new MCP server is ready to use.

Useful commands:

- `qdai-bridged status` — daemon / enrollment / relay status
- `qdai-bridged pending` — connect intents awaiting approval
- `qdai-bridged approve <id> --target cursor` — approve an intent for a client
- `qdai-bridged service install` — enable per-user autostart

## Next steps

- [Browse the marketplace](https://marketplace.quickdeploy.ai/marketplace)
- [Read the docs](https://docs.quickdeploy.ai/docs)
- [View the source and releases](https://github.com/QuickDeployAI/monorepo)