partnerstack_create_ dealCreates a deal.
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
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_ dealCreates a deal.
partnerstack_get_ dealReads one deal.
partnerstack_list_ dealsLists deals partners registered, newest first.
partnerstack_list_ sales_ cycle_ stagesLists the stages a lead or deal can be in.
partnerstack_update_ dealChanges a deal, such as its stage or amount in cents.
partnerstack_create_ partnershipAdds a partner to your program.
partnerstack_get_ partner_ teamLists the members of a partner's team, with each member's stack key.
partnerstack_get_ partnershipReads one partner.
partnerstack_list_ partnershipsVendor keys: lists partners in your program, newest first, filtered by email, group, approved_status or date.
partnerstack_list_ productsLists products customers hold, such as a trial or active subscription.
partnerstack_partner_ overviewUse when asked how one partner is doing.
partnerstack_update_ partnershipChanges one partner's group, tier, manager, partner_key or custom fields.
partnerstack_update_ partnership_ tagsAdds or removes tags on a partner, using add and remove lists.
partnerstack_activity_ summaryUse for what happened recently in the program.
partnerstack_list_ custom_ reportsLists the custom reports saved under Performance in PartnerStack, with each report's key and name.
partnerstack_read_ report_ exportUse to read the rows of an export.
partnerstack_run_ custom_ reportUse to read a report saved under Performance in PartnerStack.
partnerstack_create_ leadCreates a lead for a partner.
partnerstack_get_ leadReads one lead.
partnerstack_list_ leadsLists leads partners submitted, newest first.
partnerstack_update_ leadChanges a lead, such as its status or amount in cents.
partnerstack_create_ customerAdds a customer credited to a partner.
partnerstack_get_ customerReads one customer.
partnerstack_list_ customersLists customers referred by partners, newest first.
partnerstack_list_ webhooksLists webhooks in your program, with their events and target URLs.
partnerstack_update_ customerChanges a customer.
partnerstack_decide_ applicationApproves or declines one application.
partnerstack_list_ applicationsLists applications to join your program, newest first.
partnerstack_create_ rewardGives a partner a reward, which can be real money.
partnerstack_create_ transactionRecords a customer payment, which can pay partners real rewards unless the customer is a test customer.
partnerstack_list_ actionsLists recorded actions, newest first: what a partner or customer did, such as a demo or a signup step.
partnerstack_list_ rewardsLists partner rewards, newest first.
partnerstack_list_ transactionsLists customer transactions, newest first.
partnerstack_record_ actionRecords that a partner or customer did something, and how many times.
partnerstack_rewards_ summaryUse for reward totals: how much was earned, pending or paid.
partnerstack_list_ marketplace_ programsPartner keys only.
partnerstack_list_ groupsLists partner groups, such as Affiliates or Resellers, with each group's key, slug and name.
partnerstack_list_ partnership_ linksLists a partner's referral links.
partnerstack_list_ payoutsPartner keys only.
partnerstack_archive_ dealArchives a deal.
partnerstack_assign_ partnership_ to_ dealAssigns a deal to a partner.
partnerstack_convert_ dealTurns a won deal into a customer, credited to the deal's partner.
partnerstack_get_ deal_ fileAnswers a link to download one file on a deal.
partnerstack_get_ deal_ form_ templatesReads 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_ filesLists files attached to a deal, with each file's key for partnerstack_get_deal_file.
partnerstack_add_ partner_ team_ memberInvites someone to a partner's team, which emails them.
partnerstack_archive_ partnershipRemoves a partner from your program by archiving the partnership.
partnerstack_create_ productRecords that a customer holds a product.
partnerstack_create_ product_ bookAdds a product to your product book.
partnerstack_delete_ productDeletes a customer's product.
partnerstack_delete_ product_ bookDeletes a product book entry.
partnerstack_get_ productReads one customer's product, by its PartnerStack key or external key.
partnerstack_get_ product_ bookReads one product book entry, by its PartnerStack key or external key.
partnerstack_list_ product_ booksLists your product book: the products you sell through partners.
partnerstack_update_ partnerships_ groupMoves several partners to another group at once.
partnerstack_update_ productChanges a customer's product, such as moving it from trial to active.
partnerstack_update_ product_ bookChanges a product book entry's name or description.
partnerstack_create_ tierCreates a partner tier in a tier collection, with its benefits and criteria.
partnerstack_create_ tier_ collectionCreates a tier collection.
partnerstack_export_ base_ recordsQueues a bulk CSV export of partners, customers, transactions, rewards, leads, deals, applications or training.
partnerstack_export_ custom_ reportQueues a CSV of a saved report, which emails member_email when ready.
partnerstack_get_ custom_ reportReads one saved report's settings, not its rows.
partnerstack_get_ report_ exportChecks a queued export.
partnerstack_get_ tierReads one tier.
partnerstack_get_ tier_ collectionReads one tier collection.
partnerstack_list_ tier_ collectionsLists your tier collections, with each collection's key.
partnerstack_list_ tiersLists partner tiers.
partnerstack_update_ tierChanges a tier's name, benefits or criteria.
partnerstack_update_ tier_ collectionChanges a tier collection.
partnerstack_archive_ leadArchives a lead.
partnerstack_convert_ leadTurns a lead into a customer, credited to the lead's partner.
partnerstack_get_ lead_ form_ templatesReads 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_ webhookStops a webhook.
partnerstack_create_ webhookSends chosen PartnerStack events to a URL.
partnerstack_delete_ customerDeletes a customer.
partnerstack_get_ webhookReads one webhook.
partnerstack_update_ webhookChanges a webhook's events or URL.
partnerstack_create_ applicationCreates an application on someone's behalf.
partnerstack_decide_ applications_ bulkApproves or declines several applications at once.
partnerstack_archive_ actionArchives an action, and any rewards or drip rewards tied to it.
partnerstack_delete_ transactionDeletes a transaction.
partnerstack_get_ marketplace_ programPartner keys only.
partnerstack_convert_ click_ to_ customerServer-to-server tracking: credits a signup to the partner whose link was clicked.
partnerstack_list_ disti_ listing_ categoriesLists the category names PartnerStack uses for distribution listings, with AppDirect ids.
partnerstack_list_ form_ templatesLists the custom forms in your program, for links, applications, deals, leads and more.
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.
pk_...••••••••••••3f7a••••••••••••3f7aAdding partners, deciding applications, recording transactions and giving rewards are writes and wait until an owner or admin allows write actions; new connections start read-only. PartnerStack's vendor keys cannot be limited on its side, so this switch in PopMCP is the limit that counts. The AI is told to ask before anything that can pay real money or email someone.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your PartnerStack credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
What happened in our partner program in the last 30 days?
partnerstack_activity_summaryok
Then just ask for the work
“What happened in our partner program in the last 30 days?”
“How is ada@example.com doing as a partner: customers, rewards, links and deals?”
“How much in rewards is pending and approved this quarter, and who earned the most?”
“Who has applied to join our program and is still waiting for a decision?”
“Approve this application and put them in the Resellers group”
“Run our saved Monthly partners report and summarize the top performers”
“Move this deal to Closed Won and turn it into a customer”
“As a partner, which of my programs paid me the most, and what payouts have I had this year?”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting PartnerStack behind an AI client.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Launch a hosted MCP endpoint for PartnerStack, keep tool access under control, and start testing real workflow prompts right away.