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

# Use the Desktop Connector

> Pair Adam with supported desktop CAD and 3D applications or a local Streamable HTTP MCP server.

The Adam Desktop Connector links the Adam web app to supported applications running on your computer. It is used for **SolidWorks, Revit, Blender, SketchUp, Unreal Engine**, and local custom MCP connections.

<Info>
  Autodesk Fusion has a dedicated add-in and must not be paired through the Desktop Connector. Onshape uses OAuth and an optional Onshape extension.
</Info>

## Pair a desktop application

<Steps>
  <Step title="Open the integration in Adam">
    Select **Integrations**, choose the desktop application, and start its setup flow.
  </Step>

  <Step title="Install the connector">
    Download and install the Adam Desktop Connector on the computer that runs the target application.
  </Step>

  <Step title="Generate a pairing code">
    In Adam, generate a new pairing code. Codes expire, so keep the setup window open.
  </Step>

  <Step title="Enter the code locally">
    Open the Desktop Connector and enter the code. The connector associates this device with your active Adam team.
  </Step>

  <Step title="Open the target application">
    Keep both the connector and the application running. Return to Adam and confirm the device is connected before starting work.
  </Step>
</Steps>

## Application notes

<Tabs>
  <Tab title="SolidWorks">
    The SolidWorks connection is Windows-only. Start SolidWorks and keep it running; the connector starts the local bridge when it detects the application.
  </Tab>

  <Tab title="Revit">
    Revit support depends on Autodesk's Public MCP Server Tech Preview and currently targets Revit 2027. Follow the version-specific setup shown in Adam.
  </Tab>

  <Tab title="Blender, SketchUp, Unreal">
    Install any application-side component requested by the integration flow, then keep the application and Desktop Connector open while Adam needs live access.
  </Tab>
</Tabs>

## Connect a custom MCP server

Use **Custom MCP** when you have a local tool server that exposes a **Streamable HTTP** MCP endpoint.

Enter the local endpoint URL in the Desktop Connector, verify the server is running, and test it with a read-only request. A command-line stdio server is not a URL and cannot be entered directly; expose a supported HTTP endpoint first.

<Warning>
  A custom MCP server defines its own tools and security boundary. Review the server and its permissions before exposing it to Adam, especially if its tools can write files or change external systems.
</Warning>

## Manage paired devices

Use the integration detail to inspect, rename, repair, or unpair a connector when those controls are available. Unpair devices you no longer control.

If a device appears offline:

* open the Desktop Connector on the paired computer;
* confirm the target application and any required bridge or plug-in are running;
* verify the computer can reach Adam over the network; and
* generate a fresh code and pair again if the previous relationship was removed.