Skip to main content
Whop runs two Model Context Protocol (MCP) servers: one that lets agents search and read these docs, and one that lets them operate on live Whop data.
Claude Code and Grok have a Whop plugin that installs this server for you. See Claude Code and Grok.

​
Whop Docs MCP server

Gives AI agents direct access to Whop documentation for accurate guidance while building. Server URL: https://docs.whop.com/mcp
One-click install of the docs server for Cursor: Install MCP Server

​
Whop MCP server

Lets AI agents call the Current API: list resources, create data, and explore your setup interactively. Server URL: https://mcp.whop.com/mcp

​
One URL, every client

All clients connect to the /mcp URL. Clients on older protocol revisions use the same URL with no special configuration.
If you connected using the /sse URL, update it to /mcp. The /sse endpoint has been retired and now returns a 404.

​
Authentication

The server signs you in through the browser, so the whole client config is a URL. Don’t add an API key, a bearer token, or a custom authorization header. On first use your browser opens Whop’s sign-in screen, which lists the scopes the connection requests. Whop holds the credentials server-side. They never reach your client config or the model.

​
What a connection can reach

The grant is you, not one business. Business context is a parameter on each operation, so the agent chooses it per call. The tool surface is a reviewed subset of the API. Endpoints that need a first-party whop.com session are excluded.
Confirmation and idempotency reduce accidental or duplicate actions. They don’t reduce the privileges of the grant. Connect only MCP clients you trust, inspect the actions an agent proposes, and disconnect access when you no longer need it.

​
Confirming consequential operations

Consequential operations run in two calls. The first returns prepared: true with the effect, a signed mcp_confirmation_token, and its expiry. Nothing has executed at that point. Call the same tool again with the same arguments plus the token and a stable idempotency_key to execute. If the arguments change between the two calls, the server returns confirmation_invalid.

​
Retries and idempotency

The idempotency_key is a stable key you pick so a retry replays instead of re-executing. On an uncertain outcome the server’s response says whether to retry with the same key or verify the effect first. Never switch to a new key until you’ve verified what happened.

​
Connect from Claude.ai

  1. Open Claude.
  2. Open Settings, then Connectors.
  3. Select Add custom connector.
  4. Enter the server URL: https://mcp.whop.com/mcp
Disconnect the same way: open the connector and remove it. The grant stops working immediately.

​
When sign-in fails

​
Plain-file access for agents

If you have no MCP client, docs.whop.com/llms.txt indexes every page by product area, and appending .md to any docs URL returns the raw Markdown.

​
Next steps

API overview

How requests, versioning, and pagination work.

Quickstart

Make your first API call in a few minutes.

Test in sandbox

Point your agent at test data before going live.

Whop CLI

Build and manage Whop apps from your terminal.