May 3, 2026

How to Connect Claude to Whop

A plain-English guide to connecting Claude to Whop with MCP, choosing the right setup path, and testing safely before using live tools.

Summary

Connecting Claude to Whop means giving Claude access to Whop tools through the Model Context Protocol. The official Whop API MCP server is available at https://mcp.whop.com/sse, and Claude can use that endpoint through Claude Web connectors or Claude Desktop with mcp-remote.

The connection is simple. The operational risk is not. Once Claude can use Whop MCP, the useful tasks are things like listing products, inspecting payments, summarizing memberships, checking failed transactions, and drafting account changes. Some tools may be read-only. Others may modify live data. Your setup should make that distinction obvious from the start.

Choose the Claude setup path

Use Claude Web if you want the lowest-friction way to connect to Whop from the browser. You add a custom connector, point it at the Whop MCP endpoint, authorize, and start a chat.

Use Claude Desktop if you prefer a local desktop workflow or already keep MCP servers in your desktop config. Claude Desktop needs a local command because it does not directly run a remote SSE URL as a plain config entry. mcp-remote handles that bridge.

If you are connecting Claude as part of development work, also consider Whop Docs MCP vs Whop API MCP. The docs MCP is for reading documentation. The API MCP is for authenticated account or app data.

Connect Claude Web

In Claude Web:

  1. Open Settings.
  2. Go to Connectors.
  3. Add a custom connector.
  4. Use this URL:
https://mcp.whop.com/sse

When Claude asks for authorization, provide the Whop API key that fits the task. A reporting workflow should not need the same broad access as an app-development workflow.

Connect Claude Desktop

Open the Claude Desktop config file for your operating system and add a Whop MCP server entry.

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

Restart Claude Desktop fully after saving. If Claude was already open, quit the app and relaunch it. MCP server changes often do not load until a full restart.

Test the connection without touching data

Do not start by asking Claude to create a product, refund a payment, or cancel a membership. Use a read-only connection test.

Good first prompt:

List the Whop MCP tools available in this chat. Do not call any tool that modifies data. Group the tools into read-only and write-capable categories if you can infer that from the tool names.

Good second prompt:

Make one read-only test call that confirms the connection works. If a tool call would modify data, stop and ask for confirmation instead.

This sequence proves Claude can see the server and helps you understand the permission surface before doing real work.

What Claude can help with after setup

Once connected safely, Claude is useful for operational summaries and guided changes:

The strongest workflow is still human-reviewed. Ask Claude to gather information, summarize it, and propose actions. Approve write calls only when the target resource, action, and arguments are clear.

Common mistakes

The first mistake is using the wrong MCP server for the job. If you want help understanding Whop documentation, use the docs MCP. If you want Claude to inspect live Whop data, use the API MCP.

The second mistake is using a broad key by default. A key with unnecessary write permissions expands the blast radius of a bad prompt or mistaken tool call.

The third mistake is asking for broad autonomous changes. "Clean up my memberships" is too open-ended. "List memberships with failed payments in the last 7 days and summarize possible next steps without modifying anything" is much safer.

Related guides

Official references