ClickBank MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLICKBANK_ACCOUNT | Yes | Default nickname (5–10 lowercase alphanumeric). Required for analytics; default for quickstats | |
| CLICKBANK_API_KEY | Yes | Clerk key, including the `API-` prefix | |
| CLICKBANK_DEV_KEY | No | Optional legacy developer key; Authorization becomes `DEV-…:API-…` | |
| CLICKBANK_BASE_URL | No | Override API root | https://api.clickbank.com/rest/1.3 |
| CLICKBANK_ENABLE_WRITES | No | Set to `true` to register refund, product, shipping-notice, and subscription tools | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_analyticsB | Fetch vendor or affiliate analytics by dimension (product, country, tracking id, etc.). Set summarize=true for totals. |
| get_subscription_analyticsC | Fetch subscription details or trends. view selects the ClickBank report (details, next_payment, cancel windows, by_status, trends). |
| list_ordersB | List orders matching date, type, vendor, affiliate, email, or tracking filters. |
| count_ordersB | Count orders matching the same filters as list_orders. |
| get_orderB | Get order details for a receipt ID. |
| get_order_upsellsA | List upsell transactions for a parent receipt. |
| check_order_activeA | HEAD a receipt: active=true if the order is not refunded, charged back, or canceled. 403 is returned as active=false (also used when the receipt is missing or inaccessible). |
| list_productsA | List products for a site nickname. Optionally filter STANDARD or RECURRING. |
| get_productA | Get one product by SKU and site nickname. |
| list_quickstatsB | Daily sale, refund, and chargeback totals for an account and date range. |
| summarize_quickstatsA | Sum sale, refund, and chargeback amounts for an account and date range. |
| list_clickbank_accountsA | List account nicknames the current API key can read. |
| list_shippable_ordersA | List physical-goods orders by shipped status, date range, or receipt. |
| count_shippable_ordersB | Count physical-goods orders matching shipping filters. |
| get_ship_noticesA | Get shipping notices already filed for a receipt. |
| list_ticketsA | Search support, cancel, and refund tickets. Date windows (create/update/close) cannot exceed 7 days. |
| count_ticketsA | Count tickets by type, status, or receipt. |
| get_ticketA | Get one ticket by ID. |
| get_refund_amountsA | Preview how a FULL, PARTIAL_PERCENT, or PARTIAL_AMOUNT refund converts in the customer's currency. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools map cleanly to a distinct resource and action, but the analytics-related tools overlap: get_analytics, get_subscription_analytics, list_quickstats, and summarize_quickstats all offer sales/revenue metrics with fuzzy boundaries. list_orders and list_shippable_orders can also be confused when dealing with physical goods.
Tool names consistently follow a verb_noun snake_case pattern using get_, list_, count_, summarize_, and check_. The conventions are predictable across all resource areas, making the toolset easy to navigate.
19 tools is on the heavy side, especially since three count_* tools duplicate the filtering logic of their list_* counterparts rather than adding new capabilities. The count is still organized and justified by the broad ClickBank domain, but it feels slightly inflated.
Core query workflows are well covered: orders, products, tickets, shipping, subscriptions, analytics, and accounts all have reasonable read operations. The main gaps are the lack of write/update operations and a dedicated refund transaction list, though agents can work around these via order filters and quickstats.