list_payments — SnapEX Pay MCP Tool Read-only
list_payments
(list payments) is one of 32 tools on the
SnapEX Pay
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_payments from your client
- Claude Code SnapEX Pay list_payments run in your project directory
- Claude Desktop SnapEX Pay list_payments ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SnapEX Pay list_payments ~/.cursor/mcp.json
- VS Code SnapEX Pay list_payments .vscode/mcp.json
- Zed SnapEX Pay list_payments ~/.config/zed/settings.json
- Windsurf SnapEX Pay list_payments ~/.codeium/windsurf/mcp_config.json
- Cline SnapEX Pay list_payments ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SnapEX Pay list_payments ~/.gemini/settings.json
- Grok SnapEX Pay list_payments .mcp.json (in your project root)
- ChatGPT SnapEX Pay list_payments Settings → Connectors → Advanced → Developer mode
- Claude.ai SnapEX Pay list_payments Settings → Connectors → Add custom connector
- LangChain SnapEX Pay list_payments pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http pay https://pay.snapex.pro/mcp
Other tools on this server
- create_account
- get_account
- list_assets
- get_fiat_rates
- get_fees
- list_static_address_networks
- get_balances
- list_transactions
- create_invoice
- get_invoice
- list_invoices
- get_invoice_payment_methods
- select_invoice_payment_method
- preview_payment
- create_payment
- get_payment
- create_static_address
- list_static_addresses
- list_static_address_deposits
- preview_payout
- create_payout
- get_payout
- list_payouts
- preview_conversion
- create_conversion
- get_conversion
- list_conversions
- list_webhooks
- create_webhook
- update_webhook
- rotate_webhook_secret
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.