MCP servers that can list products
4 verified servers expose a tool that can list products in a catalog
Billing logic usually starts from the catalog: which products exist, at what prices, before an agent builds an invoice or a payment link around one. A list-products tool returns that catalog so the agent works from real ids rather than guessed names.
These verified servers let an agent list the products on a payment platform.
Stripe
Stripe
Stripe's official MCP server lets agents create customers, payment links, invoices, and read balances.
list_products
list_products returns the products on a Stripe account, the lookup behind building a payment link or invoice for the right item.
Polar
Polar
Polar's official remote server lets agents manage products, subscriptions, orders, customers, and revenue metrics on the merchant-of-record platform.
polar_products_list
polar_products_list lists the products in a Polar organization, for businesses billing through its merchant-of-record platform.
Paddle
Paddle
Paddle's official MCP server lets agents manage the product catalog, billing, subscriptions, and reports through the Paddle Billing API.
list_products
list_products returns the catalog in Paddle, so a SaaS billing agent can find the product before it charges against it.
PayPal
PayPal
PayPal's official remote MCP server brings invoicing, orders, and payments into agentic commerce.
list_product
list_product returns products from the PayPal catalog, the fit when you sell and collect through PayPal.
What to know
A product list is the lookup behind most billing actions. To create a payment link or an invoice for the right thing, an agent needs the product (and usually a price) id, and listing is how it resolves a human name like Pro Plan to the id the create tools want. The four processors here all expose it, returning the catalog as the account has it configured. Reading the catalog first is also how an agent avoids billing for a product that does not exist or was retired.
A catalog changes rarely, so an agent that resolves a product name to its id once can hold that mapping rather than re-listing every time it bills. The ids it learned are the useful thing to keep; the rest of the catalog is a fetch away when it needs it.
Questions
- Why list products before billing?
- Because the create tools want a product or price id, not a display name. Listing resolves a name like Pro Plan to its id, so an agent bills for the right thing. It also lets the agent confirm a product still exists before charging against it.
- Does the list include prices?
- Usually you get products, with prices either included or a related call away, depending on the processor. On Stripe, products and prices are separate objects, so an agent often lists both. Check the server's tools if you need the price id specifically.