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

# Partner MCP use cases

> What partners can do once they connect their own AI assistant to the partner MCP - and how to drive adoption.

Once a partner connects their AI client to the partner MCP, they can ask about and act on their own program data in plain language, everything scoped to what their account can see. Knowing the common use cases helps you explain the value and drive adoption, so partners actually turn it on. These map to the real tools the partner MCP exposes, so each one works the moment a partner connects.

## What you'll achieve

A clear picture of the jobs partners get done from their own assistant, so you can pitch the partner MCP in onboarding, QBRs, and enablement, and partners self-connect and use it.

## Before you start

<Steps>
  <Step title="Make sure partners can self-connect">
    Partners connect the assistant themselves from their portal, no vendor toggle needed. See [Give partners their own AI assistant](./give-partners-their-own-ai-assistant) for the steps to share.
  </Step>
</Steps>

## Steps

<Steps>
  <Step title="Check their pipeline">
    A partner asks their assistant about their open and registered deals, including stage, amount, and recent activity, without opening the portal.
  </Step>

  <Step title="Track their earnings">
    A partner asks about their commission status, what they have earned, and upcoming payouts, so they can self-serve finance questions.
  </Step>

  <Step title="Register a deal or share a lead">
    A partner submits a deal registration or shared lead through their assistant; the assistant discovers the right form, collects the fields, and submits it, scoped to their account.
  </Step>

  <Step title="Update a record or add a comment">
    A partner updates an editable field on one of their deals or posts a comment, and the change flows back through Introw the same as if they had done it in the portal.
  </Step>

  <Step title="Get answers">
    A partner asks program and enablement questions and gets sourced answers in plain language, in any language, without logging in.
  </Step>
</Steps>

## Verify it worked

A partner completes one of these jobs through their own AI client and sees the result reflected in their portal (a registered deal, an updated field, a posted comment), confirming the assistant is acting within their access.

## Related

<CardGroup cols={2}>
  <Card title="Partner AI assistant" icon="book-open" href="./give-partners-their-own-ai-assistant">
    The steps partners follow to connect.
  </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>