Add to ChromeConnect Retriever through MCP
Add Retriever to your AI agent and complete the connection. The setup guide covers the current configuration for Codex, Claude, and other MCP clients.
LINKEDIN / CODEX / CLAUDE
Send LinkedIn outreach from your AI agent.
Tell Codex, Claude, or another MCP-compatible agent who to reach and what to say. Retriever AI handles connection requests, DMs, and InMail in Sales Navigator through your browser.
Free, powered by ads. See plans.
BEFORE YOU START
Bring your list and your message.
Have your LinkedIn session open, your recipient list ready, and the message you want to send. The same MCP connection can help with other tasks on the websites you use.
Your message, delivered from your account.
- Connection requests for the people you choose
- DMs and Sales Navigator InMail
- A record of what was sent and what needs attention
Choose the people and the message
Open LinkedIn in the Chrome profile you use. Give your agent profile links, the action to take, and your message. Use Sales Navigator for the InMail workflow shown in the demo.
Run it and check the result
Start with a short list. Check the sent requests and messages in LinkedIn, then use the returned status to see who still needs attention.
COPY A START
Use a prompt. Make it yours.
Replace the examples with your pages, rules, and approval point. rtrvr will work from the request you give it.
Use Retriever to open these LinkedIn profiles: [profile URLs]. For people I’m not connected to, send a connection request with this note: [your note]. Skip pending requests and existing connections. Return each profile URL and the result. If LinkedIn blocks an action or a field needs information I haven’t supplied, stop and tell me.
Use Retriever to send a message to these people in Sales Navigator: [profile URLs]. Subject: [subject]. Message: [your message]. Use InMail where available. Do not send a second message to anyone already contacted in this task. Return the profile, message type, and confirmed result for each person. Flag unavailable actions instead of retrying them repeatedly.
THE RECORDING
See the actual run.
The November 2 recording shows connection requests, direct messages, Sales Navigator InMail, and the MCP connection from an AI agent.
LinkedIn outreach from Codex or Claude
Connection requests, DMs, and Sales Navigator InMail through Retriever’s MCP connection.
A few useful details.
Do I have to use Codex or Claude?
No. The recording uses an MCP connection. You can connect Retriever to another MCP-compatible agent, or give the task directly to Retriever AI in Chrome.
Are a connection request, a DM, and InMail the same thing?
No. A connection request invites someone to connect. A DM sends a message where LinkedIn makes messaging available. InMail is a separate messaging option; its availability and credits depend on your LinkedIn account. Tell Retriever which action you want.
Can I check the messages before sending?
Yes. Change the prompt to ask for drafts and a pause before sending. When you are ready, give the agent explicit instructions about which messages to send.