Mcp Stripe Acp
Let your coding agent manage Stripe Agent Commerce Protocol flows—checkout, delegated charges, products, and invoices—while you build agentic SaaS or marketplace billing.
Overview
io.github.codespar/mcp-stripe-acp is a Build-phase MCP server that exposes Stripe Agent Commerce Protocol checkout, delegation, products, and invoices to coding agents.
What is this MCP server?
- Stripe ACP: AI agent checkout, payment delegation, products, and invoices
- npm @codespar/mcp-stripe-acp v0.1.2 with stdio MCP transport
- Single secret: STRIPE_API_KEY required at runtime
- Targets agent-native commerce where users authorize the agent to complete purchases
- Payment-platform MCP bridge, not a substitute for Stripe Dashboard policy setup
- Package version 0.1.2
- npm identifier @codespar/mcp-stripe-acp
- stdio transport
Community signal: 252 GitHub stars.
What problem does it solve?
Building agent-mediated checkout in Stripe ACP means juggling REST docs and test keys while your IDE agent cannot safely create or inspect live payment objects.
Who is it for?
Solo builders creating AI agents that complete purchases, manage Stripe products/invoices, or prototype delegated payment UX on top of Stripe ACP.
Skip if: Merchants who only need a static Stripe Checkout link, teams without a Stripe account, or products that require non-Stripe LATAM rails only.
What do I get? / Deliverables
With STRIPE_API_KEY configured, your agent can drive ACP-oriented Stripe tools during integration so delegated payment and catalog code matches real API behavior.
- MCP-exposed Stripe ACP operations for agent-driven checkout and catalog work
- Faster iteration on delegated payment and invoice flows in code
- Live Stripe object interactions from the agent during integration
Recommended MCP Servers
Journey fit
Stripe ACP wiring is implementation work on payment and catalog APIs during product build, before you rely on it in production launch analytics. ACP is a third-party payments API surface; it belongs on the integrations shelf next to other billing and commerce MCP servers.
How it compares
Stripe ACP MCP connector for agents, not a pricing-validation skill or hosted checkout page generator.
Common Questions / FAQ
Who is io.github.codespar/mcp-stripe-acp for?
Developers building agent-driven SaaS or automation where Stripe handles money movement and ACP-style delegation matters.
When should I use io.github.codespar/mcp-stripe-acp?
During build when you are integrating agent checkout, product CRUD, invoices, or payment delegation against Stripe test or live keys.
How do I add io.github.codespar/mcp-stripe-acp to my agent?
Add @codespar/mcp-stripe-acp as an MCP stdio server in Claude Code or Cursor and set the STRIPE_API_KEY environment variable to your Stripe secret key.