Stripe integration: operations for AI agents
Stripe connects to Type.com as an integration. This page lists the 9 operations documented for Claude and Codex in Type.com: 6 read, 2 write, 1 destructive.
About Stripe
Search the Stripe API and documentation, inspect account data, run eligible analytics, and request permitted API changes through Stripe's hosted MCP server. Available operations depend on the saved key, account and product permissions.
Categories: Payment processing, Accounting
How to connect Stripe to Type.com
- Connect
- API key sent as bearer token; current Stripe MCP documentation recommends an Agent API key
- Access
- Organization connection: one shared account for the workspace.
- MCP
- This integration is not available through Type’s MCP server. It remains available in Type.
To add the connection, follow the steps in Space connections.
Documented operations
9 operations. Your connection's permissions determine which operations are available.
- Read
Get stripe account info
This will get the account info for the logged in Stripe account.
- Read
Search stripe documentation
Search 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.
- Read
Stripe analytics
This 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`. Start SQL with a one-line `--` comment summarizing how the query answers the user's question. 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 (every few seconds) 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
- Read
Stripe api details
Get 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, enum values, or optional query parameters. You can skip it when the stripe_api_search result already lists every parameter you need, or when you've already fetched this operation's details. The response may include an "LLM Context" section with usage guidance specific to the operation — follow any instructions there.
- Read
Stripe api read
Read data from any Stripe API GET operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to see its parameters, unless the search result already lists everything you need or you've already fetched this operation's details. 3. Call this tool with the stripe_api_operation_id and a parameters object containing path and query parameters. Path parameters use the name inside the curly braces of the path: for GET /v1/customers/{id}, pass {"id": "<customer ID>"}. 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).
- Read
Stripe api search
Search 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, path parameters, required query parameters, and top-level body parameter names with types. Does not include optional query parameters, parameter descriptions, enum values, or nested object fields — use stripe_api_details to get those before calling the relevant Stripe API execution tool.
- Write
Send stripe feedback
Share feedback about Stripe's products. Submit when the user gives product feedback or you observe something concrete that worked or failed. Do not report model behavior, the user's local environment, an unclear prompt, or a recovered tool error. Use actor "human" for the user's own words; "agent" for your observations. Not a support channel — no ticket or reply.
- Write
Stripe implementation planner
Stripe integration planner. Use this tool to help users accept payments, sell products online, set up billing, set up a marketplace or platform, 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.
- Destructive
Stripe api write
Write 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 see its parameters, unless the search result already lists everything you need or you've already fetched this operation's details. Always use it 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 together. Path parameters use the name inside the curly braces of the path: for POST /v1/payment_links/{id}, pass {"id": "<payment link ID>", "active": false}. 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).
No operations match.
Not supported
- Resources and operations outside the saved key's permissions or enabled Stripe products
- Stripe OAuth sign-in through this Type native provider
- Ordinary secret/restricted keys without the Agent tag after Stripe's announced December 2026 MCP cutoff. Use the credential type required by Stripe for your MCP connection.
Example prompts
- What was our MRR and net churn for each of the last six months?
- Find the customer with email jane@acme.com and list their open invoices.
- Create a 20% off coupon that lasts three months and tell me its ID.
Get started
- Open Space settings → Connections and search for Stripe.
- Connect your account and add the connection to the Space.
- Ask for what you need in any thread in that Space.
See How connections work for access and permissions, or browse all integrations.