Skip to main content
Glama
Stripe MCP Server

Stripe MCP Server

by jsyapps

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

  • 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 install

2. Build the Server

npm run build

3. Set Up Environment Variables

Create a .env file in the stripe_mcp directory:

STRIPE_SECRET_KEY=sk_test_your_stripe_secret_key_here

You 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 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

  • create_payment_link - Create new payment links

  • list_payment_links - List existing payment links

  • get_payment_link - Get payment link details

  • update_payment_link - Update payment link settings

Payment Processing

  • create_payment_intent - Create payment intents

  • confirm_payment_intent - Confirm payments

  • get_payment_intent - Get payment details

  • list_payment_intents - List payment intents

Products & Prices

  • create_product - Create products

  • list_products - List products

  • get_product - Get product details

  • create_price - Create prices

  • list_prices - List prices

Customer Management

  • create_customer - Create customers

  • list_customers - List customers

  • get_customer - Get customer details

  • get_customer_payments - Get payment history

Development

Run in Development Mode

npm run dev

Test 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:

  1. Your Stripe API keys are correct

  2. The server builds without errors (npm run build)

  3. Claude Desktop configuration is properly set up

  4. Environment variables are loaded correctly

For Stripe API questions, refer to the Stripe Documentation.

Available Tools

17 tools
confirm_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_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_productB

Get product details

Inputs: id (required).

list_customersD

List customers

Inputs: email, limit.

list_payment_intentsB

List payment intents

Inputs: limit, customer.

list_pricesC

List prices

Inputs: limit, active, product.

list_productsC

List products

Inputs: limit, active.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Stripe accounts to query customers, revenue, invoices, subscriptions, disputes, and issue refunds.
      86 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with Stripe APIs through function calling, supporting operations on customers, products, invoices, subscriptions, and more.
      31,367 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables querying MRR, churn, and revenue from Stripe, Gumroad, and Lemon Squeezy directly inside Claude, allowing natural language questions about business metrics.
      5
      61 npm
      MIT