ThriveCart MCP Server

供賣家管理產品、結帳、退款和聯盟行銷夥伴。

託管 MCP 伺服器

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

可安裝到 Claude Code、Codex、Cursor 等客戶端

文件

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

ThriveCart API and MCP server: Let your AI agent run your ThriveCart launches.

ThriveCart has an official REST API and webhooks, but no MCP server of its own, and its API cannot create coupons, clone products or change a product's status (checked 24 Oct 2026). Coupons are still marked "Coming soon" in the developer docs. Cotlet runs 15 ThriveCart tools hosted, over MCP for agents and REST for scripts.

Connect ThriveCart products, transactions and subscriptions to your reporting workflow. Use MCP for your agent or REST from automation tools and scripts.

MCP setup REST API guide

What can you automate in ThriveCart?

  • Create a sale coupon
  • Switch off old coupon codes
  • Clone a product for a new cohort
  • List overdue and paused subscriptions
  • Refund a payment and cancel the plan
  • Approve affiliates with a commission

Does ThriveCart have an MCP server or an API?

  • The API covers 9 of our 15 tools: products, transactions, affiliates, refunds, pause and cancel. It has no list of subscriptions by status, only one customer at a time by email.
  • Zapier has 18 ThriveCart triggers and one action, a raw API request. n8n has no ThriveCart node, only its HTTP Request node.
  • A free MCP server on GitHub wraps the official API with an API key. It stops where the API stops.
What you needOfficial APIGitHub MCP serverCotlet
Refund, pause or cancel a subscriptionYes, in your codeYes, you confirmYes, after your OK
Approve affiliates and set a commissionYes, in your codeSearch and create onlyYes, on Pro+
Create and switch off coupons"Coming soon"NoYes
Clone, disable or archive a productNo, read onlyNoYes
Overdue subscriptions with their MRROne customer at a timeOne customer at a timeYes, as one list
The route ThriveCart providesYes, officialYes, official APIUses the dashboard

Checked 24 Oct 2026. Sources: ThriveCart developer documentation, ThriveCart API reference (Postman), Zapier: ThriveCart integrations, thenavidm/thrivecart-mcp-cli on GitHub

How does Cotlet connect to ThriveCart?

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

We never keep your ThriveCart password, and no coupon, refund or cancellation goes through until you approve it.

Connect ThriveCart 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.

  1. Enable ThriveCart for agents. Create a Cotlet account, sign in to ThriveCart as the account owner in its Cloud Browser, then press Enable for agents.
  2. Add the Cotlet MCP address. Put https://cotlet.dev/mcp/v1 in your agent's MCP server or connector settings.
  3. Let the agent in. Chat apps open a Cotlet sign-in. Editors, n8n and scripts send an API key from the console.

The shared address https://cotlet.dev/mcp/v1 carries ThriveCart next to every other app you enable. Enabled ThriveCart after you connected? Refresh the connector and the new tools appear.

Claude:

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

Claude Code:
claude mcp add --transport http cotlet-thrivecart \
  https://cotlet.dev/mcp/v1 \
  --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-thrivecart": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-thrivecart]
url = "https://cotlet.dev/mcp/v1"
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: thrivecart_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: thrivecart_write

How to use the ThriveCart REST API

Create your Cotlet API key

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

Sign in to ThriveCart in its Cotlet Cloud Browser and enable the app for agents. Use your own ThriveCart account; cloning products requires the account owner.

Make your first ThriveCart API request

REST:

curl https://cotlet.dev/api/v1/thrivecart/products \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read products and choose the right paging method

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": "thrivecart",
  "tool": "list_products",
  "result": {
    "products": [
      {
        "product_id": "12",
        "name": "Landing Page Course",
        "type": "digital",
        "status": "live"
      }
    ]
  }
}

Read result.products; product listing has no pagination input. The default active selection excludes archived products, while status=all includes them.

Transactions and affiliates use a page number rather than a cursor. Transactions allow up to 100 records per page; affiliates use 25.

Compare product settings and subscription status as well as IDs. Read-only reports do not change a checkout or collect a payment.

ThriveCart workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestRead products and product details into a checkout and funnel audit sheet without changing settings.
MakeHTTP > Make a requestRead subscription status into a payment follow-up review queue without charging customers.
Python or Node.jsREST APIPage through transactions to prepare a reconciliation report in your chosen accounting destination.

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

Cotlet reads ThriveCart; 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.

ThriveCart API endpoints and MCP tools

Products

