Recurly MCP by usefulapi

Each tool has a clearly distinct purpose: reads (get_* vs list_*) target specific or collection resources, while cancel and pause are clearly different subscription state mutations. List tools that optionally accept account_id are still distinguishable by resource (invoices vs subscriptions). No meaningful overlap exists.

All tools use a consistent recurly_ prefix and snake_case verb_noun structure (get_account, list_subscriptions, pause_subscription). The only minor deviation is recurly_cancel_customer_subscription, which inserts 'customer' into the noun phrase unlike the other resource-oriented names.

8 tools is in the healthy 3-15 range and each tool covers a distinct operation. However, the set is slightly thin for a billing platform surface, offering mostly reads plus two subscription mutations.

Major gaps exist: no create/update/delete for accounts, subscriptions, or invoices; no invoice retrieval by id; no way to create a subscription or account despite being a subscription billing service. The surface covers listing and basic lifecycle changes but leaves core workflows impossible.