MoneMee MoneMeeLog in
Cursor & Windsurf · guide

How to sell a desktop or web app built in Cursor

Short answer

The simplest way to sell a project built in Cursor is as a download outside the app stores: connect the repo or release asset on MoneMee as a software product, set a price, connect Stripe, share the link – or create the product via MCP straight from Cursor. Buyers pay on the product page and get their personal download link. You write the license terms into the description; optionally MoneMee issues a license key per purchase, which your app verifies.

Cursor and Windsurf often produce desktop tools, Mac apps, CLIs or web apps with a backend. Payment is rarely the problem. The problem is everything around it: how do I deliver, how do I settle the license, how does the buyer get an invoice?

Jump to the steps

€0 per month. A fee only per sale, and it drops as your revenue grows. Payouts via Stripe Connect straight to your bank account.

Last reviewed: 2026-11-05 · MoneMee team

What Cursor does and where it stops

Cursor is an editor with an AI agent: it writes and changes code in your local repo. Hosting, distribution and sales are outside its scope. For a desktop tool that means you need a place where buyers pay, download and get updates, without a store review.

  • Cursor and Windsurf work in your local repo. The result is code or a build artefact, not a sales channel.
  • Desktop distribution outside the stores is technically simple: release asset on GitHub, per-buyer download link via MoneMee.
  • After payment, the license is the next gap. Contractually you settle it in the description; technically your app verifies the license key MoneMee issues per purchase.
  • Because Cursor supports MCP servers, you can also create your product from inside the editor; see the MCP section below.

From the finished Cursor project to a sales link

Five steps for a desktop tool, CLI or self-hosted web app.

  1. Build the release

    Produce the artefact buyers receive: installer, binary, ZIP or simply the source code. Create it as a GitHub release or keep the branch as the delivery state.

  2. Create a software product on MoneMee

    Register, pick the “Software” product type. Enter repo URL, branch and delivery mode “release asset” or “branch ZIP”, add a personal access token with read access.

  3. Write license and description

    Who may use the tool, on how many devices, with which updates? Three sentences in the description are enough to start.

  4. Connect Stripe Connect

    Link once. Payouts go straight to your account.

  5. Publish and share

    monemee.com/@your-name/your-tool is your sales link. Buyers pay as guests and receive download link and invoice. You announce new releases through the product newsletter.

If your project lives in a private GitHub repo you don't need to zip anything: MoneMee connects to the repo with a personal access token and, on publish, either zips the branch or fetches a release asset. Every buyer then gets their own download link.

Publish straight from Cursor: the MCP route

If you work with an AI coding agent you don't have to switch to a dashboard to sell. MoneMee runs an official MCP server. Your agent connects via OAuth 2.1, creates the software product from the session with the `create_software_product` tool and links your GitHub repo in the same call.

Flow diagram: Claude or your agent talks to your authorised MoneMee account through the MCP connector and creates the product in your store.

Your agent talks to your MoneMee account through the MCP connector – after a one-time authorisation, products land directly in your store.

  1. Claude / agent
  2. MCP connector
  3. MoneMee account
  4. Your store
  1. Connect the MCP server

    Add the remote URL https://monemee.com/mcp/v1 to your agent configuration, or run the npm package @monemee/mcp-server locally over stdio. Sign-in uses OAuth 2.1 with PKCE; no manual client registration needed.

  2. Create the product from the session

    Tell your agent what to sell. It calls create_software_product with github_repo_url, github_branch and the delivery mode (branch ZIP or release asset) and writes title and description itself.

  3. Connect Stripe and share the link

    You set up Stripe Connect once in the browser. After that the product is live and you share monemee.com/@your-name/your-tool.

All tools, scopes and OAuth details are in the developer documentation. MoneMee MCP server for developers · Sell MCP servers

What you don't have to build

Six things every app sale involves that you don't have to code, maintain or legally review yourself when you sell through MoneMee.

Checkout

Stripe checkout with guest purchase, no account required. No webhooks, no session logic, no payment backend inside your app.

