OAuth 2.1 + usage-based Stripe billing for MCP servers
Self-hosted Next.js/TypeScript boilerplate: full OAuth 2.1 + PKCE, API key management with zero-downtime rotation, usage-based Stripe billing, and Redis rate limiting. 7 modules, 300+ tests. One-time €79, no revenue share, no platform lock-in. The metering core is free and open source on npm.
a few months ago i started building custom MCP servers on the side. the tool logic took me an afternoon; the auth and billing infrastructure took weeks. after spending four hours reading RFC 9728 at 3 AM, i ended up parking it with a static API key.
i eventually decided to build it properly using Claude Code as a pair. and yes, AI writes code insanely fast now, that’s literally how this project started. but what an LLM draft doesn't do by default is make the right architectural decisions when money is on the line. early on, the AI generated a webhook handler that returned the exact same 400 error for an invalid signature as it did for a temporary DB outage. that meant Stripe never retried the event, and billing updates vanished in silence. finding, testing, and fixing those silent failures is the actual work. generating code is cheap now; the decisions, the tests, and the edge cases someone already paid to discover are not.
you don’t have to take my word for it, though. I extracted and published the core metering logic as a standalone, free MIT package on npm (`mcp-metering`). you can install it, inspect the code, and judge the engineering quality yourself before deciding if the rest of the stack is worth €79. it’s a full proof of quality, not a stripped-down teaser.
the full boilerplate includes full OAuth 2.1 + PKCE, per-user API key management with zero-downtime rotation, usage-based Stripe billing, and Redis rate-limiting. it’s organized into 7 decoupled modules with 300+ tests. one-time payment of €79, full source code, no revenue share, no platform lock-in, and a 7-day refund policy.
would love to hear your feedback on the architecture or any of the documented trade-offs in the README!
About MCP-Billing on Product Hunt
“OAuth 2.1 + usage-based Stripe billing for MCP servers”
MCP-Billing launched on Product Hunt on July 28th, 2026 and earned 119 upvotes and 13 comments, placing #13 on the daily leaderboard. Self-hosted Next.js/TypeScript boilerplate: full OAuth 2.1 + PKCE, API key management with zero-downtime rotation, usage-based Stripe billing, and Redis rate limiting. 7 modules, 300+ tests. One-time €79, no revenue share, no platform lock-in. The metering core is free and open source on npm.
On the analytics side, MCP-Billing competes within API, SaaS, Developer Tools and GitHub — topics that collectively have 699.7k followers on Product Hunt. The dashboard above tracks how MCP-Billing performed against the three products that launched closest to it on the same day.
Who hunted MCP-Billing?
MCP-Billing was hunted by Marc Gil. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of MCP-Billing including community comment highlights and product details, visit the product overview.
Marc Gil