Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## Stripe is supported and offers OAuth2 and API-key auth modes |
| 2 | |
| 3 | Composio supports the Stripe toolkit with OAuth2 and API-key auth modes; the marketplace entry is available on the Stripe toolkit page. |
| 4 | |
| 5 | ## For Stripe API-key auth, use the Stripe secret key from Developers -> API Keys -> Standard keys |
| 6 | |
| 7 | For Stripe API-key auth, use the Stripe secret key from Stripe Dashboard -> Developers -> API Keys -> Standard keys -> Secret key. In API/SDK connection payloads, the auth config field may need to be passed as `api_key`. |
| 8 | |
| 9 | ## One Stripe MCP/API-key connection maps to one Stripe account unless the customer uses Stripe Connect |
| 10 | |
| 11 | Stripe usually uses different API keys for separate accounts, so one connected account/MCP server has access to one Stripe account. If the customer uses Stripe Connect, the platform can consolidate connected accounts under one platform API key and may better fit multi-account workflows. |
| 12 | |
| 13 | ## MRR can be calculated from `STRIPE_LIST_SUBSCRIPTIONS` |
| 14 | |
| 15 | Use `STRIPE_LIST_SUBSCRIPTIONS` to retrieve subscription data, then calculate MRR from the returned subscriptions in the agent/application layer. |
| 16 | |
| 17 | ## Stripe payment-success triggers are available |
| 18 | |
| 19 | Use `STRIPE_CHECKOUT_SESSION_COMPLETED` for completed Checkout sessions. Fetch the current trigger catalog for invoice payment events before implementation rather than assuming every Stripe event has a corresponding trigger. |