Home / Use cases / mcp-server-payments

Payments for an MCP server — the missing piece of the spec

The problem

The MCP spec defines tools, prompts, and resources — but no payment primitive. Every MCP author re-invents billing badly, or skips it entirely.

What Spawnpay does

Spawnpay is a per-call USDC wrapper that drops into any MCP tool with two lines. Works in stdio, SSE, and HTTP transports. No spec change required on the client. The agent already authed to MCP — Spawnpay just adds money.

Code

// In your MCP server's tool handler
import { paywall } from 'spawnpay-paywall';

server.tool('my_tool', /* ... */, paywall(
  { price: 0.002, vendor: 'SP_yourCode' },
  async ({ args }) => runTool(args)
));
60-SEC QUICKSTART → PLAYGROUND → TOP UP USDC →

What you get with $7 free credit

Every new spk_ wallet starts with $7. That covers 7,000 proxy calls, 1,400 cloud-scrapes, or 700 screenshots — enough to verify Spawnpay fits your workflow before topping up.

See also