TL;DR: I built a Model Context Protocol server that lets AI assistants like Claude and Cursor query real-time AI quota reset signals across 15+ products.
The Problem
If you're paying for AI subscriptions (OpenAI Codex at $20-200/mo, Claude Pro, Gemini Advanced), quota resets are money. When your quota resets, you want to know immediately.
The problem: resets are scattered across multiple status pages, happen at unpredictable times, and there's no unified API to track them.
The Solution
I built Reset Beer — a dashboard that aggregates official status pages from 15+ AI products and sends alerts when quota reset signals drop.
The MCP integration is what makes it interesting. Instead of just receiving emails, Pro users can connect Reset Beer to their AI assistants and ask: "Any recent quota resets for Codex?"
Architecture
The MCP server is a single Next.js API route that implements JSON-RPC 2.0 over HTTP (Streamable HTTP transport per MCP spec 2025-03-26).
Three tools are exposed:
- list_recent_resets — Query reset events by time range, product, and limit
- get_product_status — Get the latest event for a specific product
- list_products — List all tracked AI products
API Key Authentication
Each Pro user gets a cryptographically random API key (rb_ prefix, 64 hex chars). The key is stored as SHA-256 hash in the database.
What I Learned
- MCP is easier than expected — The spec is well-designed
- API key auth > OAuth for first-party tools — Bearer tokens are simpler
- Calendar rules ≠ actionable signals — Filter predictable events
- Static generation + cookies don't mix — Use client components with Suspense
Try It
- Product: https://reset.beer
- npm:
npm install reset-beer-mcp - GitHub: https://github.com/suxinsk/reset-beer-mcp
Pro is $9.99 one-time (lifetime, no subscription). Free tier available.
Built solo with Next.js 15, Neon Postgres, Better Auth, Resend, and Vercel. Follow on X.
Top comments (0)