Cloning and new products need the account owner's login; ThriveCart greys both out for sub-users. Archiving keeps the product's stats and transactions.

  • List products (list_products, read): Products in your account with type, status and ID.
  • Get product (get_product, read): One product with its pricing options, bumps, upsells and downsells.
  • Clone product (clone_product, write): Copy a product with its checkout and settings, e.g. for a new cohort.
  • Set product status (set_product_status, write, asks first): Switch a product between live, test and disabled, or archive or restore it.

Coupons

The part ThriveCart's API leaves out. Codes take letters and digits only, and the use cap counts all buyers together.

  • List coupons (list_coupons, read): Coupons with code, discount, status, dates, products and number of uses.
  • Create coupon (create_coupon, write, asks first): New coupon with a fixed or percentage discount, dates, use limit and products.
  • Update coupon (update_coupon, write, asks first): Enable or disable a coupon, or change its discount, dates, use limit or products.

Payments and subscriptions

Your payment processor runs the rebills and retries; ThriveCart records the result. A refund leaves the plan billing until it is cancelled.

  • List transactions (list_transactions, read): Payments, rebills, refunds and cancellations with customer, product, amount and invoice ID.
  • List subscriptions (list_subscriptions, read): Subscriptions with status and next payment, plus the count, monthly recurring revenue and yearly revenue of the filter.
  • Refund transaction (refund_transaction, write, asks first): Full or partial refund of one payment, with an internal note. Does not cancel the subscription.
  • Pause subscription (pause_subscription, write, asks first): Pause billing indefinitely, for a number of billing periods or until a date.
  • Cancel subscription (cancel_subscription, write, asks first): Stop all future payments of a subscription. Cannot be undone.

Affiliates

The affiliate center is a Pro+ feature, so these three need Pro+ or a lifetime license with Pro+.

  • List affiliates (list_affiliates, read): Affiliates with their approval status per product.
  • Approve affiliate (approve_affiliate, write, asks first): Approve or reject a pending affiliate application for one or more products.
  • Set affiliate commission (set_affiliate_commission, write, asks first): Custom commission for one affiliate on one product.

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

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

  • What we store. Your signed-in ThriveCart profile, AES-256-GCM, in Finland. Never the password.
  • What your agent gets. The 15 ThriveCart tools. No cookie and no ThriveCart API key.
  • What the session sees. What the owner login sees: products, buyers' emails, transactions, affiliates.
  • What no tool touches. Payment processor settings, payouts, your plan, password, two-factor and deleting.
  • If ThriveCart asks for a code. With two-factor on, you type the 6-digit code yourself. We hold no authenticator.
  • How to cut access. Disable for agents, reset the browser or delete the key. The next call stops.

A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.

Is it against ThriveCart's terms? Account safety

Except as expressly authorized by these Terms, you may not: ... (d) allow or permit any third party to access or use the Services

ThriveCart Terms of Service, Restrictions, read 24 Oct 2026

Cotlet is a third party acting in your account, so this clause reaches it. The terms also let ThriveCart suspend access for "abusive or excessively frequent use", with no refund. The API key and OAuth apps are the route ThriveCart authorises; the terms name no bots or scraping. We found no public case of a seller closed for automation (checked 24 Oct 2026).

How we keep your account looking like you:

  • Your own owner login, signed in by you
  • One Cloud Browser with its own IP and cookies
  • Coupons, refunds and cancellations wait for your OK
  • You finish sign-in and 2FA yourself
  • If ThriveCart objects, its tools pause for every user within 24 h

If you only need refunds, cancellations and transaction reports, use ThriveCart's own API or a server built on it. Cotlet is for the coupon and product work the API cannot do.

What happens when ThriveCart changes?

  • 12 h between tests of the ThriveCart reads
  • 24 h between tests of coupon and product writes
  • $0 for a call to a ThriveCart tool paused for repair

ThriveCart moved to monthly plans on 15 Jul 2026 and keeps adding features to its dashboard, which changes faster than its API. When a coupon form or the Products page moves, we pause and fix that tool, and a failed call costs nothing. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Finds every payment. Main product, bump and upsell come as separate transactions.
  2. Checks what is left. Amounts already refunded are taken off first.
  3. Waits for your OK. The refund shows up in your Cotlet console.
  4. Cancels the right plan. Only the subscription you refunded; others stay.
ActionUndo
Create or change a couponDisable it with update_coupon; its use history stays
Clone a productArchive the copy with set_product_status
Archive a productRestore it from Archived Products
Pause a subscriptionResume it in the dashboard; a set resume date only ThriveCart support can change
Refund a paymentNo, it goes straight to Stripe or PayPal
Cancel a subscriptionNo, the buyer has to purchase again

8 of 15 tools ask first: every write except clone_product, which only makes a copy you edit later. Switch the wait off per tool if a weekly coupon cleanup should run on its own.

