# Whop Connect

> Connect and verify this workspace's Whop account

- Skill: `whopio/whop-connect` (Agent Skill)
- Install (CLI): `npx skillmds@latest add whopio/whop-connect`
- Raw SKILL.md: https://api.skillmd.com/api/skills/whopio/whop-connect/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: whopio (https://skillmd.com/u/whopio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/whopio/whop-connect

---


# Connect to Whop

Confirm the Whop MCP server is connected and report what the grant can reach. Do not
skip ahead to a business action — this command's only job is the connection.

## Steps

1. **Call `connection_status`.**

   - **It works** → report, in plain language: the authenticated user
     (`user_name`), the permission profile, and how many tools are available.
     Then handle the account:
     - **`account_id` is set** → name the account and its `biz_…` id.
     - **`account_id` is null** → say plainly that no account is selected yet, then
       call `accounts_list`. One account: name it and say it will be used when the
       user passes its id. Several: list them and ask which. None: say the user has
       no Whop business yet and point them at whop.com.

     Do not invent an account, and do not report a null account as if it were one.
     Then stop and ask what they want to do.
   - **The tool is missing entirely** → the MCP server has not loaded. Tell the user
     to open `/plugins` and confirm the `whop` plugin is enabled, then `/mcps` to
     check the `whop` server's state. `grok mcp doctor whop` diagnoses configuration
     and connectivity, and takes `--json`.
   - **It returns unauthenticated** → the OAuth flow has not completed. Tell them to
     open `/mcps`, select `whop`, and press `i` to authenticate. The browser opens to
     Whop for sign-in and authorization. **No API key is involved** — if they are
     reaching for one, that is the wrong path for this server. Grok also triggers
     this flow automatically the first time it uses a Whop tool.

2. **Say what they authorized.** The hosted endpoint requests the MCP `admin` scope:
   full administrative access to the reviewed MCP surface, across *every* business
   the signed-in user manages — not scoped to one business. Worth one sentence so
   they know what they granted, and that they can revoke it from `/mcps` later.