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