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
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.
The partner needs portal access
The partner signs in to their partner portal where the Integrations page is available.
Steps
Open Integrations in the partner portal
As the partner, go to 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.
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.
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.
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
Partner MCP use cases
What partners can do with their assistant.
Partner support agent
The in-portal AI assistant.
Implementation reference
MCP connectors and how the server is scoped.