Skip to main content
Stripe MCP logo
  • Category: payment processing
  • Auth: DCR_OAUTH
  • Composio-managed OAuth available? No
  • Tools: 10
  • Triggers: 0
  • Slug: STRIPE_MCP
  • Version: 20261018_00

Tools

Slug: STRIPE_MCP_LIST_AVAILABLE_ACCOUNTS_OR_ORGSLists all Stripe accounts in this session with their stripe_context and livemode values.
  • Call this first to get stripe_context and livemode before any account-specific operation.
  • After calling, ask the user which account to use unless already specified.
  • Warn the user before switching between testmode and livemode.

Output

array
required
Slug: STRIPE_MCP_MANAGE_STRIPE_ACCOUNTSReturns a URL to the Stripe Dashboard where users can add accounts, remove accounts, or change permissions for this session.
  • Use when the user wants to add, remove, or modify permissions for an account.
  • Call this directly — no need to call list_available_accounts_or_orgs first.
  • Present the URL to the user and wait for them to confirm they completed their changes.
  • After confirmation, call list_available_accounts_or_orgs to sync the updated account list.

Output

string
required
URL to the Stripe Dashboard page where the user can manage accounts and permissions
Slug: STRIPE_MCP_SEARCH_STRIPE_DOCUMENTATIONSearch the Stripe documentation for the given question and language.It takes two arguments:
  • question (str): The user question to search an answer for in the Stripe documentation.
  • language (str, optional): The programming language to search for in the documentation.

Input Parameters

string ("dotnet" | "go" | "java" | "node" | "php" | "ruby" | "python" | "curl")
The programming language to search for in the documentation.
string
required
The user question about integrating with Stripe will be used to search the documentation.
boolean
When set to true, search only in the Stripe API reference documentation instead of the full documentation set. Use true when users need specific API implementation details, code examples, or parameter references. Use false (default) for conceptual explanations, best practices, integration guides, or troubleshooting help.

Output

array
required
Slug: STRIPE_MCP_SEND_STRIPE_MCP_FEEDBACKSubmit feedback from user or agent about Stripe’s MCP server tools.Valid: “the search tool returned irrelevant results”, “I wish there was a tool for X” Invalid: Stripe API complaints, AI model issues, IDE/environment problems
  • Only call when feedback clearly targets MCP tools.
  • If feedback is about one specific tool, include its name in tool_name.
  • If feedback is from user, quote their exact message and set source to “user”.
  • If a tool didn’t follow your expectations as an agent, set source to “agent”.

Input Parameters

string
required
User’s exact message containing feedback. Max 1000 chars.
string ("user" | "agent")
required
user or agent
string
required
User persona, their broader goal, current task, and estimated technical proficiency.
string ("positive" | "negative" | "neutral")
required
positive, negative, or neutral
string
The name of the tool the user is giving feedback about. Include if confident that feedback is about a specific tool.

Output

string
required
string
required
boolean
required
Slug: STRIPE_MCP_STRIPE_ANALYTICSThis tool is for analyzing Stripe Sigma and Metrics data (e.g. about revenue, charges, products, invoices, subscriptions, disputes, transactions, tax tables, payments etc) and running SQL-based reporting queries. Use it for historical analytics, aggregations, and business intelligence questions (e.g. MRR, churn, cohorts, revenue trends). Prefer this tool over making multiple Stripe API calls that would need to be joined or aggregated client-side.

SQL Query Runs

execute_query_run: Runs a SQL query (Trino) against reporting tables. Requires sql. Returns a QueryRun object; use retrieve_query_run to poll. retrieve_query_run: Retrieves a QueryRun’s status and results. Requires query_run_id. search_query_tables: Searches available reporting tables by keyword. Requires search_string. retrieve_query_table: Gets full schema for a specific table. Requires table_name, which is the name parameter in each table. execute_query_template: Starts a pre-built query template for subscription/billing metrics (Trino, async). Requires metric. Optional: dimensions, grains, metric_filters. Returns a query_run_id; use retrieve_query_template to poll for results. retrieve_query_template: Retrieves the status/results of a template run started by execute_query_template. Requires query_run_id.

