agent command. Agent mode is a set of flags and integrations on the CLI itself.
Giving an agent Whop’s tools
Connect the Whop MCP server athttps://mcp.whop.com/mcp. It signs in through the browser, needs no API key in the client config, and asks before it runs consequential operations.
Use the CLI alongside it for the things the API doesn’t do: scaffolding a project, running a dev server, and deploying.
whop mcp add registers the CLI itself as a local MCP server instead. Its tools are the CLI’s commands, except sign-in: auth, login, and logout aren’t exposed, so run whop login or set WHOP_API_KEY before the agent starts.
Skills
whop skills add syncs Whop’s skill files into your agent: one whop skill plus playbook references that teach the agent Whop’s payment, app, and ads flows. whop skills list shows what’s installed.
Machine-readable output
Global flags on every command, so an agent can call the CLI directly and parse what comes back:Signing an agent in
For unattended use, pass--api-key or set WHOP_API_KEY. For OAuth, follow the CLI’s own agent guidance. Run whop login --method oauth --format jsonl in the background with output to a file. Open the emitted authorizationUrl in the user’s browser without truncating it, then wait for the final done event.
Next steps
Build with the CLI and Claude
The full agent-in-the-loop workflow.
AI and MCP
Connect the Whop MCP server.

