# Your Stripe account. Answers without the dashboard. Source: https://corespeed.io/integrations/stripe 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. ## Set up an agent Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)` It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Stripe after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up ## 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. You ask your agent: "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." It calls CoreSpeed: - `stripe__stripe_api_search`: ok, 388 ms - `stripe__stripe_api_read`: ok, 642 ms It reads from: Stripe. ### Payment follow-up: Three payments to chase. Two cards were declined and one has expired. Each customer gets a short note. **Failed** - Halcyon Labs · $480 · card declined - Brightline Studio · $560 · expired card - Northgate Supply · $200 · card declined **Draft note** - Your last payment did not go through. Could you update the card on file this week? _Illustrative account · No refund, retry or email sent_ All connectors: https://corespeed.io/docs/connectors ## From payment records to the next step Requests you can make once Stripe is connected. The data is fictional. ### Find the payments that failed Failed payments · this week · From your Stripe account - Failed: 3 payments, $1,240 in total - Most common reason: Card declined - Read only · Nothing retried ### Hold a refund for a person Refund for invoice 1042 · Example policy on - Amount: $480.00 - Policy: Ask before any refund over $100 - Waits for a person Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md) ### Check the docs before you build A failed-payment webhook · Stripe's documentation - Event: invoice.payment_failed - Test with: A restricted test key - From Stripe's own docs ## 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 guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor ## Questions ### Which Stripe key does my agent need? A restricted key you create for agent access in the Stripe Dashboard. Stripe's MCP no longer accepts secret keys, and access follows the key's permissions. ### Can my agent refund a payment? Only if the key allows writes. A refund is a stripe_api_write call, and Stripe's approval rules and your CoreSpeed approvals can hold it for a person. How approvals work: https://corespeed.io/docs/approvals ### Is this Stripe's own MCP server? Yes. CoreSpeed forwards your calls to Stripe's hosted MCP server and keeps only the tools it has reviewed. ### Do I have to switch agents? No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once. ### Can my agent access every account in our organization? No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private. ### Does this work without connecting an account? No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors Every tool and price: https://corespeed.io/catalog/stripe ## Related pages - [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents. - [Clink for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/clink): Shop and pay from a Clink agent wallet. Your agent prepares the checkout; paying is a separate call a person can approve. - [Gumroad for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/gumroad): Read Gumroad sales and subscribers and manage offer codes from your agent. A refund can wait for a person to approve it. - [Square for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/square): Ask your agent about Square orders, payments and customers, and draft invoices you review before they go out. ## Sources - Connectors: https://corespeed.io/docs/connectors - Stripe MCP: https://docs.stripe.com/mcp - Stripe API keys: https://docs.stripe.com/keys - Stripe approvals: https://docs.stripe.com/account/approvals Reviewed 2026-11-10. ## Links - Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md) - All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md) - Documentation: https://corespeed.io/docs - Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)