What ChatGPT can do through Linkydy
- Search leads by prompt — use search_leads for keyword/title text search or search_by_url for exact filters from a standard LinkedIn people-search URL.
- Save and manage a pipeline — matches go into the Linkydy CRM with name, title, company, and profile URL; ChatGPT can list and review them later.
- Find a work email — call find_email for one profile URL; your Apollo.io API key must be configured in the extension.
- Run outreach — send one connection request with {{FIRST_NAME}}, {{LAST_NAME}}, {{POSITION}}, and {{COMPANY}} placeholders, or warm a prospect with a reaction or comment.
- Monitor results — ask for sent, accepted, pending, acceptance rate, and today's invite count.
The division of labor: ChatGPT plans and calls tools; Linkydy executes in your browser. The extension auto-pauses on LinkedIn's own invite-limit or rate-limit response, while ChatGPT should use get_safety_status to pace sends.
Before you start: how ChatGPT connects
Setup steps
- Install Node.js 18+, then install Linkydy, sign in, and keep Chrome open.
- Open Linkydy dashboard → AI Agent (MCP) → copy the private pairing token. Premium unlocks the token and On switch.
- In ChatGPT Desktop open Settings → Connectors → Advanced / Developer mode → Add MCP server, then enter:
Command: npx Arguments: -y linkydy-mcp Environment variable: LINKYDY_TOKEN = PASTE_YOUR_TOKEN_HERE
- Save the server. ChatGPT launches linkydy-mcp locally; it opens a loopback WebSocket on 127.0.0.1:8765 for the Chrome extension.
- Toggle the connection On in Linkydy. When the status dot turns green, ask ChatGPT to call get_account.
If your ChatGPT surface does not expose a local command form and only accepts an HTTPS URL, that surface needs a separate stdio-to-HTTPS MCP bridge. The Claude and Cursor setups launch the local server directly.
Example prompts
Safety and pacing
ChatGPT never sees your LinkedIn password or session cookie. Actions run in your own Chrome session, from your own IP, while the browser and MCP connection are on. The MCP implementation has no artificial daily cap: get_safety_status reports today's invite count so ChatGPT can self-pace, and the extension auto-pauses if LinkedIn returns an invite-limit (415) or rate-limit (429) signal. Avoid burst sending and review write actions in ChatGPT.
MCP access requires Linkydy Premium. Free accounts get an explicit premium_required response — no silent failures, no surprise charges. More on the overall risk model: Is LinkedIn automation safe?
Linkydy