Payhip MCP Server

Products, orders, coupons, sales stats and buyer tickets for Payhip sellers.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/payhip'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Payhip API and MCP server: Let your AI agent handle your Payhip store.

Payhip has a public API for coupons and software license keys, 4 webhook events and no MCP server of its own (checked 24 Oct 2026). Orders, products, buyers, subscribers and analytics have no endpoints. Cotlet runs 20 Payhip tools hosted, over MCP for agents and REST for scripts.

Read Payhip orders, products and sales reports through MCP or REST. Connect your seller account to agents, automation workflows or scripts.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with Payhip
Page: https://cotlet.dev/integrations/payhip-api-mcp-server

What can you automate in Payhip?

Reset a buyer's download credits
Resend a lost receipt
Compare this week's sales with last
Publish a new digital product
Make a launch coupon
Block a buyer after a dispute

Does Payhip have an MCP server or an API?

The API reference says: "At the moment we only have support for interacting with the Coupon and License Key resources, but more will be added in future."
Webhooks send paid, refunded, subscription.created and subscription.deleted as they happen. A failed delivery is retried once an hour for 3 hours, and past orders never arrive.
Zapier's Payhip app has 5 triggers and no actions, so Zapier MCP has no Payhip step to run.

What you need	Payhip API	Zapier	Cotlet
Create and list coupons	Yes	No	Yes, after your OK
Verify and disable license keys	Yes	No	Not in our tools
Search past orders by buyer email	No	New sales only, polled	Yes
Reset downloads, resend a receipt	No	No	Yes
Sales stats, daily and by referrer	No	No	Yes
Edit or delete a coupon, add a product	No	No	Yes, after your OK

Checked 24 Oct 2026. Sources: Payhip API reference, Payhip Help: Public API, Payhip Help: Webhooks, Zapier: Payhip triggers

How does Cotlet connect to Payhip?

Sign in to Payhip. Use your own account in its Cotlet Cloud Browser.
Choose MCP or REST. Connect your agent or create a Cotlet API key.
Run your workflow. Ask your agent or send an HTTP request.

We never keep your Payhip password or API key, and no receipt, coupon or price change goes live until you approve it.

Connect Payhip to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

Enable Payhip for agents. Create a Cotlet account, log in to your Payhip seller dashboard in its Cloud Browser, then press Enable for agents.
Add the Cotlet address. Put https://cotlet.dev/mcp/v1/payhip in your agent as an MCP server or custom connector.
Approve the connection. Chat apps send you to a Cotlet sign-in. Code editors, n8n and scripts take an API key from the console.

Payhip rides on the shared address, https://cotlet.dev/mcp/v1, next to any other app you enable. Turned Payhip on after you connected? Refresh the connector so the 20 tools appear.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-payhip \
  https://cotlet.dev/mcp/v1/payhip \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-payhip": {
      "url": "https://cotlet.dev/mcp/v1/payhip",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-payhip]
url = "https://cotlet.dev/mcp/v1/payhip"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: payhip_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: payhip_write

How to use the Payhip REST API

Create your Cotlet API key

Create a Cotlet API key with access to Payhip and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Make your first Payhip API request

REST:

curl "https://cotlet.dev/api/v1/payhip/products?limit=2" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read products and follow the cursor

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "payhip",
  "tool": "list_products",
  "result": {
    "products": [
      {
        "product_id": "RGsF",
        "name": "Notion Budget Template",
        "type": "digital",
        "price": "12.00",
        "pay_what_you_want": false,
        "visibility": "visible",
        "views": 340,
        "orders": 21,
        "sales": "252.00",
        "archived": false,
        "url": "https://payhip.com/b/RGsF"
      }
    ],
    "total": 1,
    "next_cursor": null
  }
}

Read result.products and pass result.next_cursor unchanged as cursor until null. Keep filters and limit unchanged while paging.

Product pages default to 25 records, with a maximum of 100. The default listing excludes archived products; use the listing filter when your report needs them.

Compare product views, orders and sales as well as product IDs. Filters are applied before page slicing, so keep the same selection throughout an export.

Payhip workflows for agents and automations

Tool	Connect through	Example workflow
n8n	HTTP Request	Read products and product details into a store catalog sheet, comparing views, orders and sales on refresh.
Make	HTTP > Make a request	Combine orders and order details into a dated fulfillment report in your chosen destination.
Python or Node.js	REST API	Read sales stats and sales reports into a store performance brief, retaining the store's reporting time zone.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Payhip; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Payhip API endpoints and MCP tools

Orders and buyers

The filters of the Customers page, newest first. A reset gives back the product's download limit. These tools need a store that has had orders.

List orders (list_orders, read): Orders with buyer, items, amount, fees and status, filtered by email, product, status or date.
Get order (get_order, read): One order: buyer, items, license keys, amount, fees, VAT, status, checkout answers and note.
Add order note (add_order_note, write): Set the private note on an order; only you see it.
Reset download credits (reset_download_credits, write): Give the buyer of an order their downloads back, up to the product's limit.
Resend receipt (resend_receipt, write, asks first): Email the order's receipt with its download links to the buyer again.
List customers (list_customers, read): Buyers from your newest orders, with order count, total spent and last order.
Block customer (block_customer, write, asks first): Stop an order's buyer from buying from your store again.

