> ## 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.

# Connect tools and accounts

> Connect Adam to CAD applications, Arena, cloud services, API-key tools, and local MCP servers.

Open **Integrations** in the sidebar to browse the connections available to your active team. Search the catalog or switch to **Connected** to manage accounts already in use.

The catalog changes as providers and capabilities become available. The screen in Adam is the source of truth for the connections currently enabled for your workspace.

## Choose the right connection method

| Connection                                                                          | How it connects                                              | Keep the application open?                       |
| ----------------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------ |
| [Onshape](/integrations/onshape)                                                    | OAuth account connection; optional in-product extension      | No for web tasks; yes for live extension context |
| [Autodesk Fusion](/integrations/fusion)                                             | Adam add-in installed inside Fusion                          | Yes for live CAD access                          |
| [SolidWorks, Revit, Blender, SketchUp, and Unreal](/integrations/desktop-connector) | Adam Desktop Connector paired to this workspace              | Yes                                              |
| [Arena PLM](/integrations/arena)                                                    | Arena account session                                        | No                                               |
| Cloud services                                                                      | Provider sign-in or authorization flow                       | No                                               |
| API-key services                                                                    | Credential entered in Adam                                   | No                                               |
| Custom MCP server                                                                   | Local Streamable HTTP endpoint through the Desktop Connector | Yes                                              |

<Info>
  Fusion uses its own Adam add-in. Do not pair Fusion through the Desktop Connector.
</Info>

## Connect an integration

<Steps>
  <Step title="Select the active team">
    Use the team switcher before connecting. Connections belong to the team you are currently using.
  </Step>

  <Step title="Open the integration">
    Go to **Integrations**, search for the tool, and open its connection card.
  </Step>

  <Step title="Complete the provider flow">
    Follow the sign-in, installer, pairing-code, or credential instructions shown for that integration.
  </Step>

  <Step title="Verify the connection">
    Return to **Connected** and confirm the account or device appears. Start with a narrow inspection request before allowing writes.
  </Step>
</Steps>

## Use connected context in a task

Name the application, record or document, and desired result in your request. If several accounts are connected, identify the account or organization Adam should use.

For consequential changes, ask Adam to inspect first and state the approval boundary explicitly:

<Prompt description="Review before changing a connected system" actions={["copy"]}>
  Inspect the current assembly and list the constraints that would be affected by this change. Do not modify the model. Propose a safe sequence and wait for my approval.
</Prompt>

## Credentials and access

OAuth connections use the provider's authorization flow. For integrations that require an API key, Adam stores the credential securely and does not reveal it again in the interface. Use a dedicated, least-privilege credential whenever the provider supports one.

Disconnect an account from its integration detail or the **Connected** view when it should no longer be available to the team. Provider-side revocation can also invalidate an existing connection.

<Warning>
  A connected integration can expose business and design data to tasks run by authorized people in the team. Review team membership, task sharing, and provider permissions together.
</Warning>