workflow (custom SQL):

  1. search_query_tables: find relevant tables
  2. retrieve_query_table: get column names and types
  3. execute_query_run: run SQL
  4. retrieve_query_run: poll status, get download link

workflow (query templates):

  1. execute_query_template: start a template-based metric query (returns a query_run_id)
  2. retrieve_query_template: poll with query_run_id (exponential backoff) until status is ‘succeeded’, then get download link

Return types

All monetary values returned by this tool are expressed in the smallest currency unit. For example:
  • 1000 is 10 USD (most two-decimal currencies like GBP, EUR, AUD, CAD, divide by 100 to get the major unit value)
  • 10 is 10 JPY (zero-decimal currency)
  • 10000 is 10 BHD (three-decimal currency)
  • 1000000 is 1 USDC If you don’t know how many decimals are in a currency’s minor units, use the search_stripe_documentation tool to look it up in https://docs.stripe.com/currencies#minor-units

Input Parameters

string ("execute_query_run" | "retrieve_query_run" | "search_query_tables" | "retrieve_query_table" | "execute_query_template" | "retrieve_query_template")
required
The intent of the tool call.
object
The parameters for the tool call. Required parameters depend on the intent.
boolean
required
Whether to operate in livemode (true) or test mode/ sandbox (false). Must match the livemode of the stripe_context account.
string
required
The account to target for this request. Use the stripe_context value returned by list_available_accounts_or_orgs.
Slug: STRIPE_MCP_STRIPE_API_DETAILSGet detailed parameter information for a specific Stripe API operation. Provide the stripe_api_operation_id from stripe_api_search results to see all path, query, and body parameters with their types, descriptions, and whether they are required.Use before calling the relevant Stripe API execution tool for operations with nested object fields.The response may include an “LLM Context” section with usage guidance specific to the operation — follow any instructions there.

Input Parameters

boolean
required
Whether to operate in livemode (true) or test mode/ sandbox (false). Must match the livemode of the stripe_context account.
string
required
The account to target for this request. Use the stripe_context value returned by list_available_accounts_or_orgs.
string
required
The operation ID to get details for (e.g. ‘PostCustomers’, ‘GetPaymentIntents’)

Output

string
Supplemental usage guidance for this operation, if available
string
required
The OpenAPI Specification Version that the MCP Server used to look for the operation
Slug: STRIPE_MCP_STRIPE_API_READRead data from any Stripe API GET operation:
  1. Use stripe_api_search to find the operation ID.
  2. Use stripe_api_details to understand its parameters (required for operations with nested object fields like address, metadata, or restrictions).
  3. Call this tool with the stripe_api_operation_id and a parameters object containing path and query parameters. For mutations (POST/PATCH/PUT/DELETE), use stripe_api_write instead. Monetary values in responses are in the smallest currency unit (e.g. 1000 = $10.00 USD for most currencies).

Input Parameters

boolean
required
Whether to operate in livemode (true) or test mode/ sandbox (false). Must match the livemode of the stripe_context account.
object
required
Parameters for the API call. Include path parameters (e.g. ‘customer’ for /v1/customers/{customer}), query parameters, and body parameters. Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string.
string
required
The account to target for this request. Use the stripe_context value returned by list_available_accounts_or_orgs.
string
required
The operation ID to execute
Slug: STRIPE_MCP_STRIPE_API_SEARCHSearch for Stripe API operations by providing an intent and a resource to operate on.For the resource, use a specific, descriptive phrase (e.g. “issuing card transactions”, “payout methods”, “outbound payments”) rather than a single generic noun — Stripe has many similar resources, and the extra qualifiers help disambiguate between them rather than causing a miss. Only fall back to the bare core noun (e.g. “transactions”) if a specific multi-word search returns no results.Returns matching operations with their HTTP method, path, summary, and top-level parameter names with types. Does not include parameter descriptions, enum values, or nested object fields — use stripe_api_details to get those before calling the relevant Stripe API execution tool.

Input Parameters

