MoneMee MoneMeeLog in
Claude Code · guide

Sell what you built with Claude Code – publish via MCP

Short answer

You sell a tool built with Claude Code without leaving the terminal: connect the official MoneMee MCP server once, tell Claude "Publish this repo on MoneMee for €29" and connect Stripe once. Claude creates the software product from your GitHub repo with `create_software_product`. Checkout, download links, update emails and affiliates then run on MoneMee.

You built a CLI tool, an MCP server, a desktop app or a web tool with Claude Code. The code is in the repo, the README is written. Selling should work the way the build did: from the session, not through a click path in a dashboard.

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 Claude Code does and where it stops

Claude Code writes, tests and commits your code and can talk to external services through MCP servers. It can only sell if a service offers an MCP interface for it. MoneMee does: create a product, link the repo, set a price, all as tool calls from the session.

  • Claude Code builds the product and writes the description. It replaces neither checkout nor invoice nor download protection.
  • Through the MoneMee MCP server (@monemee/mcp-server on npm or the remote URL) Claude creates the software product and links your GitHub repo with branch and delivery mode.
  • You connect Stripe Connect once in the browser. After that no further step needs the dashboard.
  • Typical products: CLI tools, MCP servers, browser extensions, boilerplates, desktop apps as downloads. For hosted tools there are license keys your tool verifies via the validation API.

From the finished Claude Code project to a sales link

The browser route, if you prefer it the classic way. The MCP route follows right below.

  1. Tidy up the repo

    README with installation and usage, no secrets in the repo, optionally a release with a built artefact (binary or ZIP). Create a personal access token with read access.

  2. Create a software product on MoneMee

    Register, pick the “Software” product type, enter repo URL, branch and delivery mode (branch ZIP or release asset).

  3. Write the product page

    What does the tool do, for whom, how is it installed? A terminal screenshot or a short GIF shows more than three paragraphs.

  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.

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 Claude Code: 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 Claude Code tool?

Developer tools are sold as a one-time purchase with a single-user license: use on your own devices, no redistribution, updates for the current major version. That works well for MCP servers and CLIs because buyers install themselves and no hosted check is needed.

A short license in the README and in the product description is enough: who may use it, on how many devices, whether resale is allowed. For team licenses, create a second product with its own price.

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.

The payment is usually the easiest part. A basic license key field is not always enough.

From the community, paraphrased

Frequently asked questions

How do I sell an app I built with Claude Code?

Fastest via MCP: add the MoneMee MCP server to Claude Code (`https://monemee.com/mcp/v1` or the npm package `@monemee/mcp-server`), sign in once via OAuth and ask Claude to publish the repo as a product with a price. Connect Stripe once in the browser, then share the link. Alternatively create the product in the browser: connect the repo, set a price, done.

What does Claude Code need to create a product on MoneMee?

The MoneMee MCP server in its configuration (remote URL or npm package) and a one-time OAuth sign-in. After that the tools are available in the session.

Does MoneMee write the product page automatically from my repo?

No. Claude writes title and description in the tool call; MoneMee builds the page from that. There is no automatic page generated from the README.

Can I sell a private repo?

Yes. MoneMee reads it with your personal access token and zips the branch or fetches a release asset on publish. Buyers receive the archive, not repo access.

How do I sell an MCP server?

As a software product with repo or ZIP, plus installation instructions in the README. There is a dedicated page on selling MCP servers with details.

How do I ship updates?

New branch state or new release, then one email to all buyers through the product newsletter. There is no automatic send on every release.

Can I use the public API instead of MCP?

Yes. The public creator API uses API keys you create in your settings. The documentation is at /api-docs.

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.