{"id":"dev.sparkpay/sparkpay","slug":"dev-sparkpay-sparkpay","title":"SparkPay","description":"Stripe billing for indie apps: plans, coupons, subscriptions, customers and revenue reporting.","version":"1.0.0","publisher":{"kind":"domain","id":"sparkpay.dev","label":"sparkpay.dev","url":"https://sparkpay.dev"},"website":"https://sparkpay.dev","repository":"","remotes":[{"type":"streamable-http","url":"https://sparkpay.dev/api/mcp/mcp"}],"packages":[],"published":"2026-09-16","updated":"2026-09-16","status":"online","auth":"","latency_ms":1115,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_apps","title":"List Apps","description":"List the registered apps (app_id + name). Use this first to discover valid app_id values, then pass one to the other tools to scope results to a single product.","read_only":true},{"name":"list_subscriptions","title":"List Subscriptions","description":"List subscriptions/registrations, newest first. Optionally filter by app_id, status, or payment_type. Returns metadata (email, status, plan, amounts). Use get_customer for a single user, or revenue_summary for totals.","read_only":true},{"name":"get_customer","title":"Get Customer","description":"Look up a customer by email. Returns every subscription/registration for that email across apps (or within one app if app_id is given), with full detail: verification, plan, billing period, usage, refunds. Empty when the email is unknown.","read_only":true},{"name":"list_recent_payments","title":"List Recent Payments","description":"List recent paid transactions (excludes free-tier rows), newest first, ordered by payment date. Optionally scope by app_id. Use to review recent sales activity. Amounts are in the transaction currency (cents).","read_only":true},{"name":"revenue_summary","title":"Revenue Summary","description":"Revenue and subscriber summary in USD cents (normalized from each transaction currency). Returns latest_payments (the MOST RECENT payment summed per customer: a run-rate, NOT lifetime turnover, because amount_paid is overwritten on renewal), refunds, approximate MRR, active/trialing/paid counts, and lifetime_net (the only cumulative total held, accrued per OWNER across all their apps and net of re","read_only":true},{"name":"revenue_by_app","title":"Revenue By App","description":"Per-app rollup in USD cents (latest_payments/refunded/MRR + paid customer count), largest refund-adjusted latest payments first. latest_payments sums the most recent payment per customer, so it is a run-rate and NOT lifetime turnover. No lifetime figure is available per app (accrual is recorded per owner). Use to compare products at a glance; use revenue_summary for one app in depth.","read_only":true},{"name":"list_referrals","title":"List Referrals","description":"List referral records (who referred whom, reward coupon code, pending/rewarded status) with what the referred buyer paid, newest first. Use for working out creator commission: a one_time referredPaymentType means referredAmountPaidCents is the whole sale; for a recurring row it is the LATEST payment, not lifetime, so do not commission on it. Optionally scope by app_id and/or status.","read_only":true},{"name":"affiliate_commissions","title":"Affiliate Commissions","description":"Monthly per-code affiliate commission report, newest month first: attributed paid revenue (USD cents) and what each creator is owed, from the affiliate payment ledger. A payment counts only within 12 months of that buyer's FIRST attributed payment on the code (the first-year deal), and commission is computed per payment at the % frozen when it landed, so later rate changes never rewrite history. R","read_only":true},{"name":"list_recent_cancellations","title":"List Recent Cancellations","description":"Recently canceled paid subscriptions (excludes free rows), most recent cancellation first, with what each customer was paying. Use for churn review; list_subscriptions orders by signup date instead.","read_only":true},{"name":"list_coupons","title":"List Coupons","description":"List discount coupons (code, percent off, expiry, max uses, use count, which paid tiers they apply to). Optionally scope by app_id and/or restrict to currently-active ones (not expired, not maxed out). Read-only: cannot create, edit, or delete coupons.","read_only":true},{"name":"create_coupon","title":"Create Coupon","description":"Create a percentage discount coupon for an app. WRITE, human-gated: a real create requires an elicitation-capable client (e.g. Claude Desktop). The human enters the final code, percent, expiry, visibility, and tier scope in a form; those values OVERRIDE the arguments here, which only pre-fill the form message as a proposal. Clients without elicitation are refused UNLESS the deployment sets SPARK_P","read_only":false},{"name":"bulk_create_coupon","title":"Bulk Create Coupon","description":"Create the SAME discount code across many apps in one call: the portfolio-promo shortcut (e.g. a summer sale on every owned app). WRITE, human-gated: a real create requires an elicitation-capable client; the human enters the coupon terms ONCE in a form (overriding the arguments here) and that one approval covers the whole batch. Clients without elicitation are refused UNLESS the deployment sets SP","read_only":false},{"name":"delete_coupon","title":"Delete Coupon","description":"Delete one coupon from an app. WRITE, human-gated: a real delete requires an elicitation-capable client; the human sees the exact coupon (code, percent, redemption count) and must click approve. The model cannot confirm on its own, and confirm_used is only consulted for dry_run previews. Clients without elicitation are refused UNLESS the deployment sets SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 and ","read_only":false},{"name":"bulk_delete_coupon","title":"Bulk Delete Coupon","description":"Delete the SAME coupon code across many apps in one call: the inverse of bulk_create_coupon, for retiring a portfolio-wide promo. WRITE, human-gated: a real delete requires an elicitation-capable client; the human sees every app the code would be removed from (with per-app redemption counts) and must click approve, and confirm_used is only consulted for dry_run previews. Clients without elicitatio","read_only":false},{"name":"set_coupon_listed","title":"Set Coupon Listed","description":"Show, hide or SCHEDULE an EXISTING coupon on the public pricing pages by setting its `listed` flag and optional `listed_from` start date. WRITE, human-gated: a real write requires an elicitation-capable client and the human sees the code, the discount, which way it is moving and any start date; clients without elicitation pass through, since this only moves a display flag (dry_run works anywhere).","read_only":false},{"name":"set_coupon_affiliate","title":"Set Coupon Affiliate","description":"Mark an EXISTING coupon as a creator's AFFILIATE code at an agreed commission % (the standing deal is 30% of first-year attributed revenue), or clear the mark with percent:null. WRITE, human-gated: a real write requires an elicitation-capable client and the human sees the code and the rate; dry_run works anywhere. From the moment the mark is set, every payment that checks out with the code (and ev","read_only":false},{"name":"list_coupon_invites","title":"List Coupon Invites","description":"List who a coupon was offered to and what they did with it: per-address status (invited / redeemed / revoked), where the invite came from, and the timestamps. Also returns the coupon's own `invite_only` flag -- read that FIRST: when it is false the invite rows are recorded but NOT enforced, and anyone holding the code can still redeem it. Read-only. Use list_coupons for the coupon's terms, invite_","read_only":true},{"name":"invite_to_coupon","title":"Invite To Coupon","description":"Add email addresses to a coupon's invite list and, by default, switch the coupon to invite-only so the list is actually enforced. WRITE, human-gated: a real write requires an elicitation-capable client and the human sees every address plus whether the coupon is about to be closed to everyone else; clients without elicitation are refused unless the deployment sets SPARK_PAY_MCP_ALLOW_UNELICITED_WRI","read_only":false},{"name":"revoke_coupon_invite","title":"Revoke Coupon Invite","description":"Withdraw one address's right to spend a coupon: the targeted block. WRITE, human-gated: a real write requires an elicitation-capable client and the human sees the address and its current status; clients without elicitation are refused unless the deployment sets SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 and the call passes confirm_write:true (dry_run works anywhere). Works on an address that was neve","read_only":false},{"name":"plan_app_kit","title":"Plan App Kit","description":"Step 1 of onboarding a new app onto SparkPay. Recons app_name against existing apps and the rest of the portfolio's plan catalogs, then returns automated findings plus the minimum set of questions that genuinely need a human answer (plan prices, billing model, redirect URLs, trial length, push-webhook opt-in). Pass the answers to create_app_kit next.","read_only":true},{"name":"create_app_kit","title":"Create App Kit","description":"Step 2 of onboarding a new app onto SparkPay. Applies answers.plan_catalog by minting real Stripe prices (same helper /api/apps/sync-plans uses) and registers/updates the app, then returns a downloadable integration kit (lib/spark-pay client + plans.json + sync script + INTEGRATION.md, modeled on still-applying's golden pattern) plus exact post_steps for env vars and secrets. Refuses to overwrite ","read_only":false},{"name":"list_plans","title":"List Plans","description":"Download an app's live plan catalog: tiers, names, prices, trial, and the machine-readable `limits` that gate features inside the app. This is the source of truth each app repo's `bun run plans:sync` regenerates lib/spark-pay/plans.json from, so diff against this rather than trusting the committed file. Stripe price/product IDs are omitted unless include_stripe_ids is set.","read_only":true},{"name":"update_plan_limits","title":"Update Plan Limits","description":"Change the usage limits on an app's existing tiers (e.g. set ai_generations_daily to 200 on pro). WRITE, human-gated: a real write requires an elicitation-capable client; the human sees the per-tier before -> after diff and must click approve. Clients without elicitation are refused UNLESS the deployment sets SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 and the call passes confirm_write:true, which is ","read_only":false},{"name":"update_plan_meta","title":"Update Plan Meta","description":"Set an existing tier's display metadata: its name and the two badge flags the public pricing page styles cards from: is_elite (gold/carbon BEST VALUE card with the rainbow title and app icon) and recommended (MOST POPULAR). A tier called \"Elite\" is NOT styled as elite unless is_elite is actually true on the stored plan; the page reads the flag, never the tier slug, so a catalog whose top tier lack","read_only":false},{"name":"update_plan_pricing","title":"Update Plan Pricing","description":"Change what an app's EXISTING tiers charge: the amount, the billing model (one_time vs subscription), or both. WRITE, human-gated at the highest tier: a real write requires an elicitation-capable client, and the human types the tier, billing model and price into a form. Those typed values OVERRIDE the arguments here, which only pre-fill the proposal, so the model cannot move a price on its own. Cl","read_only":false},{"name":"archive_plan","title":"Archive Plan","description":"Remove a tier from an app's plan catalog. WRITE, human-gated: a real write needs an elicitation-capable client and the human must approve; dry_run previews anywhere. Every other plan tool edits tiers that already exist, so a catalog could grow but never shrink, and collapsing a multi-tier page down to a single offer was a dashboard-only job. Stripe products and prices are deliberately left intact,","read_only":false},{"name":"setup_pricing_page","title":"Setup Pricing Page","description":"Guided, stage-chained wizard that configures an app's hosted pricing page end to end: plan billing model + price (with clickable recommendations), plan name and badge (elite/recommended), optional free tier, a seasonal coupon (SUMMER26-style code suggested from the current season), favicon-derived theme color + card style, and FAQ content. WRITE, human-gated per stage: each call runs AT MOST ONE e","read_only":false}],"server_info":{"name":"spark-pay","version":"1.0.0"},"category":"finance","tags":["support","analytics","developer"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-16","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/dev-sparkpay-sparkpay/"}