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

# Integrations

> Connecting tools so your agent can take action.

Integrations are the tools your agent uses to resolve IT requests — picking up tickets in your PSA, looking up users in Microsoft 365, reading runbooks in your documentation platform, running scripts through your RMM, and more. Each integration you connect makes a set of tools available to the agent.

## Connecting an integration

Open **MSP Settings → Integrations**. You'll see a grid of all available apps — PSA (ConnectWise, HaloPSA, Autotask), Microsoft 365, RMM (NinjaOne, Datto, ConnectWise Automate, ConnectWise RMM, N-central), documentation (IT Glue), and more.

<Steps>
  <Step title="Find the app">
    Use the search bar or category filters to find the integration you want to connect. Apps already connected show a connected badge.
  </Step>

  <Step title="Click Connect">
    Click **Connect** on the app card. An authorization window opens where you sign in to the service and grant Rallied.ai access. Complete the OAuth flow in the popup, or enter API credentials for integrations that use a credentials form.
  </Step>

  <Step title="Review policies">
    After connecting, you're taken to the integration's detail page. The agent's tool policies are automatically seeded with sensible defaults—read operations default to `auto`, write operations default to `approval_needed`. Review and adjust these before the agent starts handling requests.
  </Step>
</Steps>

<Note>
  Credentials are never stored on the agent's server. OAuth tokens are managed securely and transmitted to the agent only at execution time via the Rallied.ai [Tool Gateway](/integrations/overview#how-integrations-work).
</Note>

## What happens on connect

When you connect an integration:

1. The available tools for that app are synced from the catalog.
2. Tool policies are seeded automatically based on whether each tool is a read or write operation.
3. The agent's configuration is updated so it knows about the new tools.

The agent can start using the integration immediately after the OAuth flow completes.

## Disconnecting an integration

Click **Disconnect** on a connected app card (or from within the integration's detail page). A confirmation dialog appears warning you that:

* The integration is removed
* All tool policies for that app are deleted
* The connected account is revoked

This cannot be undone. If you reconnect the same app later, policies are re-seeded from defaults.

<Warning>
  Disconnecting removes all tool policies for that integration. If you had customized any policies, you'll need to reconfigure them after reconnecting.
</Warning>

## Custom MCP servers

You can extend the agent with any remote MCP server by clicking **Add MCP Server** in the top-right corner of the Integrations tab.

<Steps>
  <Step title="Enter the server URL">
    Paste the HTTPS URL of the MCP server (e.g. `https://mcp.example.com/v1`). Local servers and plain HTTP are not supported. Click **Continue** — the dashboard probes the server to detect its authentication type.
  </Step>

  <Step title="Configure authentication">
    Depending on what the server requires, you'll see one of three options:

    * **OAuth** — a popup opens for you to authorize the connection
    * **Bearer token** — paste your API key or token
    * **Custom header** — specify the header name and value
    * **No auth** — the server is publicly accessible; no credentials needed

    Give the connection a name (the dashboard suggests one based on the URL).
  </Step>

  <Step title="Connect">
    Click **Connect** (or **Authorize with OAuth** for OAuth servers). The dashboard discovers the server's available tools and adds them to the agent's tool catalog. Tool policies are seeded automatically.
  </Step>
</Steps>

Once connected, the custom MCP server appears alongside your other integrations, and its tools are available to the agent.