Model Context Protocol

Stripe MCP Server

Financial Data Connectivity via Model Context Protocol

Enable your AI models to interact with Stripe data securely. Perfect for agents that need to check subscription status, list invoices, or handle refund requests.

Finance and support teams leverage Stripe MCP to transform their billing operations from reactive ticket-handling to proactive AI assistance. Instead of building and maintaining custom API wrappers, your AI agent can directly query customer subscriptions, process refunds, and explain invoices in plain language. This cuts support resolution time, reduces engineering overhead, and ensures financial data stays secure with Stripe's native authentication.

  • ✓Instant access to billing data without building custom integrations
  • ✓AI-powered customer support for billing questions
  • ✓Automated refund and dispute handling workflows
  • ✓Real-time revenue tracking via natural language queries
Deploy Managed ServerExplore Integrations
mcp-config.json
{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": [
  "-y",
  "stripe-mcp-server"
],
      "env": {
        "STRIPE_SECRET_KEY": "your_stripe_secret_key"
      }
    }
  }
}
Real-World Automation

Common Workflows

See how teams combine this MCP with other tools to automate real business processes.

Automated Billing Support

Scenario: A customer emails: 'Why was I charged $49 last month?' Your AI agent instantly investigates and responds with a detailed explanation.
Steps:
  1. Gmail MCP reads the customer's email and extracts email address
  2. Stripe MCP searches for the customer by email
  3. AI retrieves last 3 invoices and identifies the $49 charge
  4. Agent cross-references with product usage (if available)
  5. Drafts a personalized reply explaining the charge and includes invoice PDF link
Outcome: Support ticket resolution drops from 6 hours to 45 seconds. Customer satisfaction scores increase due to instant, accurate responses.

Churn Prevention Alerts

Scenario: Subscription cancellation webhook fires. AI evaluates whether to intervene with a retention offer.
Steps:
  1. Stripe MCP detects subscription cancellation (via webhook or polling)
  2. AI retrieves customer's LTV, usage frequency, and support history
  3. Decision engine: 'High-value user with >12 months tenure'
  4. Linear MCP creates 'retention task' with suggested discount
  5. Slack MCP alerts churn prevention team with full context
Outcome: 15% of at-risk customers retained through timely intervention. Average handling time: 2 minutes vs. manual review of 30+ minutes.

Revenue Verification

Scenario: CFO requests: 'Show me MRR growth from SaaS customers in Europe last quarter.'
Steps:
  1. Stripe MCP filters subscriptions by region (EU) and product type (SaaS)
  2. AI calculates MRR per month for Q1, applies currency conversion
  3. Notion MCP writes summary to finance dashboard
  4. Creates chart data points for presentation
  5. Slack MCP posts the result to #finance-updates
Outcome: Financial reporting task that took 4 hours manually now completes in 90 seconds with zero errors.
Protocol Definition

Available Tools — In Depth

Detailed reference for each tool exposed by this MCP server, with examples and related use cases.

⚒

list_invoices

Retrieve a paginated list of invoices for a specific customer or across the entire account. Supports filtering by date range, status (paid, draft, void), and includes line items, tax details, and payment status. Perfect for answering 'where is my invoice?' or 'show me last quarter's revenue.'

Example:""List all paid invoices for customer_ABC123 from Jan 2025 with total amounts and dates.""
Works great with:search_customersget_balance
⚒

get_balance

Get the current Stripe account balance including available funds, pending payouts, and breakdown by currency. Real-time view of cash position without logging into the dashboard. Use this for daily finance standups or cash flow forecasting.

Example:""What's our current balance in USD and EUR? How much is pending payout?""
Works great with:list_invoicessearch_customers
⚒

search_customers

Flexible customer search across email, name, metadata, and custom fields. Supports advanced queries like 'customers with subscription >$100/month in Germany.' Essential for customer lookup before processing refunds or answering support queries.

Example:""Find customer with email sarah@acme.com and return their subscription IDs and payment methods.""
Works great with:list_invoicescreate_refund
⚒

create_refund

Process a refund for a specific charge or invoice. Can issue full or partial refunds, add memo notes, and reverse the original payment method. Requires careful permission management—only use on agent with approval workflow.

Example:""Refund $29.99 for charge ch_ABC123, reason: 'Customer request within 30-day window.'""
Works great with:list_invoicessearch_customers
Setup Guide

Configuration & Best Practices

Setup Checklist

  • ✓
    STRIPE_SECRET_KEY (required)
    Find in Stripe Dashboard → Developers → API Keys. Use 'Secret Key' (sk_live_*), never publish the publishable key.
  • ✓
    Key permissions
    Full stripe API scope recommended for read+write. If read-only, still requires payments:write for refunds.
  • ✓
    Webhook setup (optional)
    Configure '/api/stripe-webhook' endpoint in Stripe Dashboard → Webhooks for real-time subscription events.
  • ✓
    Test mode first
    Use Stripe test keys (sk_test_*) to validate before production. Create test customers and charges.
  • ✓
    Rate limits
    Stripe allows ~100 requests/second per account. Exceeding returns 429.

