Connect your AI Agents to LinkedIn in minutes

What is a LinkedIn MCP?

It's an MCP server that lets your agents publish content and access data on LinkedIn via tools. Your agents can invoke these tools to create text posts, share articles, publish images, retrieve organization details, and more.

LinkedIn doesn't offer an MCP server purpose built for LinkedIn, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the LinkedIn MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Automated content publishing from a CMS: When a new article is published in a CMS like WordPress or Contentful, an agent creates a LinkedIn article share with a curated excerpt and link, posting it to the company page without manual intervention

• Job opening announcements: When a new role is opened in an ATS like Greenhouse or Lever, an agent publishes a LinkedIn text post with the job title, team, and application link, keeping the company page current without requiring the recruiting team to post manually

• Product launch distribution: When a product update is approved in a content workflow, an agent formats it for LinkedIn and publishes a branded image share to the company page, coordinated with posts going out on other channels simultaneously

• Weekly social performance digest: An agent pulls post analytics from the LinkedIn company page on a weekly schedule, combines them with website traffic data, and sends a consolidated social performance summary to the marketing team in Slack

What are popular tools for LinkedIn's MCP server?

Here are some of the most commonly used tools:

• create_text_share: publishes a text-only post to a LinkedIn profile or company page. Use this when an agent needs to push a short update, announcement, or commentary on behalf of an account

• create_article_share: shares a URL with an optional title and commentary as a LinkedIn post. Good for workflows that automatically promote new blog posts, press releases, or external content as soon as they go live

• create_image_share: publishes a post with one or more image attachments and accompanying caption text. Use this when an agent is distributing visual content like product graphics, event announcements, or branded assets

• get_profile: retrieves basic profile information for the authenticated LinkedIn user, including name, headline, and current position. Helpful when an agent needs to verify account identity or personalize outgoing post content

• get_organization: fetches details about a LinkedIn company page, including follower count, description, and page status. Call this when an agent needs to confirm page access or pull company metadata before publishing

• get_post_analytics: returns engagement metrics for a specific post, including impressions, clicks, likes, and shares. Useful for agents that compile performance reports or use engagement signals to inform future publishing decisions

What makes Merge Agent Handler's LinkedIn MCP server better than alternative LinkedIn MCP servers?

When comparing options for a LinkedIn MCP server, here's what Merge Agent Handler brings to the table:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For LinkedIn, this means you can prevent post content, profile details, and engagement analytics from being exposed to agents beyond what the specific use case requires

• Managed authentication and credentials: Merge stores and refreshes LinkedIn OAuth tokens on your behalf. You never manage token expiry or re-authorization flows manually, and agents never handle raw credentials

• Real-time observability and audit trail: Every tool call against LinkedIn is logged with full context: which tool ran, what content was submitted, and what the API returned. That record is available immediately without any extra instrumentation on your end

• Tool Packs and controlled access: Tool Packs let you bundle specific LinkedIn tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's LinkedIn MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the LinkedIn connector. Choose which tools to include: posting tools like create_text_share and create_image_share are the right fit for publishing workflows, while get_post_analytics is useful if your agent needs to measure content performance.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate LinkedIn by completing the OAuth flow. Merge stores and manages the credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your LinkedIn tools are now accessible through that endpoint.