LinkMCP

How to Connect LinkedIn to n8n (with an MCP Server)

Short answer: use n8n's built-in MCP Client Tool node to connect a LinkedIn MCP server - no custom node or install required. n8n natively speaks the Model Context Protocol, so you point its MCP Client Tool node at a LinkedIn MCP server like LinkMCP, and every LinkedIn tool (read profiles, search, message, enrich) becomes available inside your workflows and AI-agent nodes. This is the simplest, most maintainable way to add LinkedIn to n8n.

Why the MCP approach (and not a dedicated node)

You don't need a special "LinkedIn" community node. n8n's MCP Client Tool node connects to any MCP server and exposes its tools directly - so a single MCP connection gives you the full LinkedIn tool set, and it keeps working as the server adds tools, with nothing to install or maintain on the n8n side.

Steps

  1. Get a LinkedIn MCP server endpoint. With a hosted server (LinkMCP), connect your LinkedIn account once in the dashboard (this needs a paid plan) and copy the server URL and access token. (No browser extension or local scraper.)
  2. Add the MCP Client Tool node in your n8n workflow.
  3. Configure the connection with the server URL and token (as a Bearer credential).
  4. Use the tools - attach the MCP Client Tool to an AI Agent node so the agent can call LinkedIn tools, or invoke a specific tool directly in a workflow step.

What you can build in n8n

  • Lead enrichment pipelines - take a list of LinkedIn URLs or a search, pull profile data, enrich with emails, write to your CRM.
  • AI-agent workflows - an agent that researches a prospect, drafts a personalized message, and queues it.
  • Inbox automation - triage LinkedIn messages, draft context-aware replies for approval.
  • Engagement tracking - pull who engaged with your posts and route follow-ups.

Account risk in automated workflows

Because n8n can run on a schedule, it's easy to accidentally push high volumes. Keep volumes low:

  • Use an MCP server with limits on every action (LinkMCP has them by default), not raw scraping.
  • Add delays and daily caps in your workflow; don't blast connection requests.
  • Treat any published limit as a ceiling, not a target.

See our guide on LinkedIn automation risk for detail.

FAQ

Do I need a LinkedIn community node for n8n?
No - the built-in MCP Client Tool node connects to a LinkedIn MCP server directly, which is simpler and more complete.

Does this work with n8n's AI Agent nodes?
Yes - attach the MCP Client Tool to an AI Agent and it can call the LinkedIn tools as part of its reasoning.

Self-hosted or hosted n8n?
Either - the MCP Client Tool node works the same. You just need a reachable MCP server URL and token.

Can a scheduled workflow put my LinkedIn account at risk?
Yes. Any automated use of LinkedIn can put an account at risk, and a schedule makes high volumes easy. Keep volumes low. LinkMCP puts daily limits and pacing on every action and a hard monthly usage cap on every plan, so a looping workflow stops. That lowers the risk; it does not remove it.

LinkMCP is a hosted LinkedIn MCP server that plugs into n8n's MCP Client Tool node - 34 LinkedIn tools, managed sessions, no install. Start a free trial.