SNAP Protocol
Let autonomous agents deposit, withdraw, and move funds on Solana shielded pools without exposing payment metadata on-chain.
Overview
SNAP Protocol is a MCP server for the Build phase that runs private Solana agent payments through ZK shielded pools with deposit, withdraw, pool listing, and fee estimation tools.
What is this MCP server?
- ZK-shielded deposits and withdrawals on Solana via SNAP pools
- List available shielded pools and estimate fees before transacting
- stdio MCP package snap-mcp-server on npm (v0.1.2)
- Required env: SNAP_RPC_URL and SNAP_POOL_ADDRESS; optional SNAP_RELAYER_URL for private withdrawals
- Server version 0.1.2 on npm identifier snap-mcp-server
- 3 documented environment variables (2 required, 1 optional relayer)
What problem does it solve?
On-chain agent payments leak amounts and counterparties, which blocks privacy-sensitive automation and makes fee planning guesswork before you commit SOL.
Who is it for?
Indie builders wiring Solana-based agents that need shielded treasury moves and upfront fee quotes without building ZK plumbing by hand.
Skip if: Teams that only need fiat checkout, EVM-only USDC, or payments with no Solana footprint.
What do I get? / Deliverables
After you register the server, your agent can list SNAP pools, estimate fees, and drive shielded deposit and withdraw flows against your configured RPC and pool.
- Agent-callable deposit and withdraw against configured SNAP pools
- Pool listing and fee estimates before on-chain commits
- Optional relayer-backed private withdrawal path
Recommended MCP Servers
Journey fit
Payment rails and chain RPC wiring belong in Build when you connect agents to real money movement. Integrations is where MCP servers expose external protocols (Solana SNAP, relayers, pool addresses) to your coding agent.
How it compares
Solana ZK payment MCP integration, not a hosted fiat processor or a generic agent skill.
Common Questions / FAQ
Who is SNAP Protocol for?
Solo and indie developers building AI agents on Solana who want shielded deposits, withdrawals, and fee estimates exposed as MCP tools.
When should I use SNAP Protocol?
Use it during Build when you integrate autonomous spend or treasury actions and need SNAP pool discovery plus ZK-private withdraw paths.
How do I add SNAP Protocol to my agent?
Install the npm package snap-mcp-server, set SNAP_RPC_URL and SNAP_POOL_ADDRESS (and SNAP_RELAYER_URL if needed), and register the stdio MCP server in Claude Code, Cursor, or another MCP client.