May 3, 2026

Whop MCP Claude Setup

A practical Claude setup guide for Whop MCP, covering Claude Web, Claude Desktop, safe first prompts, and common connection failures.

Summary

Claude can connect to Whop through the official Whop remote MCP server. Claude Web uses a custom connector pointed at https://mcp.whop.com/sse. Claude Desktop uses mcp-remote because the desktop app expects a local command that can bridge to the remote MCP endpoint.

The important part is not just making the connection work. The important part is starting with the right permissions and the right first prompt. Whop MCP can expose real business data and, depending on the key you authorize, may allow the agent to call tools that create, update, cancel, or refund things. Treat setup like connecting an operations console, not like installing a browser extension.

Before you connect Claude to Whop

You need three things:

Use a Company API Key when Claude should work only with your own company data. Use an App API Key only when you are building an app that needs access across companies that installed it. If you are unsure, start with the company-scoped key and keep the first session read-only.

Claude Web setup

Claude Web connects to the Whop API MCP server as a remote connector.

  1. Open Claude Web.
  2. Go to Settings.
  3. Open Connectors.
  4. Choose the option to add a custom connector.
  5. Add this MCP server URL:
https://mcp.whop.com/sse

Claude should ask you to authorize the connector. When it does, provide the Whop API key that matches the scope of work. Do not use a broader key just because it is convenient. If the task is reporting, the key should not need every possible write permission.

Claude Desktop setup

Claude Desktop needs a local command that connects to the remote MCP server. The common pattern is mcp-remote.

On macOS, edit:

~/Library/Application Support/Claude/claude_desktop_config.json

On Windows, edit:

%APPDATA%\Claude\claude_desktop_config.json

Add this server configuration:

{
  "mcpServers": {
    "whop_sdk_api": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.whop.com/sse"]
    }
  }
}

Quit Claude Desktop completely and reopen it. Closing the window is not always enough. After restart, look for the MCP tools indicator and ask Claude to list the available Whop tools before asking it to touch account data.

The first prompt should be boring

The safest first prompt is not "optimize my store" or "fix failed payments." It should be a connection test.

Use:

List the available Whop MCP tools. Do not call any tool that creates, updates, deletes, cancels, refunds, or modifies data.

Then ask a second read-only question:

Use Whop MCP only for read-only inspection. Summarize what resources you can access, which company or app context appears available, and which actions would require extra approval.

This gives you three signals: Claude can see the server, the authorization worked, and the agent understands the boundary between inspection and mutation.

Safe operating pattern

Once the connection works, use a two-step pattern for any real task.

First ask Claude to propose a plan without calling write tools:

I want to review failed payments from the last 7 days. First explain which Whop MCP tools you would call and whether each call is read-only.

Then allow read-only calls:

Run the read-only calls only. Summarize the failed payment count, affected products, and any repeated failure reasons. Do not refund, cancel, pause, message, or modify anything.

Only after that should you approve a write action, and only if the arguments are visible and specific.

Common Claude setup failures

If Claude Web does not connect, check that the connector URL is exactly https://mcp.whop.com/sse. A missing protocol, trailing typo, or copied Markdown quote can break setup.

If Claude Desktop does not show the server, check the JSON first. A single missing comma can prevent all MCP servers from loading. Then confirm Node.js is installed and npx works in a normal terminal.

If Claude can see tools but every call fails, the connection may be fine and the API key may be the problem. Try a simpler read-only request. If that fails too, rotate the key or create one with the right scope.

If Claude keeps using stale authorization, restart the client and clear the MCP authorization cache if your local setup documents that option.

When Claude is the right client

Claude is useful when the work is interpretive: summarize payments, explain what a tool can do, draft a safe action plan, compare products or memberships, or turn raw API data into a report. Cursor or VS Code may be better when you are editing a Whop app codebase at the same time.

For seller operations, Claude works best when you keep the task narrow:

Related guides

Official references