Launched this week
MCP-Billing
OAuth 2.1 + usage-based Stripe billing for MCP servers
115 followers
OAuth 2.1 + usage-based Stripe billing for MCP servers
115 followers
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.
The Stripe webhook example is a strong trust signal. For MCP servers, billing is one of those areas where AI-generated code can look complete while the edge cases quietly decide whether the product is usable.
One onboarding thing Iād want as a small builder: a checklist or test mode that proves the money path end to end ā auth, metering, retry behavior, failed payments, and key rotation ā before I connect a real server.
The decision to ship the metering core as free open source while keeping the full stack paid is a really thoughtful move, it lets developers build trust with the hardest part before committing to the boilerplate.
The decision to keep the metering core open source while charging for the rest is genuinely smart, basically lets people trust the math before they trust the product. Love that there's no revenue share either, feels refreshing.