Q402 Mcp
Prototype gasless EVM payments and CCIP bridging from your agent with Q402 sandbox-first tooling before wiring paid multichain keys.
Overview
Q402 MCP is a MCP server for the Build phase that enables gasless EVM payments and CCIP bridging across 10 chains from AI agents with sandbox-first API keys.
What is this MCP server?
- Gasless payments on 10 EVM chains plus CCIP bridge paths (eth/avax/arbitrum noted)
- Sandbox-default workflow with q402_doctor storing secrets in ~/.q402/mcp.env
- Q402_TRIAL_API_KEY: BNB Chain only, 2,000 sponsored transactions, gas covered by Q402
- Q402_MULTICHAIN_API_KEY for paid multichain coverage from q402.quackai.ai/payment
- npm @quackai/q402-mcp v0.8.9 stdio; tools include q402_pay and q402_batch_pay (up to 5 recipients)
- 10 EVM chains for gasless payments per description
- 2,000 sponsored transactions on free trial API key (BNB Chain only)
- q402_batch_pay supports up to 5 recipients per environment documentation
What problem does it solve?
Adding crypto payments to an agent product usually blocks on gas funding, chain-specific SDKs, and messy secret setup.
Who is it for?
Indie builders prototyping agent-native payments on EVM who want sponsored trial transactions before buying multichain API access.
Skip if: Products with no on-chain payments, or teams that cannot accept wallet/API key custody in local mcp.env files.
What do I get? / Deliverables
After install and q402_doctor setup, your agent can call Q402 pay and bridge tools with trial-sponsored gas on BNB or paid multichain keys for broader rollout.
- Working q402_pay or q402_batch_pay calls from your agent in sandbox/trial mode
- Documented path from trial BNB sponsorship to paid multichain API key
- CCIP bridge experimentation on noted eth/avax/arbitrum routes where applicable
Recommended MCP Servers
Journey fit
Payment rails are integrated during build when your agent product needs callable pay and bridge tools, not only at launch marketing. Integrations covers MCP payment, batch pay, and cross-chain bridge tools that hook your app to Q402 infrastructure.
How it compares
Gasless payment and bridge MCP, not a token deployment or market-data catalog server.
Common Questions / FAQ
Who is Q402 MCP for?
Q402 MCP is for developers shipping AI agents that need gasless EVM payments and optional CCIP bridging without writing custom relayer code first.
When should I use Q402 MCP?
Use it during build and prototype validation when you need q402_pay or batch pay flows on supported chains, starting with the BNB trial key before multichain production keys.
How do I add Q402 MCP to my agent?
Install @quackai/q402-mcp via stdio in your MCP client, run q402_doctor to store Q402_TRIAL_API_KEY or Q402_MULTICHAIN_API_KEY in ~/.q402/mcp.env, then register the server for Claude Code, Cursor, or compatible hosts.