MCP Pool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRIPE_SECRET_KEY | No | Secret key for Stripe API authentication (e.g., sk_test_...), required when using the Stripe MCP server |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_customerA | Retrieves full details for a specific Stripe customer, including their email, balance, and metadata. Use this when you have a specific customer ID (starting with cus_). |
| list_customersA | Lists the most recent Stripe customers. Useful for finding a customer by their name or email if you don't have their ID. |
| get_payment_intentA | Retrieves details for a specific Stripe PaymentIntent, including status, amount, and any errors. Use this to check the status of a specific transaction. |
| list_payment_intentsA | Lists recent PaymentIntents. Useful for seeing the latest transactions or finding a specific one by date. |
| get_balanceA | Retrieves the current Stripe balance, including available and pending funds for different currencies. |
| get_subscriptionA | Retrieves details for a specific Stripe subscription, including current status, plan, and next billing date. |
| list_subscriptionsA | Lists recent subscriptions. Useful for summarizing active plans. |
| get_invoiceA | Retrieves a specific invoice, including line items and payment status. |
| list_invoicesB | Lists recent invoices. Useful for checking payment history for a customer. |
| get_couponA | Retrieves details of a specific coupon or discount code. |
| list_couponsA | Lists active coupons and discounts. |
| get_productA | Retrieves details of a specific Stripe product. |
| list_productsA | Lists active products. Useful for checking the product catalog. |
| get_priceB | Retrieves details of a specific price object. |
| list_pricesA | Lists prices. Useful for checking available pricing plans. |
| get_checkout_sessionA | Retrieves details of a specific Stripe Checkout session. |
| list_checkout_sessionsB | Lists recent Checkout sessions. |
| get_payoutA | Retrieves details of a specific Stripe payout to your bank account. |
| list_payoutsB | Lists recent payouts. |
| get_disputeA | Retrieves details of a specific dispute (chargeback). |
| list_disputesB | Lists recent disputes. |
| get_tax_rateA | Retrieves details of a specific tax rate. |
| list_tax_ratesA | Lists active tax rates. |
| create_refundA | Creates a refund for a specific PaymentIntent. Can refund the full amount or a partial amount. This is a destructive financial operation. |
| update_customer_metadataA | Updates the metadata key-value pairs on a Stripe customer. Existing keys not included in the request are left unchanged. |
| update_subscriptionA | Updates a Stripe subscription. Can schedule cancellation at period end or change the subscription's price. |
| create_invoiceA | Creates a new draft invoice for a customer. The invoice must be finalized before it can be paid. |
| finalize_invoiceA | Finalizes a draft invoice, transitioning it to 'open' status so it can be paid. This action cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Each tool targets a distinct Stripe resource or action, with clear separation between get, list, create, and update operations. There is no ambiguity between tools like get_invoice and list_invoices or create_invoice and finalize_invoice.
All tool names follow a consistent verb_noun pattern (e.g., create_invoice, get_balance, list_customers). The naming convention is uniform and predictable, aiding agent comprehension.
With 28 tools, the count is on the high side but justified given the breadth of Stripe's API surface. It covers many objects but feels slightly heavy; a more focused subset could improve usability.
The set covers core retrieval and listing operations well, but lacks several important create and update actions (e.g., no create_product, create_customer, update_invoice). This leaves gaps for common workflows like updating a customer's email or creating a product.