Munition
Wire Claude Code or another MCP client to x402-paid Munition services (starting with Upload) using an agent-funded USDC wallet instead of a traditional API billing account.
Overview
Munition is a MCP server for the Build phase that connects AI agents to x402 USDC-paid Munition services such as Upload via stdio MCP.
What is this MCP server?
- stdio MCP package @munition/mcp (v0.0.9) pointing at configurable MUNITION_API_URL (default https://api.munition.io)
- x402-paid service wrapper so agents invoke Munition capabilities only after USDC settlement
- Anonymous USDC wallet funding model aimed at agents without tying every call to a human billing login
- Documented live service surface today: Upload (additional services implied by “wrapper” positioning)
- npm registry transport for drop-in Claude Desktop / Claude Code MCP config
- Server schema version 0.0.9; npm identifier @munition/mcp
- Default API origin https://api.munition.io via MUNITION_API_URL
- Catalog lists one named service today: Upload
What problem does it solve?
Agents can write code to upload or buy metered services but lack a simple, anonymous way to fund those calls without you manually provisioning billing for every integration.
Who is it for?
Solo builders shipping MCP-enabled agents that must upload assets or call pay-per-use Munition APIs during development.
Skip if: Teams that need enterprise invoicing, fiat-only billing, or upload/CDN features with no crypto or x402 involvement.
What do I get? / Deliverables
After you add @munition/mcp to your client, your agent can call Munition’s Upload (and future x402 services) with USDC-funded requests instead of hand-rolled payment plumbing.
- Registered stdio MCP server exposing Munition tools to your agent
- Agent-callable Upload path against Munition API with x402 USDC settlement
- Reusable pattern for adding future Munition x402-wrapped services in the same MCP install
Recommended MCP Servers
Journey fit
Munition is installed while you are composing the product: it is an MCP bridge that lets coding agents call paid external capabilities during implementation, not a ship-time audit or launch distribution tool. The server exists to extend agent runtimes with micropayment-backed tools; that maps to agent-tooling on the build shelf rather than a single app feature like frontend or backend code alone.
How it compares
MCP payment-rail integration for agents, not a local filesystem or S3 upload skill.
Common Questions / FAQ
Who is Munition for?
Munition is for indie and solo builders running Claude Code, Cursor, or other MCP clients who want agents to use paid Munition services settled with USDC over x402.
When should I use Munition?
Use it during the build phase when your agent workflow needs Upload or other Munition capabilities and you want micropayments instead of wiring a separate billing integration yourself.
How do I add Munition to my agent?
Install the npm package @munition/mcp, configure stdio MCP in your client, set MUNITION_API_URL if you are not using https://api.munition.io, and fund the anonymous USDC wallet flow Munition documents for x402 calls.