What an agent can do in Stripe
Manage payments and billing: create payment links and invoices, look up customers, charges, subscriptions and balances, and search Stripe docs.
Jobs on Rush that use Stripe
- Find Why Customers Churned in Stripe
- Report Failed Payments in Stripe
- Build a Monthly Revenue Report From Stripe
- Reconcile Stripe Payouts Against Charges
- Review Every Refund Request With Stripe From Your Backend
- Report Trial Conversions From Stripe
- Send a Weekly Stripe Revenue Digest to Slack
Code changes on a Stripe codebase
These change the code of an app built on Stripe. They run on your repository in a Project and need no Stripe connection.
- Add Automatic Tax to a Stripe Checkout Subscription
- Handle Stripe Subscription Cancellations in a Next.js App
- Make a Stripe Webhook Handler Idempotent
- Write Tests for a Stripe Webhook Handler
How Stripe connects
Stripe is a remote MCP server, published by Stripe, at https://mcp.stripe.com/. Connecting it signs in through the MCP OAuth flow on Stripe's side.
From Stripe: Stripe's MCP documentation · source code.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names stripe in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Stripe",
"url": "https://mcp.stripe.com/"
}Whose Stripe account the agent uses
Your Stripe connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Stripe, and a run started with an API key uses the Stripe of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Stripe, and that agent's runs use their account and nothing else: never yours, never another user's.
More Finance integrations
Frequently asked questions
How do I connect Stripe to Rush?
Open Settings → Connections in the console and connect Stripe, or send POST /me/connections with {"type":"mcp","name":"Stripe","url":"https://mcp.stripe.com/"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Stripe account?
No. A run gets your Stripe connection only when it names it in connections ("connections": ["stripe"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Stripe?
Manage payments and billing: create payment links and invoices, look up customers, charges, subscriptions and balances, and search Stripe docs. 7 published jobs use it; this page lists them.
Can my app's users connect their own Stripe?
Yes. Make each user an agent from your template, and they sign in to their own Stripe through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for finance teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to