get_next_best_action — Dealwize MCP Tool Read-only
get_next_best_action
(get next best action) is one of 14 tools on the
Dealwize
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_next_best_action from your client
- Claude Code Dealwize get_next_best_action run in your project directory
- Claude Desktop Dealwize get_next_best_action ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Dealwize get_next_best_action ~/.cursor/mcp.json
- VS Code Dealwize get_next_best_action .vscode/mcp.json
- Zed Dealwize get_next_best_action ~/.config/zed/settings.json
- Windsurf Dealwize get_next_best_action ~/.codeium/windsurf/mcp_config.json
- Cline Dealwize get_next_best_action ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Dealwize get_next_best_action ~/.gemini/settings.json
- Grok Dealwize get_next_best_action .mcp.json (in your project root)
- ChatGPT Dealwize get_next_best_action Settings → Connectors → Advanced → Developer mode
- Claude.ai Dealwize get_next_best_action Settings → Connectors → Add custom connector
- LangChain Dealwize get_next_best_action pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dealwize https://api.dealwize.co/api/v1/mcpOther tools on this server
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.