Integration

Kiwify integration

Kiwify is a Brazilian platform for selling digital products (courses, ebooks, memberships, event tickets). Read the account, products, sales (with customer, payment and tracking details), sales statistics, installment plans, balances and payouts, manage affiliates, event participants and webhooks, refund a sale and request a payout. Sales, customers, affiliates, participants and payouts are personal and financial data; refunds and payouts move real money (Kiwify has no sandbox). Not exposed: the token route itself, and updating a webhook (its signing token cannot be passed through LiveContext). Authentication is OAuth client credentials: create an API key in the Kiwify dashboard (Apps > API) and enter its client_id and client_secret; every tool also asks for the account_id shown beside the key, which Kiwify requires in the x-kiwify-account-id header. Rate limit: 100 calls per minute.

Connect Kiwify How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Kiwify.Built from the 22 Kiwify tools below, on the connection you add once.

What you can do with Kiwify

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Webhook, 4 operations

create_webhookCreate webhookPOSTAgents: ask firstCreates a webhook that POSTs Kiwify events (purchases, refunds, chargebacks, subscriptions) to a url that must answer 2xx within 40 seconds. Created with no signing token: until one is set in the Kiwify dashboard, deliveries cannot be verified.
delete_webhookDelete webhookDELETEAgents: ask firstDeletes a webhook: Kiwify stops sending its events at once.
get_webhookGet webhookGETAgents: ask firstReturns one webhook: name, target url, products and the events (triggers) it receives.
list_webhooksList webhooksGETAgents: ask firstLists the account's webhooks: name, target url, products and the events (triggers) each one receives. Paged with page_number and page_size.

Affiliate, 3 operations

get_affiliateGet affiliateGETAgents: ask firstReturns one affiliate: name, email, company, CPF or CNPJ, product, commission and status. Personal data.
list_affiliatesList affiliatesGETAgents: ask firstLists the account's affiliates, filterable by status, product or a search text: name, email, CPF or CNPJ, product, commission and status. Personal data.
update_affiliateUpdate affiliatePUTAgents: ask firstChanges an affiliate's commission or status (active, blocked, refused). Send both values: read get_affiliate first and send the current one you keep. Blocking or refusing stops their sales.

Payout, 3 operations

create_payoutCreate payoutPOSTAgents: ask firstRequests a payout (withdrawal) of the available balance to the account's bank details. MOVES REAL MONEY. Needs a new UUID in Idempotency-Key; reuse it only to retry the same payout. Follow it with get_payout.
get_payoutGet payoutGETAgents: ask firstReturns one payout (withdrawal): amount, status, legal entity and dates. A payout's id is the Idempotency-Key it was requested with.
list_payoutsList payoutsGETAgents: ask firstLists the account's payouts (withdrawals), optionally for one legal entity: amount, status and dates. Paged with page_number and page_size. Financial data.

Balance, 2 operations

get_balanceGet balanceGETAgents: ask firstReturns the available and pending balance of one legal entity of the account (legal_entity_id from get_account_details). Financial data.
list_balancesList balancesGETAgents: ask firstReturns the account balance: available and pending amounts and the legal entity they belong to. Financial data.

Product, 2 operations

get_productGet productGETAgents: ask firstReturns one product with its checkout links, order bumps, offers, subscription plans, event settings and ticket batches, and revenue partners (coproducers, with tax ids).
list_productsList productsGETAgents: ask firstLists the account's products (courses, ebooks, memberships, events) with type, price, currency, status and payment type. Paged with page_number and page_size.

Sale, 2 operations

get_saleGet saleGETAgents: ask firstReturns one sale: status, product, customer (name, email, CPF or CNPJ, phone, address), payment breakdown, card brand and last digits, tracking parameters, coproducers and affiliate. Personal data.
list_salesList salesGETAgents: ask firstLists sales created between start_date and end_date (at most 90 days apart), filterable by status, payment method, product or affiliate. Personal data: customer name, email, CPF, phone and address.

Scheduled installment, 2 operations

get_scheduled_installmentGet scheduled installmentGETAgents: ask firstReturns one Kiwify installment plan with its paid and future installments, amounts, next charge date, customer access, product and customer (name, email).
list_scheduled_installmentsList scheduled installmentsGETAgents: ask firstLists the store's Kiwify installment plans (Parcelado Kiwify), filterable by creation dates (at most 90 days apart), product, offer, payment method, status or customer. Personal data.

Account detail, 1 operation

get_account_detailsGet account detailsGETAgents: ask firstReturns the Kiwify account: company name, director CPF, company CNPJ and its legal entities (ids used by balances and payouts). Personal and tax data.

Participant, 1 operation

list_event_participantsList event participantsGETAgents: ask firstLists the participants of an event product with ticket counters (issued, sold, available, checked in), filterable by check-in, batch, phone, CPF or order. Personal data: names, emails, CPF, phones.

Refund, 1 operation

refund_saleRefund salePOSTAgents: ask firstRefunds a sale to the customer. MOVES REAL MONEY and cannot be undone. Kiwify has no sandbox: only real sales of the account can be refunded.

Stats, 1 operation

get_sales_statsGet sales statsGETAgents: ask firstReturns sales statistics for a period, optionally for one product: total sales and net amount, card approval rate, refund and chargeback rates, boletos generated and paid.

Use Kiwify from Claude Code, Cursor or Codex

Connect Kiwify in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Kiwify operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Kiwify

Create your workspace
Sign up free. Nothing to install.
Connect Kiwify once
Add your Kiwify connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.