whop

name	whop
description	Run a business on Whop: websites on *.whop.app, products, checkout, payments, payouts, memberships, ads, LLC/C-corp formation, bounties, and stats. Use when the user mentions Whop, whop.com, their store, a membership or product, checkout links, payouts or transfers, Meta/TikTok ads, forming a company, or anything the Whop MCP tools provide. Not for the internal `whopdev` local-dev CLI.

Whop

This plugin connects Claude to a live Whop business through the Whop MCP server. Those tools are the way to do everything — there is no second path to prefer, and no CLI to install.

Before anything else

1. Check the connection. Call connection_status. It returns the authenticated identity, the selected account, granted scopes, and tool coverage. If it fails or the plugin's tools are missing, the user has not completed OAuth — tell them to run /whop:whop-connect.
2. Discover, do not guess. Tool names follow <group>_<operation> (payments_list, products_create). Read the tool's own schema before calling it. Never invent a tool name, a field, or an enum value — if you cannot find it, say so and ask.
3. Know the account. connection_status returns account_id, and it is often null — a user grant is not bound to one business. When it is null, nothing is selected for you: get the id from accounts_list and pass account_id (biz_…) explicitly on account-scoped calls. Never assume a default business.

Before any write

Read whop-mcp-safety before your first mutating call in a session. Whop's consequential operations use a prepare-and-confirm handshake plus required attribution fields that are easy to get wrong and expensive to get wrong. That skill is the protocol; this one is the map.