Launching today
MCP-Billing
OAuth 2.1 + usage-based Stripe billing for MCP servers
35 followers
OAuth 2.1 + usage-based Stripe billing for MCP servers
35 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.
Products used by MCP-Billing
Explore the tech stack and tools that power MCP-Billing. See what products MCP-Billing uses for development, design, marketing, analytics, and more.
Engineering & Development 2
Engineering & Development 2
UpstashServerless data platform for Redis and Kafka
5.0 (32 reviews)
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 exactly what both of those checks need to stay correct under concurrency.
Claude CodeAnthropic’s deep-context AI coder
5.0 (583 reviews)
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.
Finance 1
Finance 1
StripeFinancial infrastructure for the internet
4.9 (470 reviews)
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 line items from raw usage data.