resume_payment — Vaanzari Commerce MCP Tool
resume_payment
(resume payment) is one of 29 tools on the
Vaanzari Commerce
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resume_payment from your client
- Claude Code Vaanzari Commerce resume_payment run in your project directory
- Claude Desktop Vaanzari Commerce resume_payment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vaanzari Commerce resume_payment ~/.cursor/mcp.json
- VS Code Vaanzari Commerce resume_payment .vscode/mcp.json
- Zed Vaanzari Commerce resume_payment ~/.config/zed/settings.json
- Windsurf Vaanzari Commerce resume_payment ~/.codeium/windsurf/mcp_config.json
- Cline Vaanzari Commerce resume_payment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vaanzari Commerce resume_payment ~/.gemini/settings.json
- Grok Vaanzari Commerce resume_payment .mcp.json (in your project root)
- ChatGPT Vaanzari Commerce resume_payment Settings → Connectors → Advanced → Developer mode
- Claude.ai Vaanzari Commerce resume_payment Settings → Connectors → Add custom connector
- LangChain Vaanzari Commerce resume_payment pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http commerce https://vaanzari.com/mcp
Other tools on this server
- search_sarees
- get_saree
- list_artisans
- get_artisan
- get_account
- update_profile
- get_cart
- add_to_cart
- set_cart_quantity
- remove_from_cart
- get_picks
- save_pick
- remove_pick
- get_rewards
- get_checkout_summary
- validate_coupon
- start_checkout
- list_orders
- get_order
- cancel_order
- get_payment_status
- retry_payment
- cancel_payment_attempt
- list_support_tickets
- get_support_ticket
- create_support_ticket
- reply_support_ticket
- close_support_ticket
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.