How does billing work?

Each paid tool call sends a Stripe Billing Meter event with an idempotent identifier, so retries can't double-bill. Users get a free monthly quota, then an upgrade link in the tool result, with Stripe Checkout and the Customer Portal for subscriptions. A cron re-sends usage if Stripe calls fail.

Which MCP clients does it work with?

Claude Code, Cursor and Claude Desktop (via mcp-remote), using API keys. Claude.ai web connectors need OAuth, which is not included; the docs show where to swap it in.

Can I try it without Stripe or Supabase accounts?

Yes. Demo mode runs locally with one command and needs no Supabase or Stripe accounts.

What has been tested?

42 tests cover protocol (both spec eras), auth, quotas, metering, outage recovery, rate limits, webhook signatures, SQL/RLS and the Server Card / AI Catalog endpoints, and next build passes. A live Supabase project and live Stripe calls have not been tested, so run the launch checklist in Stripe test mode first.

Can I sell products built with it?

Yes. The single-developer commercial licence lets you build and sell unlimited products. You can't resell the template itself.

MCP STARTER · SDK v2 · SPEC 2026-07-28 · $49 one-time

A remote MCP server you can charge for, on the stack you already use

Building an MCP tool takes a weekend. Billing for it is the hard part. This Next.js + Supabase + Stripe template ships with API keys, a free tier, Stripe usage-based billing, rate limits, and a usage dashboard, all wired up and covered by 42 tests.

Get it: $49 one-time

One-off payment via Gumroad. Demo mode runs locally with no Supabase or Stripe account. Prices exclude VAT; UK and EU VAT is added at Gumroad checkout.

Paid MCP Starter: A remote MCP server with API keys, a free tier, Stripe usage-based billing, rate limits, and a usage dashboard on Next.js + Supabase.

Make a tool paid in one line

paid(deps, "my_tool", units, handler)

Why it's worth $49

Can't double-bill. Stripe Billing Meters use an idempotent identifier per call, and a cron resends usage if Stripe has an outage.
Free tier built in. A monthly quota, then an upgrade link appears in the tool result.
Serverless-friendly. A stateless Streamable HTTP endpoint on the official TypeScript SDK v2. It speaks the 2026-07-28 spec and still serves 2025-era clients.
Hardened by default. Raw-body webhook signature checks, de-duplicated events, per-user atomic Postgres rate limits with 429 + Retry-After, and RLS on every table.

What's inside

Full Next.js 16 template + Supabase migration
API key dashboard (keys are hashed and checked on every request; standard 401 challenges)
Stripe Checkout, Customer Portal, metered billing, usage-resend cron
Dashboard: plan, usage meter, usage by tool, keys, billing
CLAUDE.md rules, an /add-mcp-tool skill, and a /launch-checklist skill
Client configs for Claude Code, Cursor, and Claude Desktop
Docs: setup, Stripe, clients, auth, architecture, self-audit
Single-developer commercial licence: build and sell unlimited products, but don't resell the template

Discoverable

An MCP Server Card (SEP-2127) at /api/mcp/server-card and an AI Catalog at /.well-known/ai-catalog.json, with CORS, ETag and caching. Tests check the card matches the running server.

Proof

42 tests cover the protocol (both spec eras), auth, quotas, metering, outage recovery, rate limits, webhook signatures, SQL/RLS (run on real Postgres as anon and authenticated), and the Server Card / AI Catalog endpoints. next build passes, and a local next start server has connected from Claude Code v2.1.296. It hasn't been run against a live Supabase project or live Stripe calls.

Building it with Claude Code? See Ship-Ready AI Rules v2, and run Launch Audit before you go live.

What this doesn't do

No OAuth. Auth uses API keys, which covers Claude Code, Cursor, and Claude Desktop (via mcp-remote). Claude.ai web connectors need OAuth, and the docs show where to swap it in.
Not tested against live services. Everything is tested except a live Supabase project and live Stripe calls. Run the launch checklist in Stripe test mode first.

Not affiliated with Anthropic, Supabase, Stripe, or Vercel.

Price

MCP STARTER

Paid MCP Starter

Charge for your MCP server.

$49

one-off

Remote MCP server on SDK v2 (spec 2026-07-28)
API keys, free monthly quota, rate limits
Stripe metered billing, Checkout, Customer Portal
Usage dashboard; /add-mcp-tool and /launch-checklist skills
MCP Server Card (SEP-2127) at /api/mcp/server-card
42 tests; demo mode with no accounts

Get Paid MCP Starter

Sold via Gumroad (merchant of record)

Ship the tool. The billing's done.

Get Paid MCP Starter: $49 one-time

FAQ

How does billing work?: Each paid tool call sends a Stripe Billing Meter event with an idempotent identifier, so retries can't double-bill. Users get a free monthly quota, then an upgrade link in the tool result, with Stripe Checkout and the Customer Portal for subscriptions. A cron re-sends usage if Stripe calls fail.
Which MCP clients does it work with?: Claude Code, Cursor and Claude Desktop (via mcp-remote), using API keys. Claude.ai web connectors need OAuth, which is not included; the docs show where to swap it in.
Can I try it without Stripe or Supabase accounts?: Yes. Demo mode runs locally with one command and needs no Supabase or Stripe accounts.
What has been tested?: 42 tests cover protocol (both spec eras), auth, quotas, metering, outage recovery, rate limits, webhook signatures, SQL/RLS and the Server Card / AI Catalog endpoints, and next build passes. A live Supabase project and live Stripe calls have not been tested, so run the launch checklist in Stripe test mode first.
Can I sell products built with it?: Yes. The single-developer commercial licence lets you build and sell unlimited products. You can't resell the template itself.