maarcgiil7/mcp-billing-showcase — explained in plain English
Analysis updated 2026-05-18
See a real example of billing usage events safely so retried requests are not charged twice.
See a working example of an atomic Redis-based sliding window rate limiter.
Decide whether to buy the full paid boilerplate for adding billing to an MCP server.
Learn one approach to handling partial failures and streamed responses in usage-based billing.
| maarcgiil7/mcp-billing-showcase | 0xradioac7iv/tempfs | 7vignesh/pgpulse | |
|---|---|---|---|
| Stars | 0 | 0 | 0 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 4/5 | 3/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
This repo only contains two sample files, the runnable product with setup steps is a separate paid purchase.
This repository is a showcase for a paid boilerplate called MCP-Billing, sold separately on Gumroad, that adds login, API keys, and usage-based billing to MCP servers. MCP servers are a way for AI tools to connect to external services, and this project focuses on the billing side of running one as a paid product: figuring out what actually counts as a billable request when calls can retry, partially fail, or stream data back over time. The full paid product includes OAuth 2.1 login with PKCE, API key creation and rotation, Stripe based usage billing, rate limiting backed by Redis, per user quotas, a dashboard built with Next.js, and over 300 automated tests. This public repository only includes two real code files copied from that product as samples: one showing how usage events are recorded safely so a retried request cannot get billed twice, and one showing the rate limiting logic implemented as a single atomic Redis script. The billing approach records every usage event in a Postgres database first, before trying to report it to Stripe, so a failed Stripe call does not cause the record to disappear. Only requests marked as completed are billed by default, while partial or failed requests are still logged for review. Retried requests are protected from double billing through a database level uniqueness rule rather than a check-then-write pattern that could have a timing gap. The stack described for the full product is Next.js, TypeScript, PostgreSQL through Supabase, Prisma, and Upstash Redis, deployable to Vercel, Railway, or Fly.io. This showcase repository itself does not state a license, and the underlying product is sold rather than given away.
A public showcase of two code samples from a paid boilerplate that adds OAuth login, API keys, and Stripe usage billing to MCP servers.
Mainly TypeScript. The stack also includes TypeScript, Next.js, PostgreSQL.
This is a public sample of a separately sold paid product, no open license is granted for the full codebase.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.