Stripe MCP Server
Provides tools for Stripe payment integration, enabling creation and management of payment links, payment intents, products, prices, and customers.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Stripe MCP Server Create a payment link for a $20 tutoring session."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Stripe MCP Server
A Model Context Protocol (MCP) server that provides Stripe payment integration capabilities to Claude Desktop. This server enables you to create payment links, process payments, manage products and customers directly from Claude.
Features
Payment Links
Create payment links with products and prices
List and manage existing payment links
Update payment link settings
Support for billing address collection and promotion codes
Payment Processing
Create and confirm payment intents
Monitor payment status
Handle customer payment methods
Product & Price Management
Create and manage products
Set up pricing (one-time or recurring)
Product catalog management
Customer Management
Create and manage customer records
View customer payment history
Customer data management
Related MCP server: Stripe MCP
Setup
1. Install Dependencies
cd stripe_mcp
npm install2. Build the Server
npm run build3. Set Up Environment Variables
Create a .env file in the stripe_mcp directory:
STRIPE_SECRET_KEY=sk_test_your_stripe_secret_key_hereYou can get your Stripe secret key from your Stripe Dashboard.
4. Configure Claude Desktop
Add the following to your Claude Desktop MCP configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"stripe": {
"command": "node",
"args": [
"/path/to/your/stripe_mcp/dist/index.js"
],
"env": {
"STRIPE_SECRET_KEY": "sk_test_your_stripe_secret_key_here"
}
}
}
}Replace /path/to/your/stripe_mcp/ with the actual path to your stripe_mcp directory.
Usage Examples
Create a Payment Link
// Create a simple payment link for a $20 service
create_payment_link({
line_items: [{
price_data: {
currency: "usd",
unit_amount: 2000, // $20.00 in cents
product_data: {
name: "Tutoring Session",
description: "1-hour math tutoring session"
}
},
quantity: 1
}],
billing_address_collection: "required",
allow_promotion_codes: true
})Create a Payment Intent
// Create a payment intent for direct processing
create_payment_intent({
amount: 5000, // $50.00 in cents
currency: "usd",
description: "Monthly subscription payment",
receipt_email: "customer@example.com"
})Create a Customer
// Create a customer record
create_customer({
email: "student@example.com",
name: "John Doe",
metadata: {
student_id: "12345"
}
})Available Tools
Payment Links
create_payment_link- Create new payment linkslist_payment_links- List existing payment linksget_payment_link- Get payment link detailsupdate_payment_link- Update payment link settings
Payment Processing
create_payment_intent- Create payment intentsconfirm_payment_intent- Confirm paymentsget_payment_intent- Get payment detailslist_payment_intents- List payment intents
Products & Prices
create_product- Create productslist_products- List productsget_product- Get product detailscreate_price- Create priceslist_prices- List prices
Customer Management
create_customer- Create customerslist_customers- List customersget_customer- Get customer detailsget_customer_payments- Get payment history
Development
Run in Development Mode
npm run devTest the Server
After building and configuring, restart Claude Desktop and you should see the Stripe tools available in your conversations.
Security Notes
Never expose your Stripe secret keys publicly
Use test keys during development
Set up webhooks in production for reliable payment status updates
Follow Stripe's security best practices
Support
For issues with this MCP server, please check:
Your Stripe API keys are correct
The server builds without errors (
npm run build)Claude Desktop configuration is properly set up
Environment variables are loaded correctly
For Stripe API questions, refer to the Stripe Documentation.
Available Tools
17 toolsconfirm_payment_intentC
Confirm a payment intent
Inputs: id (required), return_url, payment_method.
create_customerC
Create a customer
Inputs: name, email, phone, metadata, +1 more.
create_payment_intentC
Create a payment intent for processing payments
Inputs: amount (required), currency (required), customer, metadata, +2 more.
create_payment_linkB
Create a Stripe payment link for customers to pay
Inputs: line_items (required), metadata, allow_promotion_codes, billing_address_collection.
create_priceC
Create a price for a product
Inputs: product (required), currency (required), metadata, recurring, +1 more.
create_productC
Create a product
Inputs: name (required), metadata, description.
get_customerC
Get customer details
Inputs: id (required).
get_customer_paymentsB
Get payment history for a customer
Inputs: customer_id (required), limit.
get_payment_intentB
Get payment intent details
Inputs: id (required).
get_payment_linkA
Get details of a specific payment link
Inputs: id (required).
get_productB
Get product details
Inputs: id (required).
list_customersD
List customers
Inputs: email, limit.
list_payment_intentsB
List payment intents
Inputs: limit, customer.
list_payment_linksA
List existing payment links
Inputs: limit.
list_pricesC
List prices
Inputs: limit, active, product.
list_productsC
List products
Inputs: limit, active.
update_payment_linkB
Update a payment link (activate/deactivate)
Inputs: id (required), active, metadata.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Tools are clearly divided by resource (payment links, payment intents, products, prices, customers), but there is some potential overlap between payment links and payment intents, and between list_payment_intents and get_customer_payments. Descriptions help distinguish them, but an agent might occasionally misselect.
All tool names follow a consistent verb_noun pattern (e.g., create_payment_link, list_prices, get_customer), using lowercase snake_case throughout. This makes the API predictable and easy to navigate.
17 tools is slightly above the ideal range but still appropriate for Stripe's domain, covering payment links, intents, products, prices, and customers. Each tool addresses a distinct need, though a few could be consolidated without loss.
Core CRUD operations exist for payment links, products, and customers, but are incomplete: products and customers lack update/delete, prices lack a get endpoint, and payment intents lack cancel/refund capabilities. This creates workflow gaps for managing the full lifecycle.
Related MCP Connectors
Stripe payments for AI agents. Create links, verify, manage customers.
Create instxnt.xyz storefronts through Claude: add products, connect Stripe, go live.
Send invoices from Claude and ChatGPT. One sentence becomes a PDF with a Stripe payment link.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Stripe accounts to query customers, revenue, invoices, subscriptions, disputes, and issue refunds.86 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables integration with Stripe APIs through function calling, supporting operations on customers, products, invoices, subscriptions, and more.31,367 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets AI agents accept US payments (cards, Apple Pay, Google Pay) via Stripe hosted checkout. Includes tools to create payment links and query payment status.MIT
- AlicenseAqualityDmaintenanceEnables querying MRR, churn, and revenue from Stripe, Gumroad, and Lemon Squeezy directly inside Claude, allowing natural language questions about business metrics.561 npmMIT