Serveur MCP
SparkPay
dev.sparkpay/sparkpay
Entreprise et opérations
Outils développeur
Paiements et fintech
Public et accessible
MCP 2025-11-25
Ce que fait ce MCP
Manages Stripe-based billing for indie applications, including plans, pricing, coupons, subscriptions, customers, revenue reporting, and integration kits.
Capacités
Outils
25
outils
archive_plan
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, exactly as update_plan_pricing leaves the old price behind: removing the row stops the plan being offered and never reaches into anyone's existing subscription. Refuses while the tier still has non-cancelled subscribers (matched on its Stripe price ids, since subscriptions carry a price rather than a tier slug), and refuses to remove an app's last remaining tier. Run `bun run plans:sync` in the app repo afterwards to regenerate plans.json.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'tier'], 'properties': {'tier': {'type': 'string'}, 'app_id': {'type': 'string'}, 'dry_run': {'type': 'boolean', 'default': False}}}
bulk_create_coupon
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 (dry_run still works anywhere). Runs each app through the same fully-guarded create as create_coupon. Unlike a single call it does NOT fail the batch when an app already has the code: that app is reported `skipped` and the rest are still created. Returns a per-app outcome matrix plus created/skipped/failed counts. Use dry_run:true first to see which apps would create vs skip. Pass explicit app_ids (from list_apps). There is deliberately no 'all apps' shortcut, so a discount can't hit an app you didn't name.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_ids', 'code', 'discount_percent'], 'properties': {'code': {'type': 'string'}, 'listed': {'type': 'boolean', 'default': False}, 'app_ids': {'type': 'array', 'items': {'type': 'string'}}, 'dry_run': {'type': 'boolean', 'default': False}, 'max_uses': {'type': 'number'}, 'expires_at': {'type': 'string'}, 'description': {'type': 'string'}, 'applies_to_tiers': {'type': 'array', 'items': {'type': 'string'}}, 'discount_percent': {'type': 'number'}, 'confirm_high_discount': {'type': 'boolean', 'default': False}}}
bulk_delete_coupon
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 elicitation are refused (dry_run still works anywhere). An app that never had the code is reported `skipped` rather than failing the batch, since the desired end state already holds there. Returns a per-app outcome matrix plus deleted/skipped/failed counts. Use dry_run:true first to see exactly which apps would lose the code. Pass explicit app_ids (from list_apps) so a delete can't hit an app you didn't name.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_ids', 'code'], 'properties': {'code': {'type': 'string'}, 'app_ids': {'type': 'array', 'items': {'type': 'string'}}, 'dry_run': {'type': 'boolean', 'default': False}, 'confirm_used': {'type': 'boolean', 'default': False}}}
create_app_kit
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 an existing app's plans unless answers.confirm_overwrite is true. Real secrets (a push-mode webhook secret) are only ever returned in post_steps, never written into a kit file.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_name', 'answers'], 'properties': {'answers': {'type': 'object', 'required': ['plan_catalog', 'success_url', 'cancel_url'], 'properties': {'push_mode': {'type': 'boolean', 'default': False}, 'cancel_url': {'type': 'string'}, 'trial_days': {'type': 'number'}, 'success_url': {'type': 'string'}, 'plan_catalog': {'type': 'array', 'items': {'type': 'object', 'required': ['tier', 'name', 'monthly_price'], 'properties': {'name': {'type': 'string'}, 'tier': {'type': 'string'}, 'amount': {'type': 'number'}, 'trial_days': {'type': 'number'}, 'payment_type': {'enum': ['free', 'subscription', 'one_time', 'contact'], 'type': 'string'}, 'yearly_price': {'type': 'number'}, 'monthly_price': {'type': 'number'}}}}, 'confirm_overwrite': {'type': 'boolean', 'default': False}}}, 'app_name': {'type': 'string'}}}
create_coupon
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 (dry_run still works anywhere). Inserts a `coupons` row and best-effort-mints the matching Stripe coupon (checkout backfills it on first use if Stripe is unreachable). The code is uppercased and must be unique per app. By default the coupon applies to every paid tier. Set dry_run:true first to preview the exact row without writing. Cannot discount a free-only app. Three house rules are enforced and cannot be argued out of: every coupon expires within 6 months (omitting expires_at means the 6-month term, not a code that never expires); a coupon at 90%+ is created invite_only, so it is redeemable only by addresses added with invite_to_coupon; and a 90%+ coupon is pinned to the second-highest paid recurring tier and may never cover the top tier or a one-time (lifetime) plan. Use list_coupons afterwards to confirm, and list_plans to see an app's tier slugs.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'code', 'discount_percent'], 'properties': {'code': {'type': 'string'}, 'app_id': {'type': 'string'}, 'listed': {'type': 'boolean', 'default': False}, 'dry_run': {'type': 'boolean', 'default': False}, 'max_uses': {'type': 'number'}, 'expires_at': {'type': 'string'}, 'description': {'type': 'string'}, 'applies_to_tiers': {'type': 'array', 'items': {'type': 'string'}}, 'discount_percent': {'type': 'number'}, 'confirm_high_discount': {'type': 'boolean', 'default': False}}}
delete_coupon
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 (dry_run still works anywhere). Removes the Stripe coupon object and then the `coupons` row, exactly like the dashboard's delete, so no orphaned Stripe object is left behind. Deleting is permanent and the code becomes reusable afterwards. Set dry_run:true to see exactly which coupon would go (and its redemption count) without touching anything. Use list_coupons first to confirm the code.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'code'], 'properties': {'code': {'type': 'string'}, 'app_id': {'type': 'string'}, 'dry_run': {'type': 'boolean', 'default': False}, 'confirm_used': {'type': 'boolean', 'default': False}}}
get_customer
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.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['email'], 'properties': {'email': {'type': 'string'}, 'app_id': {'type': 'string'}}}
invite_to_coupon
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 (dry_run works anywhere). Addresses are lowercased and de-duplicated, malformed ones are reported rather than dropped, and an address already on the list is left exactly as it is -- so re-inviting someone who already redeemed does NOT hand them a second free account, and re-inviting someone who was revoked does NOT un-block them. Set enforce_invite_only:false only to stage a list before gating the code; the result then carries a warning that the coupon is still open. Use dry_run:true first to see exactly who would be added.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'code', 'emails'], 'properties': {'code': {'type': 'string'}, 'app_id': {'type': 'string'}, 'emails': {'type': 'array', 'items': {'type': 'string'}}, 'source': {'type': 'string'}, 'dry_run': {'type': 'boolean', 'default': False}, 'enforce_invite_only': {'type': 'boolean', 'default': True}}}
list_apps
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.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
list_coupon_invites
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_to_coupon to add addresses, revoke_coupon_invite to withdraw one.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'code'], 'properties': {'code': {'type': 'string'}, 'app_id': {'type': 'string'}}}
list_coupons
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.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'number', 'default': 50}, 'app_id': {'type': 'string'}, 'active_only': {'type': 'boolean', 'default': False}}}
list_plans
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.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id'], 'properties': {'app_id': {'type': 'string'}, 'include_stripe_ids': {'type': 'boolean', 'default': False}}}
list_recent_cancellations
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.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'number', 'default': 25}, 'app_id': {'type': 'string'}, 'include_samples': {'type': 'boolean', 'default': False}}}
list_recent_payments
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).
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'number', 'default': 25}, 'app_id': {'type': 'string'}, 'include_samples': {'type': 'boolean', 'default': False}}}
list_referrals
List referral records (who referred whom, reward coupon code, pending/rewarded status), newest first. Optionally scope by app_id and/or status.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'number', 'default': 25}, 'app_id': {'type': 'string'}, 'status': {'enum': ['pending', 'rewarded'], 'type': 'string'}, 'include_samples': {'type': 'boolean', 'default': False}}}
list_subscriptions
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.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'number', 'default': 25}, 'app_id': {'type': 'string'}, 'status': {'enum': ['active', 'trialing', 'past_due', 'canceled'], 'type': 'string'}, 'payment_type': {'enum': ['free', 'subscription', 'one_time', 'payg'], 'type': 'string'}, 'include_samples': {'type': 'boolean', 'default': False}}}
plan_app_kit
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.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_name'], 'properties': {'app_name': {'type': 'string'}}}
revenue_by_app
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.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'include_samples': {'type': 'boolean', 'default': False}}}
revenue_summary
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 refunds; null when no accrual record exists). lifetime_net counts only charges whose Stripe webhook reached this app, so a missing renewal event under-counts it silently. A 0 or a low figure means "not recorded here", never "no sales". For turnover, accounts or tax, read Stripe directly: it is authoritative, and this database cannot reconstruct lifetime gross. Optionally scope by app_id; omit for platform-wide totals.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'app_id': {'type': 'string'}, 'include_samples': {'type': 'boolean', 'default': False}}}
revoke_coupon_invite
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 (dry_run works anywhere). Works on an address that was never invited too, writing a revoked tombstone, so blocking someone does not depend on whether they were on the list and survives a later bulk re-invite. This only blocks FUTURE redemptions: if the status was already `redeemed` the discount has been granted, and undoing that means cancelling or refunding the subscription in the dashboard. Prefer this over delete_coupon when one recipient misbehaves -- deleting the code punishes every other invitee. Use list_coupon_invites first to see the current status.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'code', 'email'], 'properties': {'code': {'type': 'string'}, 'email': {'type': 'string'}, 'app_id': {'type': 'string'}, 'reason': {'type': 'string'}, 'dry_run': {'type': 'boolean', 'default': False}}}
set_coupon_listed
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 are refused (dry_run works anywhere). These are deliberately the ONLY fields an agent can change on a live coupon: the percent, expiry and tier scope are terms somebody may already have been quoted, while `listed`/`listed_from` are purely a display decision. Together they decide whether the public coupons API returns the code today, which is what every app's promo bar draws from; the discount itself does not move and no Stripe object is touched. `listed_from` in the future STAGES a seasonal coupon so it appears on its own date with no cron: it never blocks anyone holding the code from redeeming it, it only holds the code back from the promo bar. Listing with no `listed_from` clears any existing schedule (lists now). Listing an INVITE-ONLY coupon is refused outright, since that would advertise a near-free code to people who cannot redeem it. A `listed_from` with listed:false is refused as a contradiction. Listing an expired/maxed coupon, or scheduling a start at or after expiry, is allowed but warns. A coupon already in the requested state reports `noop`. Use list_coupons first to see codes and their current visibility.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'code', 'listed'], 'properties': {'code': {'type': 'string'}, 'app_id': {'type': 'string'}, 'listed': {'type': 'boolean'}, 'dry_run': {'type': 'boolean', 'default': False}, 'listed_from': {'type': 'string'}}}
setup_pricing_page
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 elicitation form and commits only that stage, then returns next_call for the model to continue (stages: overview -> plans -> coupon -> branding -> content -> finish). The values the HUMAN types in each form OVERRIDE the arguments here - args only pre-fill form defaults (pass price_suggestions from market research and faq_drafts to seed them). Testimonials are NOT configurable here: they are collected from real customers on Sellular and rendered from there. Form stages are refused on clients without elicitation; overview/finish are read-only recon and work anywhere, as does dry_run (echoes the form + would-be writes, writes nothing). A declined stage leaves earlier committed stages applied - each stage is individually approved, and each effect is reversible via the standalone tools. Stripe prices are minted only by the plans stage with human-typed amounts (existing paid tiers only; free tiers never touch Stripe). After plan changes, run `bun run plans:sync` in consumer app repos. Use list_apps first for app_id.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id'], 'properties': {'tier': {'type': 'string'}, 'stage': {'enum': ['overview', 'plans', 'coupon', 'branding', 'content', 'finish'], 'type': 'string', 'default': 'overview'}, 'app_id': {'type': 'string'}, 'domain': {'type': 'string'}, 'dry_run': {'type': 'boolean', 'default': False}, 'faq_drafts': {'type': 'array', 'items': {'type': 'object', 'required': ['question', 'answer'], 'properties': {'answer': {'type': 'string'}, 'question': {'type': 'string'}}}}, 'coupon_code': {'type': 'string'}, 'discount_percent': {'type': 'number'}, 'price_suggestions': {'type': 'array', 'items': {'type': 'object', 'required': ['amount_cents', 'billing'], 'properties': {'tier': {'type': 'string'}, 'label': {'type': 'string'}, 'billing': {'enum': ['one_time', 'subscription'], 'type': 'string'}, 'rationale': {'type': 'string'}, 'recommended': {'type': 'boolean'}, 'amount_cents': {'type': 'number'}}}}}}
update_plan_limits
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 (dry_run still works anywhere). Tier-keyed, so one call can set a new limit key across every tier in a single atomic write. Use -1 for unlimited, matching the catalog convention. This writes ONLY the limits object: it never touches Stripe, prices, or plan names, so it cannot mint a price by accident. Changing prices or adding a tier is a different job: use create_app_kit or the dashboard. Set dry_run to preview the before/after without writing. After this succeeds, run `bun run plans:sync` in the app repo and commit the regenerated plans.json so the code and the catalog agree.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'updates'], 'properties': {'mode': {'enum': ['merge', 'replace'], 'type': 'string', 'default': 'merge'}, 'app_id': {'type': 'string'}, 'dry_run': {'type': 'boolean', 'default': False}, 'updates': {'type': 'object', 'propertyNames': {'type': 'string'}, 'additionalProperties': {'type': 'object', 'propertyNames': {'type': 'string'}, 'additionalProperties': {'type': 'number'}}}}}
update_plan_meta
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 lacks the flag renders as a plain grey card. Use this to repair that. WRITE, human-gated: the human sees the before -> after diff and approves (clients without elicitation pass through, since this touches no money: it never reaches Stripe, never changes an amount, limits or billing model, and is reversible by calling it again). Setting a flag false REMOVES the key rather than storing false, keeping exported plans.json minimal. Convention is at most ONE is_elite and ONE recommended tier per app: this tool does not clear the flag from its siblings, so unset the old holder in a second call. Use list_plans first for tier slugs and current flags, and run `bun run plans:sync` in the app repo afterwards to regenerate plans.json.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'tier'], 'properties': {'name': {'type': 'string'}, 'tier': {'type': 'string'}, 'app_id': {'type': 'string'}, 'dry_run': {'type': 'boolean', 'default': False}, 'is_elite': {'type': 'boolean'}, 'recommended': {'type': 'boolean'}}}
update_plan_pricing
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. Clients without elicitation are refused (dry_run still works anywhere). Stripe prices are immutable, so this mints a NEW price and repoints the plan; the old price object is left intact and existing subscribers keep the price they signed up on, so this changes what NEW buyers pay. Switching a tier to one_time also clears its monthly/yearly price ids, so checkout cannot fall back to a recurring price the pricing page no longer advertises. Free, contact and payg tiers are refused: converting those is a catalog change, not a reprice. Use list_plans first for tier slugs and current amounts, and run `bun run plans:sync` in the app repo afterwards to regenerate plans.json.
Schéma d’entrée
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['app_id', 'updates'], 'properties': {'app_id': {'type': 'string'}, 'dry_run': {'type': 'boolean', 'default': False}, 'updates': {'type': 'array', 'items': {'type': 'object', 'required': ['tier'], 'properties': {'tier': {'type': 'string'}, 'amount_cents': {'type': 'number'}, 'payment_type': {'enum': ['one_time', 'subscription'], 'type': 'string'}, 'monthly_amount_cents': {'type': 'number'}}}}}}
Historique
Modifications récentes des outils
Ajouté
setup_pricing_page
29 September 2026 02:40
Ajouté
archive_plan
29 September 2026 02:40
Ajouté
update_plan_pricing
29 September 2026 02:40
Ajouté
update_plan_meta
29 September 2026 02:40
Ajouté
update_plan_limits
29 September 2026 02:40
Ajouté
list_plans
29 September 2026 02:40
Ajouté
create_app_kit
29 September 2026 02:40
Ajouté
plan_app_kit
29 September 2026 02:40
Ajouté
revoke_coupon_invite
29 September 2026 02:40
Ajouté
invite_to_coupon
29 September 2026 02:40
Ajouté
list_coupon_invites
29 September 2026 02:40
Ajouté
set_coupon_listed
29 September 2026 02:40
Ajouté
bulk_delete_coupon
29 September 2026 02:40
Ajouté
delete_coupon
29 September 2026 02:40
Ajouté
bulk_create_coupon
29 September 2026 02:40
Ajouté
create_coupon
29 September 2026 02:40
Ajouté
list_coupons
29 September 2026 02:40
Ajouté
list_recent_cancellations
29 September 2026 02:40
Ajouté
list_referrals
29 September 2026 02:40
Ajouté
revenue_by_app
29 September 2026 02:40
Ajouté
revenue_summary
29 September 2026 02:40
Ajouté
list_recent_payments
29 September 2026 02:40
Ajouté
get_customer
29 September 2026 02:40
Ajouté
list_subscriptions
29 September 2026 02:40
Ajouté
list_apps
29 September 2026 02:40
Découvrir
Serveurs MCP similaires
Lovie Company Formation
co.lovie/company-formation
Supports company formation and business administration with bank accounts, cards, invoicing, bookkeeping, accounting periods, and…
AgentLot Marketplace
io.agentlot/marketplace
Enables agents and users to discover, bid on, purchase, deliver, and settle paid digital services and compute work.
BeeL
es.beel/mcp
Provides Spanish company administration and VeriFactu-compliant invoicing, including customers, products, invoice issuance, corre…
corply
io.github.corply-dev/corply
Supports company formation and corporate administration including incorporation documents, signatures, cap tables, corporate acti…
shiply
now.shiply/shiply
Publishes and manages web applications with SQL databases, serverless functions, domains, email tests, client intake, contracts, …
ALM X++ MCP Server
io.github.alimbenhelal-pro/alm-xpp-mcp
Supports D365 Finance and Operations development with X++ and AOT search, code analysis, Azure DevOps workflows, telemetry querie…
Focxle: AI governance for B2B deals between agents
com.focxle/afos
Provides agent spending controls, delegated budgets, signed authority checks, negotiations, escrow contracts, workforce hiring, a…
Conta Azul MCP
io.github.douglac/contaazul-mcp
Connects to Conta Azul ERP for managing customers, sales, budgets, contracts, financial accounts, receivables, invoices, settleme…