Pick a surface
MCP servers
Whop runs two, and they do different jobs:- The Whop MCP server at
mcp.whop.com/mcpoperates on live Whop data. It connects through a browser sign-in, so you never put an API key in the client config. - The Whop Docs MCP server at
docs.whop.com/mcpsearches and reads this documentation.
Plugins
The Whop plugin bundles the Whop MCP server with skills that teach the agent how to use it. In Grok Build:The skill
Whop’s docs publish an installable agent skill atdocs.whop.com/skill.md. It teaches an agent what Whop is, when to reach for it, and where the API and SDKs live. Install it with the skills CLI:
docs.whop.com/.well-known/agent-skills/index.json. The Whop CLI also ships its own skill for driving the CLI, installed with whop skills add and covered in Agent Mode.
Plain files for agents
You don’t need an MCP client to give an agent good context.- llms.txt indexes every page by product area with a one-line description each, and steers agents toward the current API.
- llms-full.txt is the same corpus expanded, for agents that want everything in one fetch.
- Append
.mdto any docs URL to get the raw Markdown of that page.docs.whop.com/developer/quickstart.mdreturns the source of the quickstart, which is what you want in a context window instead of scraped HTML.
The CLI as an agent tool
The Whop CLI emits machine-readable output on every command, so an agent can call it directly and parse the result. That covers what the API doesn’t: scaffolding a project, running it locally, and deploying. Agent Mode covers the flags. Build with the CLI and Claude walks through it end to end.Where to go next
Connect an MCP server
Setup for the docs and API servers.
Build with the CLI and Claude
Scaffold and ship an app end to end.
Agent Mode
Skills sync and the machine-readable output flags.
Quickstart
The first API call, for you, or for your agent.

