May 3, 2026

Whop MCP Cursor Setup

A practical guide to adding Whop MCP to Cursor, choosing project or global configuration, and testing tools safely.

Summary

Cursor is a strong fit for Whop MCP when you are building or maintaining a Whop-related codebase. It gives the coding agent access to project files and, through MCP, access to Whop documentation or authenticated Whop API tools.

That combination is powerful. It also means you should be deliberate about where the MCP config lives. A project-level config keeps Whop tools attached to the repo where you need them. A global config makes Whop tools available across Cursor, which is convenient but easier to misuse.

Project-level or global setup

Use a project-level setup when Whop MCP should only be available while working on a specific Whop app, automation, or internal tool. This is usually the better default for development teams because the config travels with the project context.

Use a global setup when you are the only operator, you work across several Whop projects, and you understand that Cursor may be able to access Whop tools in any workspace where global MCP servers are enabled.

If you are unsure, start project-level. You can always move to global later.

Add Whop MCP to Cursor

The official Whop MCP server is remote. In Cursor, you can connect through mcp-remote with the Whop SSE endpoint.

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

Cursor's config location can vary by version and whether you use project-level or global settings. The official Whop MCP page documents ~/.cursor/mcp.json for Cursor. If your Cursor UI exposes an MCP settings panel, prefer that UI because it reduces the chance of putting the JSON under the wrong key.

Use Cursor differently than Claude

Claude is useful for conversation and analysis. Cursor is useful when the agent is also editing code. That changes the kinds of Whop MCP tasks that make sense.

Good Cursor tasks:

Risky Cursor tasks:

Cursor can edit files and request MCP tools in the same session. Keep live-account actions separate from code-editing tasks unless you are intentionally testing an integration.

Safe first prompts

Start by asking Cursor to list tools, not to use them:

List the available Whop MCP tools. Do not call any tool that modifies data. Explain which tools look read-only and which might write to Whop.

Then ask for a project-specific plan:

Review this repository and identify where Whop IDs, API calls, checkout links, or membership logic appear. Do not call write-capable Whop tools.

Only after that should you authorize a read call:

Make the minimum read-only Whop MCP calls needed to verify the product and plan IDs used by this project.

Debugging Cursor MCP issues

If the server does not appear, check the JSON shape first. Different MCP clients may use different top-level keys, and Cursor versions have changed how MCP settings are exposed.

If the server starts but tools fail, test whether npx works in your shell. Cursor runs the configured command, so a broken Node.js or npm setup can look like an MCP problem.

If authorization fails, check the API key type. A Company API Key is the normal choice for your own company data. An App API Key is for app developers accessing data across installed companies.

If Cursor keeps using stale context, restart Cursor after changing config. Agent sessions can hold old assumptions even after the MCP server is fixed.

Related guides

Official references