Invoices

As a business seller, every buyer automatically receives a PDF invoice showing VAT or the German small-business note under § 19 UStG.

Right of withdrawal

Consumers confirm in checkout that their right of withdrawal for digital content expires under § 356 (5) BGB. Withdrawal policy, terms and privacy pages are in place.

Download protection

Each buyer gets a personal, tokenised download link: valid 30 days, maximum three downloads. A forwarded link leads nowhere.

Affiliates

Other creators and promoters market your tool for a commission. Clicks and sales are tracked and paid out separately, without you setting up a partner programme.

Update emails

Every product has a newsletter to its buyers. New version? One send instead of one email per customer.

Hosted app? Your app verifies license keys itself

If your tool runs as a hosted web app, extension or CLI, you don't need a download but a proof of purchase the app can verify itself. MoneMee issues a license key per purchase, which your app verifies via the validation API with one POST request. You can offer the download or repo in addition.

License API available

The license endpoints are live. The guide shows the integration in React, Node, Python, Chrome extensions and CLIs, including a copy-paste prompt for your builder.

Read the guide: license keys for your app

Set it up in one command with the Monemee SDK

There is an open-source SDK for web apps with a login, desktop software and Python tools. The CLI logs you in, creates the product, writes your .env and wires the paywall into your code, starting in test mode.

npx monemee init

Packages: monemee-node (Express, Next.js), monemee-react, monemee-client (Electron, Tauri, extensions, signed for offline use) and monemee for Python.

SDK on GitHub · Documentation · Guides (Electron, Chrome extension, Next.js, Python, Tauri)

What price and license model suit a Cursor project?

For desktop tools and CLIs a one-time purchase fits, with a license per person and a fixed number of their own devices, updates for the current major version included. Major versions as a new product. As long as there is no technical license check, the license is a contractual rule in your description.

Write the rule clearly and briefly, for example: one person, up to three own devices, no redistribution, updates within the version. That is a sufficient basis until license keys are available.

Pricing notes here are orientation, not sales data. MoneMee currently offers one-time purchases.

Selling software for money usually counts as a business activity in Germany: imprint, invoice and withdrawal rules for digital content apply even to a tiny tool. MoneMee handles the withdrawal confirmation in checkout and the invoice for business sellers. Registering your business and filing taxes stays with you.

As a small business under § 19 UStG you sell without showing VAT and the invoice carries the corresponding note. If you sell as a VAT-registered business, the invoice shows VAT. Whether you sell as a private person, small business or registered business is set in your account settings.

Not legal or tax advice. When in doubt, ask a tax advisor or lawyer.

Selling a Mac app outside the App Store is easy. Licensing is the hard part.

From the community, paraphrased

Frequently asked questions

How do I sell an app I built with Cursor?

Build a release or use the branch as the delivery state, create a software product on MoneMee and connect the GitHub repo, set a price, connect Stripe and share the link. If you'd rather stay in the editor, create the product via the MoneMee MCP server straight from Cursor. Checkout, download links and update emails run on MoneMee.

Does this apply to Windsurf too?

Yes. The route is identical: local repo, release or branch, software product on MoneMee. Windsurf supports MCP servers as well.

How do I protect my desktop tool from being passed on?

The download link is per buyer, valid 30 days, three downloads. In addition, your tool verifies the license key MoneMee issues per purchase with one POST request.

Do I have to sign or notarise the app?

That is a question of the operating system, not the sales platform. Explain in the description what buyers can expect on first launch.

Can I sell source code instead of a binary?

Yes. Choose branch ZIP instead of release asset. Many buyers of developer tools prefer the code.

Can I publish from inside Cursor?

Yes, via the MoneMee MCP server. Setup is described in the MCP section of this page and in the developer documentation.

What does selling through MoneMee cost?

No monthly fee. A fee per sale that drops as your revenue grows, plus Stripe fees.

Your tool is done. Selling it takes less than an afternoon.

Register for free, add your repo or ZIP, connect Stripe, share the link. You only pay when you sell.