Troubleshooting

401 Invalid API Key
Fix: Check you're using Secret Key (sk_live_*), not publishable. Ensure key is active (not revoked).
402 Payment Required / insufficient funds
Fix: Customer has no balance or card on file. Usually not a MCP issue—customer action needed.
429 Too Many Requests
Fix: Stripe rate limit hit. Implement exponential backoff and retry after ~1 second.
Rate limit: 100 requests/second per account (shared across all API calls). Use idempotency keys for retries.

When to Use Stripe MCP Server vs. Alternatives

Use This MCP When:

  • You need AI-native access via natural language
  • Your workflows span multiple tools (MCP composability)
  • You prefer cloud hosting over local Docker
  • You want zero-config deployment with ClawFast
  • Your use case requires LLMs to reason and act autonomously

Consider Alternatives When:

  • You need bulk data sync (use native export/import)
  • Real-time streaming is critical (use native webhooks)
  • You have strict compliance requiring direct API audit logs
  • Your integration is a one-off script (direct SDK may be simpler)
  • You need features not yet exposed by this MCP server
FAQ

Common Questions About Stripe MCP Server

Q: Can I access test mode data?
A: Yes, use Stripe test keys. Test and live data are fully separated—never mix.
Q: What Stripe objects are supported?
A: Invoices, Charges, Customers, Subscriptions, PaymentMethods, Balance, Refunds, Disputes. Some advanced features need direct API.
Q: Can I create charges or process payments?
A: No—MCP is read-only for payments. It can read charges and create refunds but cannot initiate new charges (use Stripe Elements for that).
Q: How do refunds work?
A: create_refund processes refunds to original payment method. Full or partial amounts allowed. Refund appears in Stripe Dashboard instantly.
Q: What about PCI compliance?
A: Stripe is PCI DSS Level 1 compliant. MCP only accesses metadata, not raw card data. Still follow security best practices for token storage.
Q: Are webhooks available?
A: Stripe sends webhooks to your endpoint. You can use a generic webhook MCP to receive them, but consider direct Stripe webhook → your server for high volume.
Q: Currency support?
A: All 135+ Stripe-supported currencies. Balance endpoint returns multi-currency breakdown.
Q: Tax and invoicing details?
A: Yes—invoice line items, tax amounts, and customer tax IDs are returned if present in Stripe.
Customer Success

Success Story: DevTools Pro (B2B SaaS)

Challenge

Support team spent 2 hours daily manually looking up customer subscriptions to answer 'why was I charged' tickets. Finance needed daily revenue snapshots for CFO.

Solution

Deployed Stripe MCP + Gmail MCP + Slack MCP. AI agent auto-responds to billing inquiries and posts Daily MRR reports to Slack.

Results

  • ✓ Support time saved: 40 hrs/month ~$4,000/month in ops cost
  • ✓ Customer response time <1 minute (was 6 hrs)
  • ✓ Daily revenue reporting automated, CFO gets Slack post at 9 AM daily
"Our support team used to dread billing Mondays. Now the AI handles 80% of those tickets before a human even sees them. We've reshifted to proactive customer success."
— Marcus Chen, Head of Operations, DevTools Pro

Combine with Other MCPs

This MCP works great alongside other tools. Here are popular combinations.

hubspot
Link Stripe customers to HubSpot contacts for unified CRM view
→
gmail
Reply to billing inquiries automatically with invoice data
→
slack
Post revenue alerts and charge notifications to finance channels
→
linear
Create finance tasks for refund approvals or disputes
→

Ready for full workflows?

Check out our integration page for Stripe MCP Server to see complete AI agent templates and step-by-step guides.

View Stripe MCP Server Integrations →

Technical Specifications

Protocol
SSE (Server-Sent Events)
Transport
HTTPS (TLS 1.3)
Authentication
Bearer token (Stripe Secret Key sk_live_*)
Rate Limit
100 requests/second per account
Typical Latency
150-400ms
Data Format
JSON
Supported LLMs
Claude 3.5+, GPT-4o, Kimi K2.5
Hosting
ClawFast managed cloud (AWS)
Uptime SLA
99.9%
Last Updated
Real-time via Stripe webhooks (when configured)

Why Managed MCP?

Model Context Protocol (MCP) is the new standard for AI connectivity. While you can host servers locally, ClawFast provides a production-grade managed environment.

  • 24/7 Availability: No need to keep your local machine running.
  • Secure Secrets: API keys are encrypted at rest and never exposed to logs.
  • SSE Protocol: Native Server-Sent Events (SSE) support for cloud-to-cloud connectivity.
  • Zero Config: One-click deployment with pre-configured templates.

Looking for more ways to use Stripe MCP Server?

Explore our high-level integration page for Stripe MCP Server to see business use cases and ready-to-use AI agent templates.

View Stripe MCP Server Integrations →

Connect Stripe MCP Server to your AI stack today

Deploy your managed MCP server in under 60 seconds.

Start Free Deployment