build_workflows — docs mcp MCP Prompt

build_workflows is one of 3 prompts on the docs mcp MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke build_workflows from your client

• Claude Code docs mcp Prompt/build_workflows run in your project directory
• Claude Desktop docs mcp Prompt/build_workflows ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor docs mcp Prompt/build_workflows ~/.cursor/mcp.json
• VS Code docs mcp Prompt/build_workflows .vscode/mcp.json
• Zed docs mcp Prompt/build_workflows ~/.config/zed/settings.json
• Windsurf docs mcp Prompt/build_workflows ~/.codeium/windsurf/mcp_config.json
• Cline docs mcp Prompt/build_workflows ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI docs mcp Prompt/build_workflows ~/.gemini/settings.json
• Grok docs mcp Prompt/build_workflows .mcp.json (in your project root)
• ChatGPT docs mcp Prompt/build_workflows Settings → Connectors → Advanced → Developer mode
• Claude.ai docs mcp Prompt/build_workflows Settings → Connectors → Add custom connector
• LangChain docs mcp Prompt/build_workflows pip install langchain-mcp-adapters

Other prompts on this server

• install_tandem_engine
• use_python_sdk

docs mcp also offers 49 resources — 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 24 September 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.