MCP Server with x402
Last updated
Last updated
is a protocol for passing context between LLMs and other AI agents. This page shows how to use the x402 payment protocol with MCP to make paid API requests through an MCP server, and how to connect it to Claude Desktop.
This guide walks you through running an MCP server that can access paid APIs using the x402 protocol. The MCP server acts as a bridge between Claude Desktop (or any MCP-compatible client) and a paid API (such as the sample weather API in the x402 repo). When Claude (or another agent) calls a tool, the MCP server will:
Detect if the API requires payment (via HTTP 402)
Automatically handle the payment using your wallet
Return the paid data to the client (e.g., Claude)
This lets you (or your agent) access paid APIs programmatically, with no manual payment steps.
Node.js (v20 or higher)
An x402-compatible server to connect to (for this demo, we'll use the from the x402 repo, or any external x402 API)
An Ethereum wallet with USDC (on Base Sepolia or Base Mainnet)
You can find a ready-to-use version of this code in the . Below, we explain each step so you understand how it works and can adapt it to your needs.
Create a .env
file in your project root:
PRIVATE_KEY
: Your EVM wallet's private key (for signing payments)
RESOURCE_SERVER_URL
: The base URL of the paid API (use the sample express server for this demo)
ENDPOINT_PATH
: The specific endpoint path (e.g., /weather
)
How it works
The MCP server exposes a tool that, when called, fetches data from a paid API endpoint.
If the endpoint requires payment, the x402-axios interceptor handles the payment handshake using your wallet.
Once payment is complete, the data is returned to the MCP client (e.g., Claude Desktop).
To use this integration with Claude Desktop:
Open Claude Desktop and go to MCP settings.
Add a new MCP server with the following config (adjust paths as needed):
Make sure your x402-compatible server (e.g., the sample express server) is running and accessible at the URL you provided.
Start the MCP client (e.g., with pnpm dev
in the client directory).
Claude can now call the tool and receive paid data!
x402-compatible server: Hosts the paid API (e.g., weather data). Responds with HTTP 402 if payment is required.
MCP server (this implementation): Acts as a bridge, handling payment and exposing tools to MCP clients.
Claude Desktop: Calls the MCP tool, receives the paid data, and displays it to the user.
Try integrating with your own x402-compatible APIs
Extend the MCP server with more tools or custom logic as needed