generate_mutual_action_plan — Dealwize MCP Tool
generate_mutual_action_plan
(generate mutual action plan) 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 generate_mutual_action_plan from your client
- Claude Code Dealwize generate_mutual_action_plan run in your project directory
- Claude Desktop Dealwize generate_mutual_action_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Dealwize generate_mutual_action_plan ~/.cursor/mcp.json
- VS Code Dealwize generate_mutual_action_plan .vscode/mcp.json
- Zed Dealwize generate_mutual_action_plan ~/.config/zed/settings.json
- Windsurf Dealwize generate_mutual_action_plan ~/.codeium/windsurf/mcp_config.json
- Cline Dealwize generate_mutual_action_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Dealwize generate_mutual_action_plan ~/.gemini/settings.json
- Grok Dealwize generate_mutual_action_plan .mcp.json (in your project root)
- ChatGPT Dealwize generate_mutual_action_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai Dealwize generate_mutual_action_plan Settings → Connectors → Add custom connector
- LangChain Dealwize generate_mutual_action_plan 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.