create_invoice — SnapEX Pay MCP Tool Mutating
create_invoice
(create invoice) 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 create_invoice from your client
- Claude Code SnapEX Pay create_invoice run in your project directory
- Claude Desktop SnapEX Pay create_invoice ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SnapEX Pay create_invoice ~/.cursor/mcp.json
- VS Code SnapEX Pay create_invoice .vscode/mcp.json
- Zed SnapEX Pay create_invoice ~/.config/zed/settings.json
- Windsurf SnapEX Pay create_invoice ~/.codeium/windsurf/mcp_config.json
- Cline SnapEX Pay create_invoice ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SnapEX Pay create_invoice ~/.gemini/settings.json
- Grok SnapEX Pay create_invoice .mcp.json (in your project root)
- ChatGPT SnapEX Pay create_invoice Settings → Connectors → Advanced → Developer mode
- Claude.ai SnapEX Pay create_invoice Settings → Connectors → Add custom connector
- LangChain SnapEX Pay create_invoice 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
- get_invoice
- list_invoices
- get_invoice_payment_methods
- select_invoice_payment_method
- preview_payment
- create_payment
- get_payment
- list_payments
- 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.