mcpField
X
x402 MCP Starter

x402 MCP Starter

Remote
github.com/kadopiDeveloper Tools
Repository

About x402 MCP Starter

x402 MCP Starter is a self-hosted Cloudflare Workers starter for adding USDC usage billing to an MCP server, aimed at developers deploying their own service. It includes configuration validation, a fixed-price sample tool, and payment-retry records; its public endpoint is for Base Sepolia testing only.

Key features

  1. 01Adds USDC billing to MCP tools
  2. 02Validates network, price, and recipient settings
  3. 03Demonstrates a fixed-price payment flow
  4. 04Records payment proofs and tool results
  5. 05Uses D1 for retry handling

Use cases

  1. 01Deploy paid MCP tools on Cloudflare Workers
  2. 02Check Base USDC payment settings before deployment
  3. 03Test a client payment round trip on Base Sepolia
  4. 04Retry the same payment and return its saved result

MCP support

It provides an MCP service over Streamable HTTP with a free configuration validator and a fixed-price paid sample tool. Unpaid calls return payment requirements for an x402-capable client to sign and retry.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://x402-mcp-starter.kadopi.workers.dev/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

2
ParameterTypeRequiredDescription
assetstringYes
payTostringYes
amountstringYes
networkenumYeseip155:84532 | eip155:8453
priceUsdnumberYes
facilitatorUrlstringYes

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.