integer
Maximum number of results to return
string
required
The intent of the operation
boolean
required
Whether to operate in livemode (true) or test mode/ sandbox (false). Must match the livemode of the stripe_context account.
string
required
Target resource the operation is looking to manipulate
string
required
The account to target for this request. Use the stripe_context value returned by list_available_accounts_or_orgs.

Output

array
required
List of operations matching the criteria
string
required
The OpenAPI Specification Version that the MCP Server used to look for the operation
Slug: STRIPE_MCP_STRIPE_API_WRITEWrite data via any Stripe API POST/PATCH/PUT/DELETE operation:
  1. Use stripe_api_search to find the operation ID.
  2. Use stripe_api_details to understand its parameters (required for operations with nested object fields like address, metadata, or restrictions).
  3. Call this tool with the stripe_api_operation_id and a parameters object containing path, query, and body parameters. For read-only lookups (GET), use stripe_api_read instead. All monetary amounts must be in the smallest currency unit (e.g. 1000 = $10.00 USD for most currencies).

Input Parameters

boolean
required
Whether to operate in livemode (true) or test mode/ sandbox (false). Must match the livemode of the stripe_context account.
object
required
Parameters for the API call. Include path parameters (e.g. ‘customer’ for /v1/customers/{customer}), query parameters, and body parameters. Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string.
string
required
The account to target for this request. Use the stripe_context value returned by list_available_accounts_or_orgs.
object
This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the approval_token parameter. If it requires human confirmation, the response will include an approval request ID and a URL to an approval page for the human to approve the tool call. You, as the LLM agent, should: 1. Present this URL to the human as a clickable markdown link. Tell them that they have to approve this tool call at that URL, and that they should tell you when they have approved the operation. 2. The human will approve that call. 3. After the human tells you they have approved the operation, you must call the tool again with the approval_token parameter and the exact same parameters. The operation will then go through.
string
required
The operation ID to execute
Slug: STRIPE_MCP_STRIPE_IMPLEMENTATION_PLANNERStripe payment integration planner. Use this tool to help users accept payments, sell products online, set up billing, or build any Stripe integration. Call this BEFORE writing code when the user wants to charge customers, add a checkout flow, handle subscriptions, create invoices, or monetize their app.WHEN TO USE: Call this tool when the user wants to:
  • Accept payments, take payments, or charge customers (credit cards, bank transfers, wallets)
  • Sell online, build e-commerce, add a shopping cart, or create a checkout page
  • Set up subscriptions, recurring billing, metered billing, or usage-based pricing
  • Send invoices or collect one-time payments
  • Add Stripe to their app, integrate Stripe, or build a payment flow
  • Understand which Stripe products to use (Checkout, Elements, Payment Intents, Connect, Billing)
  • Plan an integration architecture before writing code
  • Monetize an app, add billing, or start charging users
FIRST CALL GUIDANCE: Ask the user about their business and payment requirements before choosing a use case:
  • What do they sell? (physical goods, digital products, SaaS, services, marketplace)
  • Payment model? (one-time, subscriptions, invoices, usage-based)
  • Platform? (web, mobile app, in-person, payment links)
  • Complexity? (simple payment link vs. custom integration in existing tech stack) Then pass their full description as the message parameter.
Returns JSON with use cases, decision trees, documentation links, and a guide_id for follow-up calls.RULES:
  • Do NOT pass a guide_id unless you received it from this tool in this conversation.
  • Do NOT retry with different guide_ids if one fails — omit guide_id to start fresh.

Input Parameters

boolean
Set to true when returning the completed decision tree with your chosen options to receive the finalized integration guide.
string
required
For new guides: describe the use case or business requirements. For existing guides: provide the latest user response or the full accepted transcript.
string
ONLY pass a guide_id that was returned by a previous call to this tool in this conversation. Never fabricate, guess, or reuse guide_ids from other sessions. If you do not have a guide_id from a prior response, omit this field entirely. Invalid guide_ids will be rejected.
boolean
required
Whether to operate in livemode (true) or test mode/ sandbox (false). Must match the livemode of the stripe_context account.
string
required
The account to target for this request. Use the stripe_context value returned by list_available_accounts_or_orgs.