signal_leads_results — Signal Leads MCP Tool
signal_leads_results
(signal leads results) is one of 3 tools on the
Signal Leads
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call signal_leads_results from your client
- Claude Code Signal Leads signal_leads_results run in your project directory
- Claude Desktop Signal Leads signal_leads_results ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Signal Leads signal_leads_results ~/.cursor/mcp.json
- VS Code Signal Leads signal_leads_results .vscode/mcp.json
- Zed Signal Leads signal_leads_results ~/.config/zed/settings.json
- Windsurf Signal Leads signal_leads_results ~/.codeium/windsurf/mcp_config.json
- Cline Signal Leads signal_leads_results ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Signal Leads signal_leads_results ~/.gemini/settings.json
- Grok Signal Leads signal_leads_results .mcp.json (in your project root)
- ChatGPT Signal Leads signal_leads_results Settings → Connectors → Advanced → Developer mode
- Claude.ai Signal Leads signal_leads_results Settings → Connectors → Add custom connector
- LangChain Signal Leads signal_leads_results pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http leads https://leads.cloudforbots.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 15 October 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.