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

> How a partner connects their own LLM to Introw over MCP and reaches vendor resources from their assistant.

**Open in Introw:** [Integrations](https://app.introw.io/integrations)

## How it works

Partner AI is the partner-side experience of Introw's MCP server. The partner connects their own MCP client - Claude, ChatGPT, Cursor, or another assistant - to Introw over OAuth, and from then on reaches the tools you expose (deal registration, coaching, enablement, support) from that assistant. Everything is scoped by the vendor-configured [capability matrix](/headless#governance-and-trust) and writes back to the CRM. The canonical MCP setup and tool reference live in the Developer domain; this page frames the partner-side path and links there.

* Connect an assistant: [Connect an MCP client](/features/developer/mcp/guides/connect-an-mcp-client), [Connect Claude](/features/developer/mcp/guides/connect-claude), [Connect ChatGPT](/features/developer/mcp/guides/connect-chatgpt).
* Give partners their own assistant: [Give partners their own AI assistant](/features/developer/mcp/guides/give-partners-their-own-ai-assistant).
* What the assistant can answer and do: [MCP](/features/developer/mcp) and [Partner Support](/features/ai/partner-support).

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  client["Partner's MCP client"] -->|"OAuth"| mcp["Introw MCP server"]
  mcp --> tools["Tools scoped by capability matrix"]
  tools --> crm["Writes back to CRM"]
```

## Prerequisites

* MCP enabled for the organization.
* The partner has an MCP-capable client (Claude, ChatGPT, Cursor, or similar).
* The partner contact has access to the vendor's partner experience, which scopes what the assistant can reach.

## Settings & configuration

The partner connects their assistant from **Integrations** in their own portal. What the assistant can see and do is governed by the vendor's capability matrix and the partner's permissions - not configured on the partner side.

**MCP connection** lives on the partner's **Integrations** screen and is where the partner authorizes their assistant over OAuth. Access is scoped to the partner's permissions, so the assistant can only reach what the vendor exposes.

## Setup walkthrough

<Steps>
  <Step title="Enable MCP for the organization">
    The vendor confirms MCP is enabled. See [MCP](/features/developer/mcp/technical).
  </Step>

  <Step title="The partner connects their assistant">
    The partner opens **Integrations** and connects their MCP client over OAuth. See [Connect an MCP client](/features/developer/mcp/guides/connect-an-mcp-client).
  </Step>

  <Step title="The partner works from the assistant">
    The partner registers deals, gets coaching, and self-serves support and enablement from their assistant, scoped to their permissions.
  </Step>
</Steps>

## How-to guides

<CardGroup cols={2}>
  <Card title="Connect an MCP client" icon="book-open" href="/features/partner-connect/partner-ai/guides/connect-an-mcp-client">
    As a partner, connect any MCP-capable client - Cursor, Gemini, Windsurf, Notion AI, and more - to your Introw partner data with the partner MCP connector.
  </Card>

  <Card title="Connect ChatGPT" icon="book-open" href="/features/partner-connect/partner-ai/guides/connect-chatgpt">
    As a partner, connect ChatGPT to Introw over MCP so you can query and act on your own partner data - deals, commissions, tasks - from inside ChatGPT.
  </Card>

  <Card title="Connect Claude" icon="book-open" href="/features/partner-connect/partner-ai/guides/connect-claude">
    As a partner, connect Claude to Introw over MCP so you can query and act on your own partner data - deals, commissions, tasks - from inside Claude.
  </Card>
</CardGroup>

## Limits & gotchas

<Warning>
  What a partner's assistant can reach is scoped by the vendor's capability matrix and the partner's permissions. MCP must be enabled for the organization before a partner can connect.
</Warning>

## Troubleshooting

* **The assistant cannot connect** - MCP is not enabled for the organization, or the OAuth authorization did not complete.
* **The assistant returns nothing for a partner** - the partner contact lacks experience access, or the capability is not exposed to them.