FAQ

Do I need to understand OAuth 2.1 to use this?#

What if Stripe changes its API?#

The code is in your repository. You control the updates. There is no hosted layer between you and Stripe that can break independently.

Does it work with any MCP server, or only certain frameworks?#

Any. It works as an independent layer: your MCP server calls the auth and billing endpoints over HTTP, so it is framework agnostic. See multi-tenancy.

How does it handle retries and interrupted calls in billing?#

Each usage event carries an idempotency key, so a network retry is charged once. Interrupted calls are recorded as partial and you decide whether to charge them. Full detail in billing decisions.

Is support included?#

Yes. Marc responds to GitHub issues for 60 days from purchase.

Can I use it in client projects?#

Yes, unlimited use. You cannot resell the boilerplate itself. See license.

Is there a refund policy?#

Yes. A 7-day refund if the code does not work in your environment and it cannot be fixed via GitHub issues. No questions asked within that window.

Why not just ask Claude Code to build this?#

You can, and that is literally how it was built, with Claude Code as a pair programmer from day one. Writing the first draft was never the hard part. Early on a webhook handler returned the same 400 for an invalid signature as for a transient database error, which meant Stripe never retried and billing events could silently vanish. Catching that is the actual work. Code is cheap to generate now, the decisions and the tests that pin them down are not.

Check that level of detail yourself before paying: mcp-metering is free and open source.