Moonclerk

@moonclerk show me all active subscriptions and their next billing dates

Based on your MoonClerk account, you have 47 active subscriptions. Here's a summary: 23 are on monthly billing cycles with next charges between Dec 15-31, 2024. 18 are quarterly subscriptions, next billing in Jan-Feb 2025. 6 are annual plans renewing in Q1 2025. The most common plan is 'Pro Monthly' with 15 subscribers. This illustrative example shows how the MCP retrieves subscription data including billing schedules and plan distribution.

This example demonstrates read-only subscription retrieval. Requires API key with read access to subscription data. The MCP returns raw subscription objects—the AI synthesizes them into a billing timeline. Useful for revenue forecasting and churn monitoring, but won't show payment method details or customer contact info without additional list_customers calls.

@moonclerk find all payments from the 'Annual Conference' form in the last 30 days and calculate the total

Found 12 payments through the 'Annual Conference' payment form in the past 30 days. Total collected: $8,400. Breakdown: 9 successful payments ($700 each), 2 partial payments ($350 each), 1 refunded payment ($700). Average processing time was 2.3 days from submission to settlement. This illustrative example shows how filtering by form and date range helps track campaign-specific revenue.

Combines list_payments filtering with AI calculation. Requires knowing the exact form name or ID—consider listing forms first if unsure. The MCP provides payment status and amounts; the AI handles aggregation. Be aware that 'last 30 days' depends on payment creation date, not settlement date, which may affect accounting reconciliation.

@moonclerk compare customers who have active discounts versus those without, and tell me which group has higher retention

Analyzing your customer base: 34 customers have active discounts (list_discounts), while 89 customers pay full price (list_customers). Among discounted customers, 91% have subscriptions older than 6 months versus 67% retention in the full-price group. The most common discount is '20OFF' applied to 18 customers. This illustrative cross-reference suggests discounts correlate with longer subscription duration, though causation isn't established—early adopters may have received promotional pricing.

This synthesis example showcases using multiple MCP tools together (list_discounts + list_customers + list_subscriptions) to derive business insights the vendor dashboard might not surface. The AI infers retention patterns from subscription age data. Requires API access to all three endpoints. Results depend on how your team tags and applies discounts—inconsistent naming makes analysis harder.

When Moonclerk MCP speeds up subscription accounting

A 6-person SaaS company runs monthly close and needs to reconcile Moonclerk subscription revenue against their books. The finance lead pulls List Payments filtered by date range and List Subscriptions to cross-check active plans against invoiced amounts. This MCP is the right call if you're doing this reconciliation more than twice a month and your payment volume is under 500 transactions per period—the tool set is lean but covers the core read operations. If you need refund workflows or dispute handling, you'll still be opening the Moonclerk dashboard. The buying threshold: you're spending 90+ minutes a month manually exporting CSVs and pivoting them in spreadsheets.

Why support teams use this for billing questions

A 3-person support team fields 20-30 billing questions a week from customers asking about applied discounts or payment history. The List Discounts and List Customers tools let the team answer "why was I charged this amount" without leaving their chat workspace or pinging the founder who owns the Moonclerk login. This MCP wins if your support volume justifies API-key auth setup and your team already uses a shared AI workspace for ticket triage. The trade-off: you can read payment data but can't issue refunds or update subscriptions through the MCP, so complex billing issues still escalate. If more than 40% of your billing questions require write actions, the MCP saves less time than you'd expect.

When this MCP fits subscription health reviews

A 5-person product team reviews churn quarterly and wants to segment canceled subscriptions by payment form and discount usage to understand which acquisition channels retain best. The List Subscriptions and List Payment Forms tools surface the raw data without waiting on a finance export. This MCP is borderline if you're only running this analysis once a quarter—setup overhead might outweigh the 30-minute CSV export alternative. It's the right call if you're iterating on pricing experiments and need to pull subscription cohorts weekly or more. The threshold: you're making product decisions based on subscription behavior at least twice a month, and you want that data in the same workspace where you're drafting roadmap docs.