build_feature — Duck Framework MCP MCP Prompt
build_feature
is one of 1 prompt on the
Duck Framework MCP
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke build_feature from your client
- Claude Code Duck Framework MCP Prompt/build_feature run in your project directory
- Claude Desktop Duck Framework MCP Prompt/build_feature ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Duck Framework MCP Prompt/build_feature ~/.cursor/mcp.json
- VS Code Duck Framework MCP Prompt/build_feature .vscode/mcp.json
- Zed Duck Framework MCP Prompt/build_feature ~/.config/zed/settings.json
- Windsurf Duck Framework MCP Prompt/build_feature ~/.codeium/windsurf/mcp_config.json
- Cline Duck Framework MCP Prompt/build_feature ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Duck Framework MCP Prompt/build_feature ~/.gemini/settings.json
- Grok Duck Framework MCP Prompt/build_feature .mcp.json (in your project root)
- ChatGPT Duck Framework MCP Prompt/build_feature Settings → Connectors → Advanced → Developer mode
- Claude.ai Duck Framework MCP Prompt/build_feature Settings → Connectors → Add custom connector
- LangChain Duck Framework MCP Prompt/build_feature pip install langchain-mcp-adapters
Duck Framework MCP also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 5 November 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.