Stripe AI
Use Stripe’s AI tooling to connect agents to Stripe payment operations and integration guidance.
A checkout problem can span a commerce catalog, a payment provider, recurring billing, and application code. Start with the system that owns the record you need, then use the matching guide or skill to investigate the next part of the workflow.
12 guides · 8 MCP / 4 Skills
This collection separates payment and billing tools from commerce development and integration guidance. It includes existing provider guides and the new Paddle, SumUp, commercetools, Dodo Payments, and Airwallex additions. No pricing or tax assumptions are needed to choose a setup guide.
| Your task | Start here | How to choose |
|---|---|---|
| Inspect payments or subscriptions | Payment and billing APIs | Choose the provider holding the transaction or subscription record; check the guide’s environment and permissions. |
| Debug carts, products, or orders | Commerce and checkout development | Start with commerce records before assuming the payment provider caused the checkout issue. |
| Implement an integration | Integration and subscription skills | Use vendor guidance for application code and lifecycle handling, then configure account tools separately. |
| Explore without changing an account | The provider guide’s tool-selection notes | Read-only, non-destructive, and sandbox are different controls. The Paddle guide explains why non-destructive can still include creation operations. |
No matching guides. Try another search or reset the filters.
Find the provider connected to the payment, customer, or subscription you need to inspect.
Use Stripe’s AI tooling to connect agents to Stripe payment operations and integration guidance.
Integrate PayPal account and payment workflows with AI agent tools and MCP.
Connect to Square’s hosted OAuth MCP server for Square API workflows; the official repository also documents a local sandbox configuration.
Use Adyen’s alpha MCP server to inspect payment methods and sessions, create payment links, and work with merchant webhook configuration.
Inspect Razorpay payments, orders and settlements, and manage payment links through Razorpay’s official remote MCP service.
Work with Paddle Billing products, prices, customers, subscriptions, transactions, and reports through its official MCP server.
Connect AI payment workflows to SumUp using its MCP server and supporting AI toolkit.
Work from product and order context into checkout implementation guidance.
Connect an MCP client to commercetools products, carts, orders, customers, and payment information.
Use Shopify’s skills to guide agents working on Shopify development tasks.
Combine Dodo Payments integration skills with its API and documentation MCP connectors.
Prepare account integration and subscription workflows with vendor-authored instructions.
Use Airwallex’s workflow and integration skills for billing, checkout, issuing, treasury, and connected-account onboarding.
Plan in-app purchase integrations and RevenueCat project workflows with official cross-platform skills and optional authenticated MCP access.
No. Sandbox identifies an environment; its tools may still create or modify test records. Check the provider’s tool controls separately. Non-destructive also does not necessarily mean read-only, as the Paddle guide explains.
This collection helps you choose an integration guide. It does not compare fees, tax rules, or contractual terms. Consult the provider’s current official commercial documentation for those decisions.
Begin with the system owning the failing record. Inspect commerce carts and orders, then provider payment or subscription context, and finally the application’s logs and webhook handling.
Explore the fourth batch: 29 official cloud, payment, security, and monitoring additions →
See all 25 additions in the third batch → · Full directory →