Claude Desktop Vision Driven Design (VDD) MCP Server Prompt/implement_next_task
How to: Claude Desktop Vision Driven Design (VDD) MCP Server implement_next_task
Add Vision Driven Design (VDD) MCP Server to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"vision-driven-design": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://vdd.simonmak.com/api/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
implement_next_task is surfaced in the attachment menu, under the server's name. Unlike a tool, you invoke it deliberately — Claude Desktop will not call it for you.
-
04
If it does not appear, check that Vision Driven Design (VDD) MCP Server is connected and that you are looking at its prompts rather than its tools.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Same prompt, other clients
Read from the server itself, by connecting to it and calling prompts/list on 3 October 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.