BYO-UI
Stripe

Stripe

Curated anchor platform in payments, billing, and revenue operations with material relevance to the Marcom operating stack and a first-party developer surface.

Commerce & paymentsSystem of recordBYO-UI-ready platform
Representative source ↗Product site ↗
System roleSystem of record
Access maturityBYO-UI-ready platform
Agent postureFirst-party provider
Reference updatedNot stated by publisher
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

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.

01 · Records and state owned

Generic Stripe API read and write tools plus resource search/fetch, refunds, reports, analytics and documentation; OAuth grants user-based granular permissions

02 · Data you can retrieve

Generic Stripe API read and write tools plus resource search/fetch, refunds, reports, analytics and documentation; OAuth grants user-based granular permissions

03 · Actions and write paths

Stripe's first-party MCP/agent surface includes state-changing tools in the documented capability area: Generic Stripe API read and write tools plus resource search/fetch, refunds, reports, analytics and documentation; OAuth grants user-based granular permissions. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.

04 · Authentication and permissions

Profiles and patterns must treat refunds, payment, billing and destructive operations as consequential and require test mode, explicit approval, narrow OAuth authorization and audit logging. Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary.

05 · Monitoring, approval, and recovery

Stripe's broad stripe_api_write tool can invoke POST, PATCH, PUT and DELETE API methods. Profiles and patterns must treat refunds, payment, billing and destructive operations as consequential and require test mode, explicit approval, narrow OAuth authorization and audit logging. Stripe's broad stripe_api_write tool can invoke POST, PATCH, PUT and DELETE API methods. Profiles and patterns must treat refunds, payment, billing and destructive operations as consequential and require test mode, explicit approval, narrow OAuth authorization and audit logging.

06 · Gaps and implementation limits

Stripe's broad stripe_api_write tool can invoke POST, PATCH, PUT and DELETE API methods. Profiles and patterns must treat refunds, payment, billing and destructive operations as consequential and require test mode, explicit approval, narrow OAuth authorization and audit logging.

First-party MCP tool catalog

12 named MCP tools · Stripe remote server

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.

First-party exact listComplete list on cited pageStripe MCP server
Generic API access4
stripe_api_searchreadstripe_api_detailsreadstripe_api_readreadstripe_api_writeconsequential write
Accounts, refunds, resources, documentation, and reporting8
get_stripe_account_inforeadcreate_refundconsequential writesearch_stripe_resourcesreadfetch_stripe_resourcesreadsearch_stripe_documentationreadstripe_implementation_plannerdraftsend_stripe_mcp_feedbackwritestripe_reportread/write
Catalog evidence: Stripe MCP server: Tools

First-party access

Documented surfaces

Stripe Sigma SQL ↗Stripe Sigma provides SQL reporting over Stripe data as a separately activated product. Availability and API status must be checked independently from the core Stripe API and MCP tool surface.Source: Reporting and reconciliation with SigmaMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPStripe-hosted remote API and knowledge MCPCurrent documented service

Role: provider

Read scope: Generic Stripe API read and write tools plus resource search/fetch, refunds, reports, analytics and documentation; OAuth grants user-based granular 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: Profiles and patterns must treat refunds, payment, billing and destructive operations as consequential and require test mode, explicit approval, narrow OAuth authorization and audit logging.

Approval boundary: Stripe's broad stripe_api_write tool can invoke POST, PATCH, PUT and DELETE API methods. Profiles and patterns must treat refunds, payment, billing and destructive operations as consequential and require test mode, explicit approval, narrow OAuth authorization and audit logging.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation5

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Stripe ships these experiences.

Single-platform patterns

  • Revenue reconciliation and billing-operations console
  • Revenue reconciliation console
  • Commerce operations cockpit
  • Customer-resolution workbench
Use in the brief composer →

Multi-platform compositions

  • Stripe + CRM or support system: revenue reconciliation console
  • Stripe + lifecycle platform + analytics or finance system: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“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.

6 recorded sources
MCPRepresentative source
https://docs.stripe.com/mcp ↗

Stripe's broad stripe_api_write tool can invoke POST, PATCH, PUT and DELETE API methods. Profiles and patterns must treat refunds, payment, billing and destructive operations as consequential and require test mode,…

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

APISource inventory
https://docs.stripe.com/api ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Developer docsSource inventory
https://docs.stripe.com/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Webhooks / extensionsSource inventory
https://docs.stripe.com/webhooks ↗

First-party webhook, event, SDK, embedded-app, or extension documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://stripe.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Feb 20, 2026
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Stripe Sigma SQLTargeted review
Reporting and reconciliation with Sigma ↗

Stripe Sigma provides SQL reporting over Stripe data as a separately activated product. Availability and API status must be checked independently from the core Stripe API and MCP tool surface.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party access review

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.