list_deals — Clickwise Affiliate Network MCP Tool Read-only
list_deals
(list deals) is one of 20 tools on the
Clickwise Affiliate Network
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_deals from your client
- Claude Code Clickwise Affiliate Network list_deals run in your project directory
- Claude Desktop Clickwise Affiliate Network list_deals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Clickwise Affiliate Network list_deals ~/.cursor/mcp.json
- VS Code Clickwise Affiliate Network list_deals .vscode/mcp.json
- Zed Clickwise Affiliate Network list_deals ~/.config/zed/settings.json
- Windsurf Clickwise Affiliate Network list_deals ~/.codeium/windsurf/mcp_config.json
- Cline Clickwise Affiliate Network list_deals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Clickwise Affiliate Network list_deals ~/.gemini/settings.json
- Grok Clickwise Affiliate Network list_deals .mcp.json (in your project root)
- ChatGPT Clickwise Affiliate Network list_deals Settings → Connectors → Advanced → Developer mode
- Claude.ai Clickwise Affiliate Network list_deals Settings → Connectors → Add custom connector
- LangChain Clickwise Affiliate Network list_deals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://partners.clickwise.net/api/v1/mcp
Other tools on this server
- search_products
- get_product_feed
- get_catalog_stats
- get_deal
- list_news
- get_news
- find_affiliate_programs
- request_tracked_links
- get_monetization_feed
- get_tracked_link_request
- request_merchant_onboarding
- list_programs
- update_profile
- list_my_programs
- create_tracking_links
- get_performance_report
- list_conversions
- get_payment_status
- apply_to_program
This list was read from the server itself, by connecting to it and calling tools/list on 6 October 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.