mcpField
S
Snap Protocol

Snap Protocol

Local
agentzeny.aiFinance0Updated 21w ago
RepositoryVisit website

About Snap Protocol

Snap Protocol is an MCP server for private payments on Solana, with tools to list pools, deposit, withdraw, and estimate fees. It uses stdio transport and includes helpers for compatibility with existing local flows.

Key features

  1. 01List SNAP pools
  2. 02Deposit and withdraw funds
  3. 03Estimate transaction fees
  4. 04Provide helpers for local-flow compatibility

Use cases

  1. 01Check available SNAP pools
  2. 02Initiate deposits or withdrawals through MCP
  3. 03Estimate fees before a transaction

MCP support

Exposes pool listing, deposit, withdrawal, and fee-estimation tools to MCP clients over stdio, alongside compatibility helpers.

#solana#privacy#zk-proofs#payments#blockchain

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "agentzeny": {
      "command": "npx",
      "args": [
        "-y",
        "snap-mcp-server"
      ],
      "env": {
        "SNAP_RPC_URL": "<SNAP_RPC_URL>",
        "SNAP_POOL_ADDRESS": "<SNAP_POOL_ADDRESS>",
        "SNAP_RELAYER_URL": "<SNAP_RELAYER_URL>"
      }
    }
  }
}
Run commandnpx -y snap-mcp-server
Environment variables to set
SNAP_RPC_URLSolana RPC endpoint URL
SNAP_POOL_ADDRESSDefault shielded pool address
SNAP_RELAYER_URLOptional relayer URL for private withdrawals

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmsnap-mcp-server0.1.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

SNAP MCP Server

MCP server for SNAP private payments. It targets @modelcontextprotocol/sdk 1.28.0 and uses stdio transport.

Tools

  • snap_list_pools
  • snap_deposit
  • snap_withdraw
  • snap_estimate_fee

The server also keeps snap_withdraw_private, snap_pool_info, and snap_balance as compatibility helpers for existing local flows.

Claude Code Config

{
  "mcpServers": {
    "snap": {
      "command": "npx",
      "args": ["tsx", "/path/to/agent-privacy-pool/integrations/mcp/snap-mcp-server.ts"],
      "env": {
        "SNAP_RPC_URL": "https://api.mainnet-beta.solana.com",
        "SNAP_POOL_ADDRESS": "B8SyffZKt8LABKogWjH9rZcjY5PV2hyYRCbTxxbcrpFf",
        "SNAP_RELAYER_URL": "https://your-relayer.example"
      }
    }
  }
}

For deterministic local transport tests, set SNAP_MCP_STUB_MODE=1.

Environment

Start from integrations/mcp/.env.example:

  • SNAP_RPC_URL
  • SNAP_POOL_ADDRESS
  • SNAP_RELAYER_URL
  • SNAP_MCP_NOTE
  • SNAP_MCP_VIEWING_KEY_JSON
  • SNAP_MCP_STUB_MODE

SNAP_MCP_NOTE should be a serialized note returned by SNAPClient.serializeNote(...).

Mainnet Pools

  • 0.1 SOL: B8SyffZKt8LABKogWjH9rZcjY5PV2hyYRCbTxxbcrpFf
  • 1 USDC: 5LeuHrPBgHNhgbCy996MEjcsBk5gNHhVj6AiuuCHZ8od
  • 10 USDC: ECuHf8kgiWfmL3Q6id4WGBQWvuukhzqvF5vsxuPAKZBv

Run

cd /path/to/agent-privacy-pool
set -a
source integrations/mcp/.env.example
set +a
npx tsx integrations/mcp/snap-mcp-server.ts

Smoke test:

npx mocha --require tsx integrations/tests/mcp-stdio.test.ts

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.