100+ integrations are ready to connect to your AI.Connect your first MCP

PartnerStack MCP server for your AI

Ask how a partner is doing, see what your program earned this month, review who applied, move leads and deals along and read your saved reports, whether you run a partner program or earn from one.

PopMCPPartnerStack

What happened in our partner program in the last 30 days?

Supported PartnerStack tools

Every documented endpoint in PartnerStack's Vendor API and Partner API, plus server-to-server tracking, with the everyday program tools loaded by default and one-call answers for how a partner is doing, what rewards add up to and what happened lately.

85 tools in the full catalog: 45 read and 40 write. 39 load by default, and the rest are found with tool search.

partnerstack_create_deal

Creates a deal.

partnerstack_get_deal

Reads one deal.

partnerstack_list_deals

Lists deals partners registered, newest first.

partnerstack_list_sales_cycle_stages

Lists the stages a lead or deal can be in.

partnerstack_update_deal

Changes a deal, such as its stage or amount in cents.

partnerstack_create_partnership

Adds a partner to your program.

partnerstack_get_partner_team

Lists the members of a partner's team, with each member's stack key.

partnerstack_get_partnership

Reads one partner.

partnerstack_list_partnerships

Vendor keys: lists partners in your program, newest first, filtered by email, group, approved_status or date.

partnerstack_list_products

Lists products customers hold, such as a trial or active subscription.

partnerstack_partner_overview

Use when asked how one partner is doing.

partnerstack_update_partnership

Changes one partner's group, tier, manager, partner_key or custom fields.

partnerstack_update_partnership_tags

Adds or removes tags on a partner, using add and remove lists.

partnerstack_activity_summary

Use for what happened recently in the program.

partnerstack_list_custom_reports

Lists the custom reports saved under Performance in PartnerStack, with each report's key and name.

partnerstack_read_report_export

Use to read the rows of an export.

partnerstack_run_custom_report

Use to read a report saved under Performance in PartnerStack.

partnerstack_create_lead

Creates a lead for a partner.

partnerstack_get_lead

Reads one lead.

partnerstack_list_leads

Lists leads partners submitted, newest first.

partnerstack_update_lead

Changes a lead, such as its status or amount in cents.

partnerstack_create_customer

Adds a customer credited to a partner.

partnerstack_get_customer

Reads one customer.

partnerstack_list_customers

Lists customers referred by partners, newest first.

partnerstack_list_webhooks

Lists webhooks in your program, with their events and target URLs.

partnerstack_update_customer

Changes a customer.

partnerstack_decide_application

Approves or declines one application.

partnerstack_list_applications

Lists applications to join your program, newest first.

partnerstack_create_reward

Gives a partner a reward, which can be real money.

partnerstack_create_transaction

Records a customer payment, which can pay partners real rewards unless the customer is a test customer.

partnerstack_list_actions

Lists recorded actions, newest first: what a partner or customer did, such as a demo or a signup step.

partnerstack_list_rewards

Lists partner rewards, newest first.

partnerstack_list_transactions

Lists customer transactions, newest first.

partnerstack_record_action

Records that a partner or customer did something, and how many times.

partnerstack_rewards_summary

Use for reward totals: how much was earned, pending or paid.

partnerstack_list_marketplace_programs

Partner keys only.

partnerstack_list_groups

Lists partner groups, such as Affiliates or Resellers, with each group's key, slug and name.

partnerstack_list_partnership_links

Lists a partner's referral links.

partnerstack_list_payouts

Partner keys only.

partnerstack_archive_deal

Archives a deal.

partnerstack_assign_partnership_to_deal

Assigns a deal to a partner.

partnerstack_convert_deal

Turns a won deal into a customer, credited to the deal's partner.

partnerstack_get_deal_file

Answers a link to download one file on a deal.

partnerstack_get_deal_form_templates

Reads the form a deal must fill in for a group or partner, so custom fields can be sent correctly on partnerstack_create_deal.

partnerstack_list_deal_files

Lists files attached to a deal, with each file's key for partnerstack_get_deal_file.

partnerstack_add_partner_team_member

Invites someone to a partner's team, which emails them.

partnerstack_archive_partnership

Removes a partner from your program by archiving the partnership.

partnerstack_create_product

Records that a customer holds a product.

partnerstack_create_product_book

Adds a product to your product book.

partnerstack_delete_product

Deletes a customer's product.

partnerstack_delete_product_book

Deletes a product book entry.

partnerstack_get_product

Reads one customer's product, by its PartnerStack key or external key.

partnerstack_get_product_book

Reads one product book entry, by its PartnerStack key or external key.

partnerstack_list_product_books

Lists your product book: the products you sell through partners.

partnerstack_update_partnerships_group

Moves several partners to another group at once.

partnerstack_update_product

Changes a customer's product, such as moving it from trial to active.

partnerstack_update_product_book

Changes a product book entry's name or description.

partnerstack_create_tier

Creates a partner tier in a tier collection, with its benefits and criteria.

partnerstack_create_tier_collection

Creates a tier collection.

partnerstack_export_base_records

Queues a bulk CSV export of partners, customers, transactions, rewards, leads, deals, applications or training.

partnerstack_export_custom_report

Queues a CSV of a saved report, which emails member_email when ready.

partnerstack_get_custom_report

Reads one saved report's settings, not its rows.

partnerstack_get_report_export

Checks a queued export.

partnerstack_get_tier

Reads one tier.

partnerstack_get_tier_collection

Reads one tier collection.

partnerstack_list_tier_collections

Lists your tier collections, with each collection's key.

partnerstack_list_tiers

Lists partner tiers.

partnerstack_update_tier

