Stripe Automation via Rube MCP
Automate Stripe payment operations through Composio's Stripe toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Stripe connection via
RUBE_MANAGE_CONNECTIONS with toolkit stripe
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit stripe
- If connection is not ACTIVE, follow the returned auth link to complete Stripe connection
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Customers
When to use: User wants to create, update, search, or list Stripe customers
Tool sequence:
STRIPE_SEARCH_CUSTOMERS - Search customers by email/name [Optional]
STRIPE_LIST_CUSTOMERS - List all customers [Optional]
STRIPE_CREATE_CUSTOMER - Create a new customer [Optional]
STRIPE_POST_CUSTOMERS_CUSTOMER - Update a customer [Optional]
Key parameters:
email: Customer email
name: Customer name
description: Customer description
metadata: Key-value metadata pairs
customer: Customer ID for updates (e.g., 'cus_xxx')
Pitfalls:
- Stripe allows duplicate customers with the same email; search first to avoid duplicates
- Customer IDs start with 'cus_'
2. Manage Charges and Payments
When to use: User wants to create charges, payment intents, or view charge history
Tool sequence:
STRIPE_LIST_CHARGES - List charges with filters [Optional]
STRIPE_CREATE_PAYMENT_INTENT - Create a payment intent [Optional]
STRIPE_CONFIRM_PAYMENT_INTENT - Confirm a payment intent [Optional]
STRIPE_POST_CHARGES - Create a direct charge [Optional]
STRIPE_CAPTURE_CHARGE - Capture an authorized charge [Optional]
Key parameters:
amount: Amount in smallest currency unit (e.g., cents for USD)
currency: Three-letter ISO currency code (e.g., 'usd')
customer: Customer ID
payment_method: Payment method ID
description: Charge description
Pitfalls:
- Amounts are in smallest currency unit (100 = $1.00 for USD)
- Currency codes must be lowercase (e.g., 'usd' not 'USD')
- Payment intents are the recommended flow over direct charges
3. Manage Subscriptions
When to use: User wants to create, list, update, or cancel subscriptions
Tool sequence:
STRIPE_LIST_SUBSCRIPTIONS - List subscriptions [Optional]
STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS - Create subscription [Optional]
STRIPE_RETRIEVE_SUBSCRIPTION - Get subscription details [Optional]
STRIPE_UPDATE_SUBSCRIPTION - Modify subscription [Optional]
Key parameters:
customer: Customer ID
items: Array of price items (price_id and quantity)
subscription: Subscription ID for retrieval/update (e.g., 'sub_xxx')
Pitfalls:
- Subscriptions require a valid customer with a payment method
- Price IDs (not product IDs) are used for subscription items
- Cancellation can be immediate or at period end
4. Manage Invoices
When to use: User wants to create, list, or search invoices
Tool sequence:
STRIPE_LIST_INVOICES - List invoices [Optional]
STRIPE_SEARCH_INVOICES - Search invoices [Optional]
STRIPE_CREATE_INVOICE - Create an invoice [Optional]
Key parameters:
customer: Customer ID for invoice
collection_method: 'charge_automatically' or 'send_invoice'
days_until_due: Days until invoice is due
Pitfalls:
- Invoices auto-finalize by default; use
auto_advance: false for draft invoices
5. Manage Products and Prices
When to use: User wants to list or search products and their pricing
Tool sequence:
STRIPE_LIST_PRODUCTS - List products [Optional]
STRIPE_SEARCH_PRODUCTS - Search products [Optional]
STRIPE_LIST_PRICES - List prices [Optional]
STRIPE_GET_PRICES_SEARCH - Search prices [Optional]
Key parameters:
active: Filter by active/inactive status
query: Search query for search endpoints
Pitfalls:
- Products and prices are separate objects; a product can have multiple prices
- Price IDs (e.g., 'price_xxx') are used for subscriptions and checkout
6. Handle Refunds
When to use: User wants to issue refunds on charges
Tool sequence:
STRIPE_LIST_REFUNDS - List refunds [Optional]
STRIPE_POST_CHARGES_CHARGE_REFUNDS - Create a refund [Optional]
STRIPE_CREATE_REFUND - Create refund via payment intent [Optional]
Key parameters:
charge: Charge ID for refund
amount: Partial refund amount (omit for full refund)
reason: Refund reason ('duplicate', 'fraudulent', 'requested_by_customer')
Pitfalls:
- Refunds can take 5-10 business days to appear on customer statements
- Amount is in smallest currency unit
Common Patterns
Amount Formatting
Stripe uses smallest currency unit:
- USD: $10.50 = 1050 cents
- EUR: 10.50 = 1050 cents
- JPY: 1000 = 1000 (no decimals)
Pagination
- Use
limit parameter (max 100)
- Check
has_more in response
- Pass
starting_after with last object ID for next page
- Continue until
has_more is false
Known Pitfalls
Amount Units:
- Always use smallest currency unit (cents for USD/EUR)
- Zero-decimal currencies (JPY, KRW) use the amount directly
ID Prefixes:
- Customers:
cus_, Charges: ch_, Subscriptions: sub_
- Invoices:
in_, Products: prod_, Prices: price_
- Payment Intents:
pi_, Refunds: re_
Quick Reference
| Task |
Tool Slug |
Key Params |
| Create customer |
STRIPE_CREATE_CUSTOMER |
email, name |
| Search customers |
STRIPE_SEARCH_CUSTOMERS |
query |
| Update customer |
STRIPE_POST_CUSTOMERS_CUSTOMER |
customer, fields |
| List charges |
STRIPE_LIST_CHARGES |
customer, limit |
| Create payment intent |
STRIPE_CREATE_PAYMENT_INTENT |
amount, currency |
| Confirm payment |
STRIPE_CONFIRM_PAYMENT_INTENT |
payment_intent |
| List subscriptions |
STRIPE_LIST_SUBSCRIPTIONS |
customer |
| Create subscription |
STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS |
customer, items |
| Update subscription |
STRIPE_UPDATE_SUBSCRIPTION |
subscription, fields |
| List invoices |
STRIPE_LIST_INVOICES |
customer |
| Create invoice |
STRIPE_CREATE_INVOICE |
customer |
| Search invoices |
STRIPE_SEARCH_INVOICES |
query |
| List products |
STRIPE_LIST_PRODUCTS |
active |
| Search products |
STRIPE_SEARCH_PRODUCTS |
query |
| List prices |
STRIPE_LIST_PRICES |
product |
| Search prices |
STRIPE_GET_PRICES_SEARCH |
query |
| List refunds |
STRIPE_LIST_REFUNDS |
charge |
| Create refund |
STRIPE_CREATE_REFUND |
charge, amount |
| Payment methods |
STRIPE_LIST_CUSTOMER_PAYMENT_METHODS |
customer |
| Checkout session |
STRIPE_CREATE_CHECKOUT_SESSION |
line_items |
| List payment intents |
STRIPE_LIST_PAYMENT_INTENTS |
customer |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Example
User request:
Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---
2name: stripe-automation
3description: 'Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.'
4metadata:
5 source: https://skillmd.com/skills/sickn33/stripe-automation
6 aas-risk: critical
7 aas-source: community
8 aas-date-added: '2026-02-27'
9---
10
11# Stripe Automation via Rube MCP
12
13Automate Stripe payment operations through Composio's Stripe toolkit via Rube MCP.
14
15## Prerequisites
16
17- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
18- Active Stripe connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `stripe`
19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
20
21## Setup
22
23**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
24
251. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
262. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `stripe`
273. If connection is not ACTIVE, follow the returned auth link to complete Stripe connection
284. Confirm connection status shows ACTIVE before running any workflows
29
30## Core Workflows
31
32### 1. Manage Customers
33
34**When to use**: User wants to create, update, search, or list Stripe customers
35
36**Tool sequence**:
371. `STRIPE_SEARCH_CUSTOMERS` - Search customers by email/name [Optional]
382. `STRIPE_LIST_CUSTOMERS` - List all customers [Optional]
393. `STRIPE_CREATE_CUSTOMER` - Create a new customer [Optional]
404. `STRIPE_POST_CUSTOMERS_CUSTOMER` - Update a customer [Optional]
41
42**Key parameters**:
43- `email`: Customer email
44- `name`: Customer name
45- `description`: Customer description
46- `metadata`: Key-value metadata pairs
47- `customer`: Customer ID for updates (e.g., 'cus_xxx')
48
49**Pitfalls**:
50- Stripe allows duplicate customers with the same email; search first to avoid duplicates
51- Customer IDs start with 'cus_'
52
53### 2. Manage Charges and Payments
54
55**When to use**: User wants to create charges, payment intents, or view charge history
56
57**Tool sequence**:
581. `STRIPE_LIST_CHARGES` - List charges with filters [Optional]
592. `STRIPE_CREATE_PAYMENT_INTENT` - Create a payment intent [Optional]
603. `STRIPE_CONFIRM_PAYMENT_INTENT` - Confirm a payment intent [Optional]
614. `STRIPE_POST_CHARGES` - Create a direct charge [Optional]
625. `STRIPE_CAPTURE_CHARGE` - Capture an authorized charge [Optional]
63
64**Key parameters**:
65- `amount`: Amount in smallest currency unit (e.g., cents for USD)
66- `currency`: Three-letter ISO currency code (e.g., 'usd')
67- `customer`: Customer ID
68- `payment_method`: Payment method ID
69- `description`: Charge description
70
71**Pitfalls**:
72- Amounts are in smallest currency unit (100 = $1.00 for USD)
73- Currency codes must be lowercase (e.g., 'usd' not 'USD')
74- Payment intents are the recommended flow over direct charges
75
76### 3. Manage Subscriptions
77
78**When to use**: User wants to create, list, update, or cancel subscriptions
79
80**Tool sequence**:
811. `STRIPE_LIST_SUBSCRIPTIONS` - List subscriptions [Optional]
822. `STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS` - Create subscription [Optional]
833. `STRIPE_RETRIEVE_SUBSCRIPTION` - Get subscription details [Optional]
844. `STRIPE_UPDATE_SUBSCRIPTION` - Modify subscription [Optional]
85
86**Key parameters**:
87- `customer`: Customer ID
88- `items`: Array of price items (price_id and quantity)
89- `subscription`: Subscription ID for retrieval/update (e.g., 'sub_xxx')
90
91**Pitfalls**:
92- Subscriptions require a valid customer with a payment method
93- Price IDs (not product IDs) are used for subscription items
94- Cancellation can be immediate or at period end
95
96### 4. Manage Invoices
97
98**When to use**: User wants to create, list, or search invoices
99
100**Tool sequence**:
1011. `STRIPE_LIST_INVOICES` - List invoices [Optional]
1022. `STRIPE_SEARCH_INVOICES` - Search invoices [Optional]
1033. `STRIPE_CREATE_INVOICE` - Create an invoice [Optional]
104
105**Key parameters**:
106- `customer`: Customer ID for invoice
107- `collection_method`: 'charge_automatically' or 'send_invoice'
108- `days_until_due`: Days until invoice is due
109
110**Pitfalls**:
111- Invoices auto-finalize by default; use `auto_advance: false` for draft invoices
112
113### 5. Manage Products and Prices
114
115**When to use**: User wants to list or search products and their pricing
116
117**Tool sequence**:
1181. `STRIPE_LIST_PRODUCTS` - List products [Optional]
1192. `STRIPE_SEARCH_PRODUCTS` - Search products [Optional]
1203. `STRIPE_LIST_PRICES` - List prices [Optional]
1214. `STRIPE_GET_PRICES_SEARCH` - Search prices [Optional]
122
123**Key parameters**:
124- `active`: Filter by active/inactive status
125- `query`: Search query for search endpoints
126
127**Pitfalls**:
128- Products and prices are separate objects; a product can have multiple prices
129- Price IDs (e.g., 'price_xxx') are used for subscriptions and checkout
130
131### 6. Handle Refunds
132
133**When to use**: User wants to issue refunds on charges
134
135**Tool sequence**:
1361. `STRIPE_LIST_REFUNDS` - List refunds [Optional]
1372. `STRIPE_POST_CHARGES_CHARGE_REFUNDS` - Create a refund [Optional]
1383. `STRIPE_CREATE_REFUND` - Create refund via payment intent [Optional]
139
140**Key parameters**:
141- `charge`: Charge ID for refund
142- `amount`: Partial refund amount (omit for full refund)
143- `reason`: Refund reason ('duplicate', 'fraudulent', 'requested_by_customer')
144
145**Pitfalls**:
146- Refunds can take 5-10 business days to appear on customer statements
147- Amount is in smallest currency unit
148
149## Common Patterns
150
151### Amount Formatting
152
153Stripe uses smallest currency unit:
154- USD: $10.50 = 1050 cents
155- EUR: 10.50 = 1050 cents
156- JPY: 1000 = 1000 (no decimals)
157
158### Pagination
159
160- Use `limit` parameter (max 100)
161- Check `has_more` in response
162- Pass `starting_after` with last object ID for next page
163- Continue until `has_more` is false
164
165## Known Pitfalls
166
167**Amount Units**:
168- Always use smallest currency unit (cents for USD/EUR)
169- Zero-decimal currencies (JPY, KRW) use the amount directly
170
171**ID Prefixes**:
172- Customers: `cus_`, Charges: `ch_`, Subscriptions: `sub_`
173- Invoices: `in_`, Products: `prod_`, Prices: `price_`
174- Payment Intents: `pi_`, Refunds: `re_`
175
176## Quick Reference
177
178| Task | Tool Slug | Key Params |
179|------|-----------|------------|
180| Create customer | STRIPE_CREATE_CUSTOMER | email, name |
181| Search customers | STRIPE_SEARCH_CUSTOMERS | query |
182| Update customer | STRIPE_POST_CUSTOMERS_CUSTOMER | customer, fields |
183| List charges | STRIPE_LIST_CHARGES | customer, limit |
184| Create payment intent | STRIPE_CREATE_PAYMENT_INTENT | amount, currency |
185| Confirm payment | STRIPE_CONFIRM_PAYMENT_INTENT | payment_intent |
186| List subscriptions | STRIPE_LIST_SUBSCRIPTIONS | customer |
187| Create subscription | STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS | customer, items |
188| Update subscription | STRIPE_UPDATE_SUBSCRIPTION | subscription, fields |
189| List invoices | STRIPE_LIST_INVOICES | customer |
190| Create invoice | STRIPE_CREATE_INVOICE | customer |
191| Search invoices | STRIPE_SEARCH_INVOICES | query |
192| List products | STRIPE_LIST_PRODUCTS | active |
193| Search products | STRIPE_SEARCH_PRODUCTS | query |
194| List prices | STRIPE_LIST_PRICES | product |
195| Search prices | STRIPE_GET_PRICES_SEARCH | query |
196| List refunds | STRIPE_LIST_REFUNDS | charge |
197| Create refund | STRIPE_CREATE_REFUND | charge, amount |
198| Payment methods | STRIPE_LIST_CUSTOMER_PAYMENT_METHODS | customer |
199| Checkout session | STRIPE_CREATE_CHECKOUT_SESSION | line_items |
200| List payment intents | STRIPE_LIST_PAYMENT_INTENTS | customer |
201
202## When to Use
203This skill is applicable to execute the workflow or actions described in the overview.
204
205## Example
206
207**User request:**
208
209> Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds.
210
211## Limitations
212- Use this skill only when the task clearly matches the scope described above.
213- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
214- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.