Spawnpay
- Robocular/spawnpay
io.github.Robocular/spawnpay is an MCP server that connects AI agents to Base L2 crypto wallets, payments, and referral earnings via Spawnpay.
About
io.github.Robocular/spawnpay is an MCP server that connects coding agents to Spawnpay’s crypto wallet, payment, and referral APIs on Base L2. Developers shipping agent products—marketplaces, paid tool routers, or referral-driven SaaS—can register this server so Claude Code or Cursor can create wallets, trigger payments, and reason about earnings flows in natural language instead of jumping between docs and scripts. Transport is stdio through the spawnpay-mcp npm package; authentication centres on SPAWNPAY_API_KEY, which the provider notes may be created automatically on first use if unset. Version 0.4.7 is listed in the server manifest. This is a task integration: you still own product economics, security review, and user-facing UX. Treat on-chain money movement as advanced scope and test on Base testnet or small amounts before production. It complements generic Web3 libraries by exposing Spawnpay-specific agent tools rather than replacing your smart-contract layer.
- Crypto wallets and payments for AI agents on Base L2
- Referral earnings surface for agent-native monetisation experiments
- Stdio MCP via npm package spawnpay-mcp (v0.4.7)
- SPAWNPAY_API_KEY with optional auto-provision on first use
- Open-source Robocular/spawnpay repository for inspection
Spawnpay by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env SPAWNPAY_API_KEY=YOUR_SPAWNPAY_API_KEY spawnpay-mcp -- npx -y spawnpay-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | spawnpay-mcp |
|---|---|
| Transport | STDIO |
| Auth | Required |
| Repository | Robocular/spawnpay ↗ |
What it does
Give autonomous agents on Base L2 wallets, crypto payments, and referral earnings without hand-rolling wallet infra in your app.
Who is it for?
Best when you're prototyping agent-native commerce, tips, or referral loops on Base and want MCP-first payment APIs.
Skip if: Traditional fiat-only SaaS, teams avoiding crypto compliance risk, or products that need a full payment UI without agent mediation.
What you get
After MCP registration, your agent can call Spawnpay tools for wallets, payments, and referrals inside your development loop.
- Agent-callable wallet and payment operations on Base L2
- Referral earnings hooks for agent monetisation experiments
- Stdio MCP bridge to Spawnpay APIs during integration work
By the numbers
- Server version 0.4.7
- Transport: stdio via npm identifier spawnpay-mcp
- Chain focus: Base L2
Recommended MCP Servers
$THREE TokenPrice, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token.89
402 McpAI agents discover, pay for, and consume any Lightning-gated API autonomously
9192 Public ComputeRemote MCP for 9192 discovery, pricebook, payment rails, GET_PULSE quotes, and receipt checks.
Aarna McpAarna - 34 tools for swap quotes, liquidity pools, and trading dataAave McpAave - 6 tools for lending rates, supply, and borrow data
AbraFlexiMCP server for AbraFlexi ERP — invoices, contacts, products, bank transactions.1How it compares
Spawnpay-focused crypto payments MCP, not a Stripe skill or a generic Ethereum wallet library.
FAQ
Who is io.github.Robocular/spawnpay for?
Developers building AI agents or agent marketplaces that need Base L2 wallets and payments from Claude Code, Cursor, or Codex.
When should I use io.github.Robocular/spawnpay?
Use it during build integrations when your agent product must send crypto, hold balances, or track referral earnings on Base.
How do I add io.github.Robocular/spawnpay to my agent?
Add the spawnpay-mcp npm stdio server to your MCP config, set SPAWNPAY_API_KEY (or let first-use provisioning create one), then restart your agent client.