Does it cancel immediately or at period end?

Usually your choice. Most of these platforms let you cancel at the end of the current billing period, where the customer keeps access they paid for, or immediately. Stripe exposes both; check the others' options. Be explicit about which, since it changes when the charges stop.

How do I keep an agent from cancelling the wrong subscription?

Act on a specific subscription id, confirm it maps to the right customer before the call, and keep a record of what was already cancelled. An agent with no memory of its prior cancellations can retry against a stale or wrong id, which is how a paying customer gets cut off.

MCP servers that can cancel a subscription

3 verified servers expose a tool that can cancel a subscription

Cancelling a subscription stops the recurring charge, which makes it a write with real money and real customer trust attached. When an agent handles a downgrade, a churn request, or a billing fix, a cancel tool ends the subscription on the platform that bills it.

These verified servers let an agent cancel a subscription on the major billing platforms.

Top pick

Stripe

Official

Stripe's official MCP server lets agents create customers, payment links, invoices, and read balances.

payments1,583

Tool:

cancel_subscription

Stripe's cancel_subscription ends a subscription on the widest billing API here, with the timing options, now or at period end, most teams already rely on.

Pick 2

Paddle

Official

Paddle's official MCP server lets agents manage the product catalog, billing, subscriptions, and reports through the Paddle Billing API.

payments50

Tool:

cancel_subscription

Paddle acts as a merchant of record, so cancel_subscription stops a SaaS subscription it manages and bills on your behalf.

Pick 3

PayPal

Official

PayPal's official remote MCP server brings invoicing, orders, and payments into agentic commerce.

payments10

Tool:

cancel_subscription

For recurring payments billed through PayPal, cancel_subscription ends an active subscription cleanly.

What to know

Cancellation is consequential in both directions: leave a subscription active and you keep charging someone who asked to stop; cancel the wrong one and you cut off a paying customer. So it wants the same care as a charge: act on a specific subscription id, confirm the target, and be clear about timing, since most platforms can cancel at period end or immediately. The three processors expose the same action against their own subscription objects, the billing equivalent of closing an account.

The state that matters across runs is what was already cancelled. An agent that cancels a subscription, forgets, and tries again either errors or, worse, acts on the wrong id the second time. Knowing which subscriptions it has already ended keeps a retry from turning into a mistake.

Questions

Does it cancel immediately or at period end?: Usually your choice. Most of these platforms let you cancel at the end of the current billing period, where the customer keeps access they paid for, or immediately. Stripe exposes both; check the others' options. Be explicit about which, since it changes when the charges stop.
How do I keep an agent from cancelling the wrong subscription?: Act on a specific subscription id, confirm it maps to the right customer before the call, and keep a record of what was already cancelled. An agent with no memory of its prior cancellations can retry against a stale or wrong id, which is how a paying customer gets cut off.