A PayPal refund fails when your PayPal balance is too low. The agent reports it and leaves the refund to you.

MCP call:

{
  "name": "create_coupon",
  "arguments": {
    "name": "Black Friday 30% main course",
    "code": "BLACKFRIDAY",
    "discount_type": "percentage",
    "discount": "30",
    "applies_to": "main_product",
    "product_ids": [
      "12"
    ],
    "starts_on": "2026-11-27",
    "ends_on": "2026-12-01",
    "max_uses": 100
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/thrivecart/coupons \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Black Friday 30% main course","code":"BLACKFRIDAY","discount_type":"percentage","discount":"30","applies_to":"main_product","product_ids":["12"],"starts_on":"2026-11-27","ends_on":"2026-12-01","max_uses":100}'

Tool output:

{
  "coupon_id": "87",
  "name": "Black Friday 30% main course",
  "code": "BLACKFRIDAY",
  "status": "enabled",
  "discount": "30%",
  "applies_to": "main_product",
  "product_ids": [
    "12"
  ],
  "starts_on": "2026-11-27",
  "ends_on": "2026-12-01",
  "max_uses": 100,
  "uses": 0
}

Cron jobs and scripts call the same tools over REST at /api/v1/thrivecart with the same key and price. Affiliate tools on a Standard plan fail, and a failed call costs nothing. The tools table lists the REST path of each tool.

How much does the ThriveCart MCP server cost?

About $14 a month for a course creator with one sale a month, 2,440 credits. ThriveCart still bills your plan as before.

JobCallsCredits
Overdue and paused review, weekly6 × 4240
Sale coupon with old codes retired6 × 160
Coupon cleanup, weekly3 × 4120
Refund a payment and cancel the plan4 × 5200
Approve an affiliate at 40%3 × 8240
Clone a product for the next cohort8 × 180
Cloud Browser, 30 days1,500
Total2,440
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Coupons and products work on Standard; affiliates need Pro+

The month is our example: one sale, 5 refund requests and 8 affiliate approvals. ThriveCart publishes only totals, 75,000+ creators and $8B+ processed. Dollars at the $29 pack rate.

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

OptionWhat it doesWhere it stops
thenavidm/thrivecart-mcp-cliMCP server and CLI, 24 tools on the official API: products, transactions, revenue, customers, refunds, pause, cancel, affiliates. MIT, last commit 5 Oct 2026.No coupons, cloning or product status. Runs on your computer with your API key.
Zapier18 triggers for purchases, rebills, refunds and affiliates, plus a raw API request action, also over Zapier MCP.Same API limits; you build each call.
Pipedream, viaSocket, Open ConnectorHosted or self-hosted ThriveCart connectors over MCP (from search listings).Built on the same API key.
ThriveCart APIREST with webhooks for 21 events, 60 requests a minute.Code you write and host. Coupons "Coming soon".

For refunds, cancellations and revenue reports, the free GitHub server or the API is the plain choice and the route ThriveCart backs. For coupons, cloning a product and a subscription list by status, nothing else reaches them today; Cotlet does that work in your 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 ThriveCart tools go to contact@cotlet.dev.

ThriveCart API and MCP: questions

Can I use the ThriveCart 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 ThriveCart under Integrations in the console and sign in to ThriveCart in its Cloud Browser as the account owner. The trial starts when you sign up, no card asked.

How do I connect ThriveCart to ChatGPT or Claude?

Sign up at cotlet.dev, log in to ThriveCart 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 ThriveCart account through Cotlet, in their phone apps too.

What can ChatGPT do in ThriveCart?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in ThriveCart: create coupons for a sale and retire old ones; review coupon usage and switch off old coupons; clone a product for a new cohort and retire the old checkout. You ask in plain words, and anything that reaches other people waits for your OK first.

Who can clone products?

Only the account owner. In ThriveCart the clone and create-new-product buttons are greyed out for sub-users, so clone_product needs an owner login.

When does a coupon start and stop?

A coupon with a start date works from 00:01 on that day, and one with an end date stops after 23:59:59 on that day. Both follow your ThriveCart time zone settings.

Do I need a ThriveCart API key?

No. Cotlet works in your signed-in dashboard, not through the API, so you create no key in Settings > API & webhooks. That is also why it can reach coupons and products, which the API cannot.

Does it work on a lifetime license?

Yes, on any plan. Affiliate tools need Pro+, which lifetime holders add for $295 a year; everything else works on Standard.

Is the MCP server different from the REST API?

Only the way in. Both carry the same 15 tools, inputs and answers, one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with ThriveCart?

No. Cotlet is independent and not affiliated with ThriveCart LLC.


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.