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

# Give partners their own AI assistant

> Partners connect their own AI client to the partner MCP from their portal and work with only their own scoped data - no vendor setup required.

Partners can connect their own AI client to Introw and work with their own data: their deals, tasks, commissions, and submissions, all scoped to what their partner account is allowed to see. There is nothing for you to switch on as the vendor: the partner connector lives in each partner's own portal, separate from your admin connectors, and partners connect it themselves. Your job is simply to point partners to it. The steps below are the ones a partner follows, so you can share them as-is.

## What you'll achieve

A partner connects their own AI assistant to their partner portal and can query and act on only their own scoped data in plain language, without logging into the portal for routine questions. Because the partner connector is separate from your internal MCP connectors, it never exposes anything beyond that partner's access.

## Before you start

<Steps>
  <Step title="No vendor toggle is needed">
    The partner connector is available to partners in their portal by default. You do not enable a partner MCP from your admin settings; partners self-connect.
  </Step>

  <Step title="The partner needs portal access">
    The partner signs in to their partner portal where the Integrations page is available.
  </Step>

  <Step title="The partner has a compatible AI client">
    The partner uses an AI client that supports custom MCP connectors (for example Claude).
  </Step>
</Steps>

## Steps

<Steps>
  <Step title="Open Integrations in the partner portal">
    As the partner, go to [Integrations](https://partners.introw.io/integrations) in your partner portal, find the **Claude** card, and select **Configure** to open the partner connector. This connector only exposes the portals available to your partner account.
  </Step>

  <Step title="Copy the MCP Server URL">
    On the connector page, select **Copy MCP Server URL**. This partner connector is separate from the vendor's admin connector, so use the URL shown here, not one from anywhere else.
  </Step>

  <Step title="Add Introw in your AI client">
    In Claude, open **Customize**, then **Connectors**, and add an **Introw** custom connector using the **MCP Server URL** you copied. This points your assistant at your partner portal data.
  </Step>

  <Step title="Complete the OAuth sign-in">
    Authorize the connection through the Introw sign-in so the assistant connects as you. Access is scoped to your partner account, so the assistant can only see and act on data your account already has.
  </Step>
</Steps>

## Verify it worked

The partner's connector page shows **Connection is active**, and the partner can ask their assistant about their own pipeline, commissions, or tasks and get live answers, without anything appearing that is outside their access. The partner can select **Disconnect** to revoke the assistant at any time.

## Related

<CardGroup cols={2}>
  <Card title="Partner MCP use cases" icon="book-open" href="./explore-partner-mcp-use-cases">
    What partners can do with their assistant.
  </Card>

  <Card title="Partner support agent" icon="book-open" href="/features/ai/partner-support">
    The in-portal AI assistant.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    MCP connectors and how the server is scoped.
  </Card>
</CardGroup>