Stripe is included because its hosted MCP can expose payments, billing, refunds, reports, and other supported API resources through broad read and write tools under granular authorization.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Supported Stripe API resources including customers, charges, refunds, PaymentIntents, Checkout Sessions, invoices, subscriptions, products, prices, payment links, disputes, balances, payouts, reports, and separately previewed Treasury or money-management resources.
Use stripe_api_read for supported GET methods, search or fetch Stripe resources, retrieve account information, inspect reports, and query Stripe documentation and implementation guidance.
Use stripe_api_write for supported POST, PATCH, PUT, and DELETE methods, plus named actions such as creating refunds or reports; actual effects depend on the authorized API method and environment.
Interactive clients use Stripe OAuth consent with user-based granular permissions and revocable sessions. Autonomous agents can use restricted API keys; connected-account calls require restricted keys with Connect permissions and a Stripe-Account header.
Administrators enable MCP separately for sandbox and live mode and can revoke user sessions within the current account, organization, and environment scope. Use restricted keys and access policies for autonomous software.
Connected-account MCP calls cannot use OAuth and require restricted keys plus Stripe-Account. Treasury balance summary is public preview, while broader agentic Treasury money movement remains request-access.
First-party MCP tool catalog
The named tools in Stripe's first-party MCP documentation for mcp.stripe.com. Generic API read and write tools expose only the supported API methods documented on the same page. Reviewed Jul 10, 2026. OAuth grants user-based permissions; restricted API keys can narrow agent access. Writes, refunds, connected-account actions, and reports can be consequential and should use explicit confirmation.
stripe_api_searchreadstripe_api_detailsreadstripe_api_readreadstripe_api_writeconsequential writeget_stripe_account_inforeadcreate_refundconsequential writesearch_stripe_resourcesreadfetch_stripe_resourcesreadsearch_stripe_documentationreadstripe_implementation_plannerdraftsend_stripe_mcp_feedbackwritestripe_reportread/writeTry a broader name, group, action, or availability term.
First-party access
Agent access
Support: Official MCP server
Read scope: Broad supported GET access through stripe_api_read, supplemented by resource search/fetch, account, report, and knowledge tools; returned data remains constrained by the OAuth grant or key permissions.
Write scope: 5 of 12 reviewed named tools have a write, draft, or mixed action label, including stripe_api_write, create_refund, stripe_implementation_planner, send_stripe_mcp_feedback, stripe_report. Read each catalog boundary before enabling them.
Authentication: OAuth consent and revocable user sessions are preferred for interactive MCP clients. Restricted API keys can authenticate clients without OAuth, autonomous agents, and Connect calls made on behalf of connected accounts.
Approval boundary: Enable human confirmation for stripe_api_write and named financial actions, especially refunds, invoice finalization, subscription cancellation, disputes, tax settings, and live-mode operations. Test mode and authorization narrow exposure but do not replace confirmation.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Stripe ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
MCP tools, reads, writes, OAuth, keys, sessions, environments, Connect, and previews
MCP tools, authentication, session controls, Connect, and preview limits reviewed 2026-07-22
First-party API reference or API overview recorded for this platform.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Reverified the named access facet exactly as bounded by the reviewed first-party record.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
restricted-key permissions, environment separation, access policies, rotation, and request logs
Stripe API key governance reviewed 2026-07-22
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.