MCP servers that can list subscriptions
3 verified servers expose a tool that can list subscriptions
Recurring revenue lives in subscriptions, and an agent that reports on it, finds a churn risk, or acts on one first has to see the list. Listing subscriptions returns what is active, past due, or cancelled, so the agent works from the real billing state.
These verified servers let an agent list the subscriptions on a billing platform.
Stripe
Stripe
Stripe's official MCP server lets agents create customers, payment links, invoices, and read balances.
list_subscriptions
Stripe's list_subscriptions returns the account's subscriptions on the widest billing API here, usually filtered by status so an agent can pull just the active or past-due ones.
Paddle
Paddle
Paddle's official MCP server lets agents manage the product catalog, billing, subscriptions, and reports through the Paddle Billing API.
list_subscriptions
On Paddle, list_subscriptions returns the SaaS subscriptions it manages, the read behind reporting or acting on recurring billing through Paddle.
Polar
Polar
Polar's official remote server lets agents manage products, subscriptions, orders, customers, and revenue metrics on the merchant-of-record platform.
polar_subscriptions_list
polar_subscriptions_list lists subscriptions in a Polar organization, for businesses billing through its merchant-of-record platform.
What to know
A subscription list is the entry point for most billing automation: who is active, whose payment failed, which renew this month. The processors here return the account's subscriptions, usually with a status an agent can filter on, so it can pull just the past-due ones or those cancelling at period end. From the list it gets the subscription id the act-on tools want, the same way listing products feeds the create tools. Reading first also grounds a billing decision in what is actually charged rather than what the agent assumes.
Subscription state changes on its own, as renewals succeed and cards fail, so the list is worth re-reading rather than caching. What an agent benefits from holding is its own working set: which accounts it is watching for churn, so a follow-up starts from that shortlist instead of scanning every subscription again.
Questions
- Can an agent filter by status?
- On most of these, yes. The list tools typically take a status filter, so an agent can ask for just the active subscriptions, the past-due ones, or those set to cancel at period end, rather than pulling everything. Check each processor's filters for the exact set.
- How does this pair with cancelling?
- Listing finds the subscription and its id; cancelling acts on it. An agent lists to find the right subscription, by customer or status, then passes that id to the cancel tool. Reading first is how it avoids cancelling the wrong one.