build_lead_list — MisarReach MCP Server MCP Prompt
build_lead_list
is one of 5 prompts on the
MisarReach MCP Server
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke build_lead_list from your client
- Claude Code MisarReach MCP Server Prompt/build_lead_list run in your project directory
- Claude Desktop MisarReach MCP Server Prompt/build_lead_list ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MisarReach MCP Server Prompt/build_lead_list ~/.cursor/mcp.json
- VS Code MisarReach MCP Server Prompt/build_lead_list .vscode/mcp.json
- Zed MisarReach MCP Server Prompt/build_lead_list ~/.config/zed/settings.json
- Windsurf MisarReach MCP Server Prompt/build_lead_list ~/.codeium/windsurf/mcp_config.json
- Cline MisarReach MCP Server Prompt/build_lead_list ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MisarReach MCP Server Prompt/build_lead_list ~/.gemini/settings.json
- Grok MisarReach MCP Server Prompt/build_lead_list .mcp.json (in your project root)
- ChatGPT MisarReach MCP Server Prompt/build_lead_list Settings → Connectors → Advanced → Developer mode
- Claude.ai MisarReach MCP Server Prompt/build_lead_list Settings → Connectors → Add custom connector
- LangChain MisarReach MCP Server Prompt/build_lead_list pip install langchain-mcp-adapters
Other prompts on this server
MisarReach MCP Server also offers 4 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.