Why use ATXP for MCP servers?
- Earn per-use: Charge per tool call with flexible pricing.
- Programmatic enforcement: Require payment before execution with a single router and helper.
- No user accounts or API keys: Agents pay from their own wallets; you don’t manage users, keys, or invoices.
- Works everywhere: Compatible with major hosts (e.g., Claude, Goose), local dev, and your own infrastructure.
Build your first monetized MCP server
Install the library
Install the ATXP express SDK in your project:
Set up your wallet
Create an ATXP account and set your wallet address in an environment variable. The best way to do this is to create a
.env file in the root of your project and add the following line:.env
Add payment requirements to tools
In each MCP tool exposed by your server that you want to charge per-use for, require payment before tool execution:
Resources
Account Portal
Log in to manage your ATXP account, configure your wallet, and view earnings.
Monetized MCP tutorial
Follow a complete tutorial to build your first paid MCP server with ATXP integration, from initial setup to live deployment.
Build an agent using paid MCP servers
Get started building an ATXP‑powered agent that pays for MCP server tool calls.