IntegrationsStripe integration
Your Stripe account.Answers without the dashboard.
Connect Stripe to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent reads customers, payments, invoices, subscriptions and balances, and searches Stripe's documentation, with a restricted key you create for agent access. A refund or any other write is a separate call that Stripe's approval rules and your CoreSpeed approvals can hold.
From payment recordsto the next step.
Requests you can make once Stripe is connected. The data is fictional.
- StripePayments · failed
- $480Halcyon Labs · card declinedFailed
- $560Brightline Studio · expired cardFailed
- $200Northgate Supply · card declinedFailed
Find the payments that failed
Read only · Nothing retried
Approval requestWaiting
Claude Code for Diane
stripe__stripe_api_write
“Refund $480.00 to Halcyon Labs for invoice 1042.”
Policy: Ask before any refund over $100.
ApproveDeny
Hold a refund for a person
Waits for a person
- CodexAnswer
Stripe docs
Which event to listen for.
- Listen for invoice.payment_failed on your webhook endpoint.
- Try it with an rk_test_ key before going live.
Check the docs before you build
From Stripe's own docs
See what failed.Decide who to contact.
Ask your agent for the payments that failed this week, with the customer and the amount, and a short note for each.
Reads fromStripe
All connectors →List this week's failed payments in Stripe with the customer and the amount. Draft a short follow-up note for each. Do not refund or retry anything.
stripe__stripe_api_searchok
List payments, filtered by status
Keep your agent.Bring your work.
One CoreSpeed account, across compatible agents.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Connect Stripe
Authorize the account and the content you need.
- 3
Start with one task
Ask for a summary, a brief, or a draft. Review the answer.
Setup guidesClaude CodeCodexCursor