
MCP-Billing tech stack
OAuth 2.1 + usage-based Stripe billing for MCP servers
The stack
“i used Claude Code as a pair programmer with a strict module-by-module workflow: write the architecture spec first, let it draft the implementation, and manually review every gate and edge case against the doc before moving to the next module.” — the maker, Sep 2026 ↗
“i chose stripe billing meters specifically for their usage-based metering api. it's built for exactly this pattern: you just report the usage events and let stripe handle all the aggregation and invoicing. beats the hell out of me trying to hand-roll invoice l…” — the maker, Sep 2026 ↗
“i needed atomic sliding-window rate limiting and a strict fail-closed quota check, but i really didn't want to manage redis infrastructure myself. upstash's rest client made it trivial to run lua scripts atomically straight from serverless functions, which is…” — the maker, Sep 2026 ↗
Its market on Product Hunt
Authentication and identity platforms
MCP-Billing next to products in authentication and identity platforms
- Hosting33% of 9 pick
Amazon Web Services — MCP-Billing went with
Netlify - Transactional Email67% of 6 pick
Resend — not known for MCP-Billing - Frontend Framework100% of 5 pick
Next.js — not known for MCP-Billing
Built on a similar stack
Products that share the most distinctive building blocks with MCP-Billing.