Stripe for payments
For payments, Stripe is our top pick of four, and it earns first place as the broadest fit for teams already building on Stripe. Its official server lets an agent create customers, payment links, and invoices and read balances, so commerce and billing flows move from dashboard clicks and hand-coded API calls into natural language.
PayPal, Square, and Razorpay are the siblings: PayPal for broad consumer acceptance, Square for blended in-person and online commerce, Razorpay for its region. Stripe leads because its tools map cleanly onto the common payments tasks and most developer teams already run on it.
How Stripe fits
The tools that fit payments work are create_customer and list_customers for the people you charge, create_product and create_price (with list_products and list_prices) to define what they pay for, and create_payment_link to hand back a hosted checkout link for a price. The invoice set, create_invoice, create_invoice_item, and finalize_invoice, bills a customer and issues the invoice, while retrieve_balance and get_stripe_account_info report settlements and connected-account state.
The honest limit: alongside the create-and-read primitives the server ships create_refund for refunds, but no named tool for capturing an authorized charge, so capture-then-settle flows still reach into the Stripe API or dashboard. The siblings differ in fit rather than depth on Stripe: PayPal is the widely accepted option, Square suits a business spanning a register and a website, and Razorpay specializes regionally. Choose Stripe when the team builds on Stripe and an agent should drive customers, prices, invoices, and payment links directly; pick a sibling when consumer reach, point-of-sale, or region decides it.
Tools you would use
| Tool | What it does |
|---|---|
| get_stripe_account_info | Retrieves information about the connected Stripe account. |
| retrieve_balance | Retrieves the account's current and pending balance. |
| create_customer | Creates a customer record. |
| list_customers | Lists the customers on the account. |
| create_product | Creates a product. |
| list_products | Lists the products on the account. |
| create_price | Creates a price for a product. |
| list_prices | Lists the prices on the account. |
| create_payment_link | Creates a payment link for a price. |
| create_invoice | Creates an invoice for a customer. |
FAQ
- Can an agent capture or refund a charge through this server?
- It can refund: create_refund issues one. It does not include a named capture verb, so capturing an authorized charge reaches into the Stripe API or dashboard. The other tools are create-and-read primitives: customers, products, prices, invoices, payment links, and balance reads.
- Why is Stripe the broadest payments pick?
- Its server exposes the common building blocks an agent needs: create_customer, create_payment_link, the invoice tools, and retrieve_balance, mapping cleanly onto everyday payments work. PayPal, Square, and Razorpay fit narrower cases by audience, channel, or region.