build_icp_list — Getlead MCP Prompt

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

by client

How to invoke build_icp_list from your client

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

Other prompts on this server

• plan_outbound_campaign
• triage_inbox

Getlead also offers 2 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 26 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.