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