find_leads_from_signals — linkedin buying signals MCP Tool Read-only
find_leads_from_signals
(find leads from signals) is one of 15 tools on the
linkedin buying signals
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_leads_from_signals from your client
- Claude Code linkedin buying signals find_leads_from_signals run in your project directory
- Claude Desktop linkedin buying signals find_leads_from_signals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor linkedin buying signals find_leads_from_signals ~/.cursor/mcp.json
- VS Code linkedin buying signals find_leads_from_signals .vscode/mcp.json
- Zed linkedin buying signals find_leads_from_signals ~/.config/zed/settings.json
- Windsurf linkedin buying signals find_leads_from_signals ~/.codeium/windsurf/mcp_config.json
- Cline linkedin buying signals find_leads_from_signals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI linkedin buying signals find_leads_from_signals ~/.gemini/settings.json
- Grok linkedin buying signals find_leads_from_signals .mcp.json (in your project root)
- ChatGPT linkedin buying signals find_leads_from_signals Settings → Connectors → Advanced → Developer mode
- Claude.ai linkedin buying signals find_leads_from_signals Settings → Connectors → Add custom connector
- LangChain linkedin buying signals find_leads_from_signals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http linkedin-buying-signals https://www.getcleed.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.