HeyLead — Autonomous LinkedIn SDR

# HeyLead > MCP-native autonomous LinkedIn SDR — AI-powered lead generation, voice-matched cold outreach, multi-touch drip sequences, and campaign analytics inside Cursor, Claude Code, or any MCP client. HeyLead gives AI agents 31 tools covering the full SDR workflow: prospect discovery, ICP generation with buyer personas, personalized connection invitations, follow-up DMs, engagement warm-ups (comments, likes, follows, endorsements), reply handling with sentiment classification, outcome tracking, and 24/7 autonomous scheduling. Install: `pip install heylead` or `claude mcp add heylead -- uvx heylead` No dashboard. No web app. Just chat with your AI. ## Documentation - [README](https://github.com/D4umak/heylead/blob/main/README.md): Installation, getting started, 31-tool reference, pricing, troubleshooting - [Agent Integration Guide](https://github.com/D4umak/heylead/blob/main/AGENTS.md): Complete tool reference for AI agents with workflow, auth, and capabilities - [Full Documentation](https://github.com/D4umak/heylead/blob/main/llms-full.txt): Comprehensive single-file documentation for AI agents - [PyPI Package](https://pypi.org/project/heylead/): Published package with version history ## API Reference - [MCP Discovery](https://heylead.dev/.well-known/mcp.json): Machine-readable MCP capabilities endpoint - [MCP Registry Manifest](https://github.com/D4umak/heylead/blob/main/server.json): Server manifest with transport config ## Optional - [MCP Registry](https://registry.modelcontextprotocol.io): Official MCP server registry - [Smithery](https://smithery.ai): Smithery AI registry listing - [GitHub Issues](https://github.com/D4umak/heylead/issues): Bug reports and feature requests

{"openapi":"3.1.0","info":{"title":"HeyLead API","version":"0.1.0"},"paths":{"/auth/login-url":{"get":{"tags":["auth"],"summary":"Login Url","description":"Redirect to Google OAuth consent page (or return URL as JSON with ?redirect=false).\n\nIf redirect_uri is provided (e.g., from the dashboard), it is passed through\nas OAuth 'state' and used after callback to redirect with the JWT token.","operationId":"login_url_auth_login_url_get","parameters":[{"name":"redirect","in":"query","required":fal