Skip to content

Using AI With Your Partner Portal

PartnerPortal has a built-in MCP server — a secure way to connect an AI assistant to your portal. Once you connect an assistant like Claude, you can ask about your partner program in plain language and have the assistant answer using your live portal data, acting as you and respecting your permissions.

This page explains what the AI can see, the questions you can ask, the actions it can take, and how access stays safe. To set it up, see Connect Claude to Your Portal.

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to outside tools and data. PartnerPortal runs an MCP server for your portal, so a supported assistant can read your program data and take a small number of actions on your behalf — the same things you could do yourself in the portal, no more.

You connect an assistant once, by pasting a connect URL and signing in with your normal portal login. There is no separate password, API key, or developer setup — see Connect Claude to Your Portal.

Once connected, your assistant can answer questions across your whole program. For example:

  • Your program at a glance — “Give me an overview of my portal.” A single orientation call returns your program setup, key settings, connected integrations, and counts.
  • Partners — “Which partners joined this quarter?”, “Show me Acme Consulting’s details, members, and recent leads.”
  • Leads — “How many leads are pending?”, “Show me the leads from Acme in the last 30 days,” “What’s the full history on this lead?”
  • Opportunities — “Which opportunities are still active, and who’s engaged?”
  • Commissions and revenue — “What do we owe partners right now?”, “Show revenue attributed to partners last month,” “Give me a health check of the program.”
  • Enablement content — “What resources do we have on onboarding?”, “What was our latest announcement?”

The assistant returns compact, readable answers and can chain questions together — for example, find a partner, then list that partner’s leads.

Behind those questions is a fixed set of tools — the specific, permission-checked actions the MCP server exposes. Your assistant decides which to call based on what you ask. There are 15 in total: 13 that read your data and 2 that make changes.

ToolWhat it answers
describe_portalA one-call overview of your portal — program setup, key settings, connected integrations, and entity counts. The best first call in a session.
list_partnersYour partner organizations, with filtering, search, and sorting (including by lifetime revenue).
get_partnerEverything about one partner — members, recent leads, commission terms, tier, and open payouts.
list_leadsYour leads, filtered by status, partner, date range, or search text.
get_leadFull detail on one lead, including its comment thread and CRM sync state.
list_opportunitiesOpportunities shared with partners, and where each partner stands.
list_commissions_owedWhat you owe partners right now — and paid history when you ask for it.
list_revenueRevenue transactions attributed to partners.
get_metrics_summaryA one-call health check of the program — partner and lead counts, recent revenue, and open payouts.
list_resourcesYour enablement content library.
get_resourceThe full contents of one resource.
list_announcementsAnnouncements you’ve sent to partners.
get_announcementThe full text of one announcement.
ToolWhat it does
create_leadRegisters a lead against one of your partners — recorded exactly like a portal registration, with that partner’s commission terms applied automatically.
add_lead_commentAdds a comment to a lead’s discussion thread, attributed to you.

Registering a lead and commenting on a lead are the only things the assistant can change — everything else is strictly read-only. Both are performed as you: a lead you register through the assistant is recorded exactly like one you register in the portal, with the partner’s commission terms applied automatically, and a comment is attributed to your account.

The AI connection is designed so it can never do more than the person using it:

  • It acts as you. When you connect, you sign in with your own portal login. The assistant sees only what your account is allowed to see, and every action is recorded under your name.
  • It’s scoped to your portal. A connection is tied to one portal. It can never reach another company’s data.
  • Sensitive details stay hidden. Partner payout and bank details are never exposed to the assistant.
  • Reads by default, two writes only. Everything is read-only except registering a lead and commenting on a lead.
  • Team members only, for now. AI access is currently available to your internal team (admins and staff). Your partners cannot connect an assistant to your portal yet.
  • Claude — on the web at claude.ai, in the Claude desktop app, and in Claude Code (the terminal). See Connect Claude to Your Portal.
  • ChatGPT — planned. This page will be updated when it’s available.

AI features are included on every plan, at no extra cost. Anyone on your team with permission to manage portal settings can get the connect URL and connect their own assistant.

Yes. Every portal has its own MCP server, so you can connect an AI assistant like Claude and work with your partner data in natural language.

Claude today — on the web, in the desktop app, and in the Claude Code terminal. ChatGPT support is planned.

Only in two ways: it can register a lead and comment on a lead, both acting as you. Everything else is read-only.

Only what your own account can see in your portal, and only for your portal. Partner payout and bank details are never exposed.

Not yet. AI access is currently for your internal team (admins and staff). Partner access is planned for a later release.

No. AI features are included on every plan.