MCP-Billing

MCP-Billing is a comprehensive self-hosted boilerplate designed for developers and businesses looking to implement secure authentication and sophisticated usage-based billing for their services, particularly those involving MCP servers. It provides a robust foundation for managing API access, user authentication, and payment processing, enabling creators to monetize their applications effectively without vendor lock-in. The core problem MCP-Billing addresses is the complexity and time investment required to build secure and reliable authentication and billing systems from scratch. Developers often face challenges in implementing standards like OAuth 2.1, managing API keys securely, and integrating with payment gateways like Stripe for usage-based models. These critical components, if not implemented correctly, can lead to security vulnerabilities, billing errors, and a poor user experience, diverting valuable development time away from core product features. Key features of MCP-Billing include full OAuth 2.1 and PKCE support, ensuring secure authorization flows for users and applications. It also offers advanced API key management, including zero-downtime rotation, which is crucial for maintaining service availability during key updates. The system integrates seamlessly with Stripe for usage-based billing, allowing businesses to charge customers based on their actual consumption of services. Furthermore, it incorporates Redis rate limiting to protect APIs from abuse and ensure fair usage for all users. The boilerplate is built with a focus on developer experience and reliability. It comprises 7 decoupled modules, each designed for specific functionalities, and is supported by over 300 tests to ensure stability and correctness. The inclusion of a free and open-source metering core on npm (`mcp-metering`) allows developers to inspect the quality of the core logic before committing to the full boilerplate, fostering trust and transparency. MCP-Billing's approach emphasizes a secure, self-hosted architecture that gives users full control over their data and infrastructure. By providing a pre-built, well-tested foundation, it significantly reduces the development time and risk associated with building these complex systems. The use of modern technologies like Next.js and TypeScript ensures a scalable and maintainable codebase. The primary benefits for users include enhanced security through robust authentication protocols, reliable and flexible monetization with usage-based billing, and improved API stability through rate limiting and secure key management. The self-hosted nature provides data sovereignty and avoids platform lock-in, offering a one-time purchase with no revenue share. Concrete use cases for MCP-Billing include SaaS platforms that need to manage user access and charge based on API calls, microservices requiring secure inter-service communication with metered usage, and any application that benefits from a tiered or consumption-based pricing model. It's ideal for developers building custom MCP servers or any service where granular access control and usage tracking are paramount. MCP-Billing is a one-time purchase for €79, offering full source code without revenue share or platform lock-in, and includes a 7-day refund policy. The core metering logic is available as a free, open-source MIT package on npm. The technology stack includes Next.js, TypeScript, Stripe for billing, and Redis for rate limiting. It is suitable for developers, startups, and established businesses seeking a secure and scalable solution for authentication and billing. In summary, MCP-Billing provides a secure, feature-rich, and cost-effective boilerplate for implementing OAuth 2.1, API key management, and usage-based Stripe billing, empowering developers to build and monetize their services with confidence and control.