LinkedIn MCP for Claude

Walk into your next meeting with the relationship history already in hand.

LinkedIn MCP · 29 October 2026

Start the meeting where the last conversation ended

You have a call with someone you first met on LinkedIn. The introduction happened months ago, the conversation moved to email, and the detail you need is somewhere in the middle. A public profile can tell you their title. It cannot tell you what you promised to send.

A LinkedIn MCP workflow with Claude starts with the relationship information available through a connected service. Cold brings the context behind your network into focus, so the brief can reflect how you know the person and what has already happened.

Maya Bennett

Co-founder at Performa AI

Overview

Deal

Recon

Activity

Relationship

Known by

Leo

Nina

Status

Connected

Company

Performa AI

Role

Co-founder

WhatsApp · Nina and Maya

6 June

We worked together at Orbit. Happy to connect you.

Gmail · Leo and Maya

22 May

Great catching up about Performa’s launch last week.

Illustrative relationship record in Cold. Names and conversations are example content.

How Claude uses MCP

Claude supports custom connectors using remote MCP. Once an authorised connection is available, Claude can use the tools that service exposes. The account, workspace and tool permissions determine what it can access.

For Cold, start from the MCP product page and the connection options available to your account. Claude’s general support for connectors is not a promise that every Cold capability is enabled in every Claude surface. Check availability before relying on a workflow.

Build a brief around one person

Choose a specific contact and explain the purpose of the meeting. Ask for the last meaningful interaction, the open questions and any commitments that still need an answer. Keep the brief short enough to read before the call.

Try: ‘Use Cold to prepare me for my meeting with Maya at Performa AI. Explain how we know each other, summarise our latest conversation and list anything I promised to follow up on. Include source references. Then suggest three questions for this meeting.’

The example name is illustrative. Replace it with a contact in your own network and compare the answer with the source conversation before using it.

Separate the facts from the agenda

Ask Claude to organise the brief into relationship history, unresolved commitments and proposed talking points. Those categories make it easier to see which statements come from your records and which are suggestions.

For example, ‘We discussed a pilot in May’ needs support from a conversation. ‘Ask whether the pilot is still a priority’ is a useful next question, but it should not appear as an agreed plan. If there is no recent interaction, the brief should make that gap clear.

Follow the introduction back to its source

A second useful prompt is: ‘Who introduced us originally? Find the first introduction in the available history and explain what the introducer said we should discuss.’ This helps you reopen a conversation with the right context.

If more than one person shares a name, add the company or role. If the thread is missing, ask Claude to identify the missing information instead of filling the gap. A well-scoped question is more useful than a confident guess.

Before your first meeting brief

Confirm the relevant contact and conversation are available in Cold, connect through the route offered to your account, and test one read-only request. An assistant can only prepare from the sources it can actually retrieve.

This workflow is meeting preparation, not automatic outreach. Drafting or sending a follow-up is a separate request and depends on the available tools. Review any suggested message before it leaves your account.

Give Claude the context behind your network

Start with one meeting rather than your entire pipeline. A useful first result explains who the person is to you, what remains unresolved and which next question would move the conversation forward.

Explore Cold MCP for the product workflow, or read the LinkedIn MCP Server overview to compare the assistant guides.