Changes a tier's name, benefits or criteria.

partnerstack_update_tier_collection

Changes a tier collection.

partnerstack_archive_lead

Archives a lead.

partnerstack_convert_lead

Turns a lead into a customer, credited to the lead's partner.

partnerstack_get_lead_form_templates

Reads the form a lead must fill in for a group or partner, so custom fields can be sent correctly on partnerstack_create_lead.

partnerstack_archive_webhook

Stops a webhook.

partnerstack_create_webhook

Sends chosen PartnerStack events to a URL.

partnerstack_delete_customer

Deletes a customer.

partnerstack_get_webhook

Reads one webhook.

partnerstack_update_webhook

Changes a webhook's events or URL.

partnerstack_create_application

Creates an application on someone's behalf.

partnerstack_decide_applications_bulk

Approves or declines several applications at once.

partnerstack_archive_action

Archives an action, and any rewards or drip rewards tied to it.

partnerstack_delete_transaction

Deletes a transaction.

partnerstack_get_marketplace_program

Partner keys only.

partnerstack_convert_click_to_customer

Server-to-server tracking: credits a signup to the partner whose link was clicked.

partnerstack_list_disti_listing_categories

Lists the category names PartnerStack uses for distribution listings, with AppDirect ids.

partnerstack_list_form_templates

Lists the custom forms in your program, for links, applications, deals, leads and more.

Connect PartnerStack to Claude, ChatGPT and Claude Code

Credentials off one PartnerStack screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.

Running a program: open Settings, then Integrations, then Partnerstack API Keys in PartnerStack, copy the public and secret key, and paste them into PopMCP. Earning as a partner: open Settings, then API, copy your key, and paste it under More options. There is no app to review and nothing to deploy.

Public keypk_...
Secret key••••••••••••3f7a
Partner API key••••••••••••3f7a
ConnectionVerified

Then just ask for the work

  • “What happened in our partner program in the last 30 days?”

    • activity_summary
  • “How is ada@example.com doing as a partner: customers, rewards, links and deals?”

    • partner_overview
  • “How much in rewards is pending and approved this quarter, and who earned the most?”

    • rewards_summary
  • “Who has applied to join our program and is still waiting for a decision?”

    • list_applications
  • “Approve this application and put them in the Resellers group”

    • list_groups
    • decide_application
  • “Run our saved Monthly partners report and summarize the top performers”

    • run_custom_report
  • “Move this deal to Closed Won and turn it into a customer”

    • list_sales_cycle_stages
    • update_deal
    • convert_deal
  • “As a partner, which of my programs paid me the most, and what payouts have I had this year?”

    • rewards_summary
    • list_payouts

Use PartnerStack from the assistant you already open

One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.

Claude DesktopCustom connector

Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.

Claude WebCustom connector

The same endpoint, registered in the browser. Nothing to install on the machine you are working from.

ChatGPTCustom connector

Register PopMCP as a custom connector, then let ChatGPT read and update the account.

CodexDesktop & CLI

Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.

OpenCodeCoding agent

Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.

ZCodeDesktop app

Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.

PartnerStack MCP server questions

What teams ask before putting PartnerStack behind an AI client.

What does PopMCP need to connect PartnerStack?

If you run a program, the public key and secret key from Settings, Integrations, Partnerstack API Keys. If you earn as a partner, one API key from Settings, API. PopMCP stores them encrypted and checks them against PartnerStack when you connect. The keys never reach your AI client.

Does it work for partners as well as companies running a program?

Yes. PartnerStack has a Vendor API for companies running a program and a Partner API for people earning from programs, and one connector covers both. Which keys you paste decides which you get. Partner keys reach the programs you joined, your customers, transactions, rewards, payouts and the marketplace. Tools for running a program are refused with a partner key, and the AI is told why.

Should I use the Test or Production keys?

Production keys for your real program. Test keys are there to try things safely: customers made with them are marked as test, and transactions for those customers pay no rewards. PartnerStack has no switch between the two, so the keys you paste decide, and it does not say which keys are in use, so keep track of which box you copied from.

Can the AI pay a partner by accident?

New connections start read-only, so giving rewards and recording transactions are hidden and refused until an owner or admin allows write actions. Once they are allowed, those tools tell the AI to ask you first, because a reward or a transaction can pay real money. PartnerStack's vendor keys cannot be made read-only on its side, so keep this switch off if you only want answers.

Can the AI read my saved reports?

Yes. Name a report saved under Performance in PartnerStack and a teammate's email. PartnerStack makes a fresh export and emails it to that teammate, and the AI reads the rows once it is ready. Exports can take up to 30 minutes, so a slow one is picked up later. PartnerStack allows one export per report and person every 2 hours.

Do I need a developer account or an approved app?

No. The keys are already on your PartnerStack settings page, with nothing to apply for. You do need a PartnerStack account. Server-to-server tracking is the one extra: it uses a separate tracking token from the same Integrations page, and everything else works without it.

Do I have to run or host the PartnerStack MCP server myself?

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Which AI clients can use this MCP server?

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

How do I connect PartnerStack to Claude Code?

Connect PartnerStack in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking PartnerStack on the consent screen. The PartnerStack tools are then available in that session, and no PartnerStack credential is stored on your machine.

Why do only 39 of the 85 tools load by default?

Loading 85 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 39-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.

What is the difference between a tool and a trigger?

A tool is something your AI calls, and there are 85 here. A trigger is something PopMCP watches for you: 27 PartnerStack events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into PartnerStack.

Connect PartnerStack to your AI in minutes

Launch a hosted MCP endpoint for PartnerStack, keep tool access under control, and start testing real workflow prompts right away.

Connect your first MCP