Products

New products are digital downloads only, up to 25 MB a file, and start invisible. update_product publishes or hides one.

List products (list_products, read): Products in your store with price, visibility, views, orders and sales.
Get product (get_product, read): One product's title, price, sale price, visibility, description and files.
Create product (create_product, write, asks first): Create a digital product with its file; invisible by default.
Update product (update_product, write, asks first): Change a product's title, price, description or visibility; publish or hide it.

Sales and reports

Days follow your store's time zone. The monthly report lists closed months that had sales.

Get sales stats (get_sales_stats, read): Sales, orders, customers, views and checkouts for a date range, per day, with referrers.
Get monthly sales report (get_sales_report, read): Payhip's monthly sales reports: which months are ready, and one month's summary.

Members, affiliates and followers

Rows come as Payhip shows them. Members of a subscription need Stripe connected in Payhip.

List subscribers (list_subscribers, read): Members of your memberships and subscription products.
List affiliates (list_affiliates, read): Your store's affiliates, active and pending, with their sales count.
List email subscribers (list_email_subscribers, read): People who follow your store and get your email updates.

Coupons

The usage limit counts all buyers together. Payhip has no per-buyer cap.

List coupons (list_coupons, read): Coupon codes with discount, product, uses, limit and dates.
Create coupon (create_coupon, write, asks first): New coupon code for the whole order, one product or a collection.
Update coupon (update_coupon, write, asks first): Change a coupon's code, discount, usage limit, dates or note.
Delete coupon (delete_coupon, write, asks first): Delete a coupon so buyers can no longer use its code.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/payhip-api-mcp-server#tools

Who can see my Payhip session, and how do I revoke it?

What we store. Your logged-in Payhip profile, AES-256-GCM encrypted, in Finland. No password.
What your agent gets. The 20 Payhip tools. Never the cookie or your Payhip API key.
What the session sees. Your store: products, orders, buyer emails, subscribers, sales.
What no tool touches. Stripe and PayPal, payouts, refunds, plan, password, two-factor.
If Payhip asks for a code. With two-factor on, you type the Authenticator code. We never do.
How to cut access. Disable for agents, reset the browser, or change your Payhip password.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). There is no SOC 2 report or third-party pentest yet.

Is it against Payhip's terms? Account safety

If you are found to be selling content that goes against our terms, you risk getting your Payhip account permanently deleted without prior notice.

Payhip Help: What products are not allowed, 26 Jul 2026

Payhip's Terms of Use (last updated 19 Feb 2018) never mention bots, scraping or automated access, and Payhip hands every store an API key and webhooks for scripts. The closures on record are about what a store sells: one review counts 28 one-star reviews Payhip answered, 12 citing PLR and 10 copyright. We found no case of a Payhip account closed for automation (checked 24 Oct 2026).

How we keep your store looking like you:

Your own seller account, logged in by you
One Cloud Browser with a steady IP and cookies
Receipts, products, coupons and blocks wait for your OK
No tool deletes a product or an order
If Payhip objects, we pause the Payhip tools for everyone within 24 h

Resending receipts in bulk sends mail from contact@payhip.com to many buyers at once. Fix tickets one by one, and use Payhip's Email Updates for a whole product.

What happens when Payhip changes?

12 h between tests of the Payhip tools
16/16 checks passed on Nov 6, 2026
$0 for a call to a Payhip tool paused for repair

If Payhip renames a field on the Products page or moves a button, we repair the tool and the call keeps its name and inputs. The tests run on a store of our own without orders, so the order tools are the ones to watch after a Payhip change. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

Finds the order. By the email the buyer wrote from. No match, no guess.
Checks for a refund. get_order shows the status; a refunded order stops the run with a note to you.
Resets the count. Back to your Download Limit, with no email sent.
Waits for your OK. The receipt resend shows in your Cotlet console first.

Action	Undo
Create a coupon	delete_coupon, or Marketing > Coupons; orders that used it keep the discount
Delete a coupon	No, create the code again
Create a product	It starts invisible; delete it in Products
Change a price or publish	Set it back with update_product; orders in between keep the new price
Resend a receipt	No, the email is out
Block a buyer	Remove them on the Blocked List page

7 of 20 tools ask first: everything a buyer sees or that changes what your store sells. reset_download_credits and add_order_note reach nobody, so they run at once. Turn the wait off per tool for a scheduled run.

Refunds are not a Cotlet tool. Payhip sends them through Stripe or PayPal, and a refunded buyer loses access to the product.

MCP call:

