gumroad_create_offer_code
Creates a new offer code for a product
LABSCO SUMMARY
Discount campaigns become something you can start and unwind from a chat window.
Offer codes are where the depth sits: create, read, update and delete are all present, which is enough to run a launch promotion end to end and take it down cleanly afterwards. Products can only be switched on or off — not created, priced or edited — so this operates a catalogue that already exists rather than building one.
What it is
A server over the Gumroad API with 11 tools covering the authenticated user, products, successful sales, and full create-read-update-delete on offer codes.
What you get
- Every product on the account, or one by its id, with enabling and disabling as separate calls
- Successful sales filtered by product, buyer email, order id and a before and after window, paged by page_key
- Offer codes listed for a product or fetched one at a time
- New offer codes created with an amount off, an offer type, a maximum purchase count and a universal flag
- The maximum purchase count of an existing code updated, and codes deleted outright
- The authenticated user's own data, readable with any scope
Requirements
GUMROAD_ACCESS_TOKEN. Its scope decides how much of the surface answers — the user lookup is the one call available with any scope.
Setup effort
One command plus a key — npx gumroad-mcp@latest init, then supply credentials
USE CASES
01
Running a launch-week discount
Create the code with the amount off and a cap on how many can be claimed, list what is already live on the product so two promotions do not overlap, and raise the cap if it runs out early.
02
Ending a promotion without leaving a live code behind
Read the code back by its id to confirm which product it belongs to, then delete it — the codes that get forgotten are the ones nobody listed before the campaign ended.
03
Answering how a product sold last month
Pull the successful sales inside a date window, narrowed to one product or one buyer's email, and fetch the product itself when the numbers need naming.
04
Taking a product off sale while you fix it
Disable it so the page stops selling, do the work, and enable it again — two calls, no editing of the listing in between.
11 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
gumroad_delete_offer_code
Deletes an offer code for a product
gumroad_disable_product
Disables a product by its ID
gumroad_enable_product
Enables a product by its ID
gumroad_get_offer_code
Retrieves a single offer code by its ID for a specific product
gumroad_get_offer_codes
Retrieves all offer codes for a product
gumroad_get_product
Retrieves a single product by its ID
gumroad_get_products
Retrieves all of the products
gumroad_get_sales
Retrieves all of the successful sales
gumroad_get_user
Retrieves the authenticated user's data. Available with any scope.
gumroad_update_offer_code
Updates the max purchase count of an existing offer code for a product
BEFORE YOU INSTALL
What to know first
Tools you get
11 tools when we connected. Five change your live store: gumroad_disable_product and gumroad_enable_product take products off and back on sale, and three offer-code tools create, change and delete discount codes. Check what your client approves automatically.
Requires
- npx on PATH
- GUMROAD_ACCESS_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 11 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Claude Desktop — Guided setup
TERMINAL
npx gumroad-mcp@latest initMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"gumroad": {
"command": "npx",
"args": [
"-y",
"gumroad-mcp@latest"
],
"env": {
"GUMROAD_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}Any MCP client — Self-hosted
ANY MCP CLIENT — SELF-HOSTED · JSON
{
"mcpServers": {
"gumroad": {
"command": "npx",
"args": [
"-y",
"gumroad-mcp@latest"
],
"env": {
"GUMROAD_ACCESS_TOKEN": "<YOUR_TOKEN>",
"GUMROAD_BASE_URL": "<YOUR_GUMROAD_BASE_URL>"
}
}
}
}Only for a self-hosted Gumroad instance: <YOUR_GUMROAD_BASE_URL> is your instance's base URL. The server appends the API version itself, so with <YOUR_GUMROAD_BASE_URL> requests go to <YOUR_GUMROAD_BASE_URL>/v2. <YOUR_TOKEN> is your Gumroad access token.
