MCP-Billing is a comprehensive, self-hosted Next.js and TypeScript boilerplate designed specifically for Model Context Protocol (MCP) servers. Built by Marc Gil, it bridges the gap between AI infrastructure and monetization by providing robust, production-ready backend modules.

The platform delivers everything developers need to commercialize their MCP servers, featuring full OAuth 2.1 + PKCE authorization, secure API key management with zero-downtime rotation, usage-based Stripe billing, and Redis rate limiting. Comprising 7 modular units and backed by over 300 tests, it ensures reliability and scalability.

Unlike closed ecosystems or platforms that take a cut of your revenue, MCP-Billing operates on a simple one-time purchase model with no ongoing revenue share or platform lock-in. Furthermore, its underlying metering core is free and open-source on npm, making it a flexible, developer-first solution for API and AI infrastructure monetization.

Pros of MCP-Billing

Full OAuth 2.1 + PKCE support for secure authentication
Usage-based Stripe billing integration out-of-the-box
API key management featuring zero-downtime rotation
Includes Redis rate limiting and 300+ tests across 7 modules
One-time purchase fee with no revenue share or platform lock-in

Cons of MCP-Billing

Self-hosted setup requires technical configuration and infrastructure management
Limited to Next.js and TypeScript stack environments as a boilerplate
Requires separate configuration and accounts for Stripe integration

Frequently Asked Questions

What is MCP-Billing?

MCP-Billing is a self-hosted Next.js and TypeScript boilerplate that equips MCP servers with OAuth 2.1 + PKCE authentication, API key management, Redis rate limiting, and usage-based Stripe billing.

How much does MCP-Billing cost?

MCP-Billing is available for a one-time fee of €79 with no revenue share or platform lock-in. Additionally, the metering core is free and open source on npm.

What technologies are used to build MCP-Billing?

It is built as a Next.js and TypeScript boilerplate, incorporating Redis for rate limiting, OAuth 2.1 for authentication, and Stripe for usage-based billing.