{
  "name": "create_coupon",
  "arguments": {
    "code": "WELCOME5",
    "discount_type": "fixed",
    "amount": "5.00",
    "applies_to": "total_order",
    "usage_limit": 100,
    "starts_on": "2026-11-01",
    "notes": "New subscriber welcome"
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/payhip/coupons \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"code":"WELCOME5","discount_type":"fixed","amount":"5.00","applies_to":"total_order","usage_limit":100,"starts_on":"2026-11-01","notes":"New subscriber welcome"}'

Tool output:

{
  "coupon_id": "1495928940",
  "code": "WELCOME5",
  "discount_type": "fixed",
  "amount": "5.00",
  "applies_to": "total_order",
  "collection_name": null,
  "product_id": null,
  "product_name": null,
  "product_url": null,
  "usage_limit": 100,
  "uses": 0,
  "starts_on": "2026-11-01",
  "expires_on": null,
  "one_item_only": false,
  "notes": "New subscriber welcome"
}

A cron job or script calls the same tools over REST at /api/v1/payhip, with one key and one price. If you already script coupons against Payhip's own API, keep it; Cotlet covers the orders, downloads and members it cannot reach. A failed call costs nothing. The tools table lists the REST path of each tool.

How much does the Payhip MCP server cost?

About $12 a month for a store with about 60 orders and 8 download tickets a month, 2,150 credits. Payhip keeps billing its own plan and fee.

Job	Calls	Credits
Buyer download ticket, fixed and noted	5 × 8	400
Weekly sales and buyer sources	2 × 4	80
Monthly sales report	1 × 1	10
Launch coupon for a new product	3 × 2	60
Publish a new digital product	3 × 2	60
Price change on a product	2 × 2	40
Cloud Browser, 30 days		1,500
Total		2,150

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
Works on Payhip Free Forever, Plus and Pro

The month is our example, since Payhip publishes no orders per seller: a few digital products, two launches. Payhip itself is $0, $29 or $99 a month with a 5%, 2% or no fee. Dollars at the $29 pack rate.

Payhip MCP server on GitHub, Zapier or hosted: which to use

Option	What it does	Where it stops
Pipedream	Hosted MCP with 3 actions (verify, enable, disable license key) and 4 webhook triggers.	No coupons list, orders, products or members.
Composio	Hosted Payhip MCP, 9 tools: coupons and the 4 webhook events.	Same coupon and event API; nothing for tickets or sales.
Zapier	5 polling triggers: new sale, refund, new product, membership started or cancelled.	No actions, so an agent can read new events and change nothing.
License key bots on GitHub, such as KeyVerify	Activate Payhip license keys from Discord, 1 star.	License keys only. No Payhip MCP server exists on GitHub.

For license keys, Pipedream or Payhip's own API is the right tool, and we do not wrap them. For buyer tickets, products, sales numbers and members there is no API to wrap, which is the part Cotlet does in your logged-in dashboard.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Payhip tools go to contact@cotlet.dev.

Payhip API and MCP: questions

Can I use the Payhip API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

How do I get access?

Create a free account at https://cotlet.dev, open Payhip under Integrations in the console and log in to Payhip in its Cloud Browser. The trial starts when you sign up, no card asked.

How do I connect Payhip to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Payhip once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Payhip account through Cotlet, in their phone apps too.

What can ChatGPT do in Payhip?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Payhip: fix download limit errors and resend download links; weekly sales summary; create a coupon for a launch. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need a paid Payhip plan?

Payhip lists the same features on Free Forever, Plus and Pro, with no feature-gating, and the plans differ in transaction fee (5%, 2% and none) (checked 11 Oct 2026). A free store works.

Do the order tools work on a store with no orders?

The tools are built, but they need an order to act on. Payhip only sells once the seller has connected PayPal or Stripe, and Cotlet never connects one for you. On a new store list_orders returns an empty list, and get_order, add_order_note, resend_receipt, reset_download_credits and block_customer have nothing to open. The same holds for the rows of list_subscribers (Stripe needed), list_affiliates, list_customers and get_sales_report. Products, coupons, followers and sales stats work from the first day.

What can it not do yet?

Cancel a subscription, refund an order (refunds are made in PayPal or Stripe), create courses, coaching, memberships or physical products, edit products with variants, archive or delete a product, unblock a buyer, manage collections, shipping or license keys, and read the location map of Analytics. Order lists show the newest 25 orders at most, and list_customers groups only those.

How does create_product send the file?

The file goes in the call itself, up to 25 MB, and Cotlet uploads it to Payhip as Add Product does. The product starts invisible; update_product with visibility visible publishes it.

Which time zone do dates use?

Your store's time zone, set under Account > Settings. get_sales_stats days follow it, and order and coupon dates are plain dates (YYYY-MM-DD).

Does add_order_note keep my old note?

No. An order has one note, so the new text replaces it. Read the note with get_order first to add to it.

Does Payhip have webhooks?

Yes, 4: paid, refunded, subscription.created and subscription.deleted, set under Settings > Developer. They report events as they happen. To look back at older orders, an agent calls list_orders instead.

Can the agent manage license keys?

Not through Cotlet. Payhip's own API verifies, enables and disables license keys, and Pipedream wraps those calls for agents.

Can the agent refund a buyer?

No. Payhip refunds go through your Stripe or PayPal account, and no Cotlet tool touches either. The agent can find refunded orders and leave them alone.

Is the MCP server different from the REST API?

Only the entry point differs. Both carry the same 20 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Payhip?

No. Cotlet is independent and not affiliated with Payhip Limited.

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.