LinkedIn MCP Server: The Complete Guide to Posting via Claude

Search for "LinkedIn MCP server" and most of what comes back — LinkedIn's own help pages, threads on Reddit, repos on GitHub — is about reading LinkedIn data: profile lookups, company page scraping, connection graphs. Almost none of it is about publishing. If you want an agent in Claude Desktop or Claude Code to actually post to LinkedIn on your behalf, you need a different category of tool, and it's worth being precise about the distinction before you install anything.

#Scraper MCP vs Posting MCP: Know the Difference

A scraper MCP server reads data LinkedIn exposes — profile fields, company page info, sometimes search results — usually without going through LinkedIn's own API, since LinkedIn doesn't offer broad read access to arbitrary profiles. These are useful for research and lead enrichment. They cannot publish anything. Many of the "LinkedIn MCP" repos you'll find on GitHub are this category, and running one expecting it to post will just fail silently or throw a missing-tool error.

A posting MCP server goes through LinkedIn's actual API — either the self-serve Share on LinkedIn product (w_member_social scope, personal profile) or the reviewed Community Management API (w_organization_social scope, company Pages) — and exposes publish, schedule, and account-management actions as MCP tools an LLM can call. This is what you need if the goal is "have Claude draft and post an update to my LinkedIn feed."

The confusion matters because the SERPs for this term are currently dominated by the scraper category. If you install one of those expecting posting capability, you'll hit a dead end.

#LinkedIn's Own API Constraints You Need to Know First

Before configuring anything, understand what LinkedIn itself will and won't let you do — no MCP server can get around these:

• Personal profile vs company Pages are different products with different scopes. Posting to your own feed uses w_member_social and is self-serve — no review needed. Posting to a company Page requires w_organization_social, an admin role on that Page, and Community Management API access, which does go through LinkedIn's review process. If your posting MCP only asks for personal-profile auth, it cannot post to a Page account, and vice versa — confirm which one you actually need before connecting.
• The Community Management API requires a registered legal entity. LinkedIn does not grant it to individual developers. If you're posting on behalf of a business's Page as an agency or a tool builder, this is a hard requirement upstream of any MCP layer.
• Daily write limits are real and tight. LinkedIn's Share on LinkedIn product allows roughly 150 API calls per member per day; other endpoints can be far lower. A posting MCP server should queue and pace requests so an agent doesn't blow through this in a scripting loop — see Social Media API Rate Limits: A Platform-by-Platform Reference for the full breakdown across platforms.

#Configuring Claude to Post to LinkedIn

The general pattern for any MCP-based posting setup is the same: add the server to Claude Desktop's or Claude Code's MCP config, authenticate once, and the tools become available to the model automatically.

For Claude Desktop, add an entry to your MCP config:

 1{
 2  "mcpServers": {
 3    "schedulenchill": {
 4      "command": "npx",
 5      "args": ["-y", "@schedulenchill/mcp-server"],
 6      "env": {
 7        "SCHEDULENCHILL_API_KEY": "your_key_here"
 8      }
 9    }
10  }
11}

For Claude Code, add the server the same way through its MCP settings, pointing at the same package and key. After that, restart the client so it picks up the new server, then authenticate the LinkedIn connection itself (OAuth happens through the provider's own flow, not through Claude) — see Schedule & Chill's docs for the exact connection steps.

Once connected, ask Claude to draft and post directly: "Draft a LinkedIn post about our Q3 roadmap update and schedule it for tomorrow at 9am." The model calls the relevant tools without you writing any code.

#The MCP Tools That Matter for LinkedIn Posting

Whichever posting MCP server you use, these are the tool categories to look for:

• Schedule a post — the core action. It should accept a when value (draft, immediate, or a specific timestamp) rather than assuming publish-now, so the agent can't accidentally post something you meant to review first.
• List scheduled posts — lets the agent (or you, asking the agent) check what's already queued before adding more, avoiding duplicate or conflicting posts.
• Get connected accounts — returns which LinkedIn accounts (personal profile, company Page, or both) are actually connected and postable, so the agent doesn't guess and fail against an account you haven't authorized.

Schedule & Chill's MCP server ships all three as part of its 21-tool set — schedule_post, list_posts (aliasing the older list_scheduled), and get_accounts — alongside media upload and analytics tools. Full reference is in the docs, and the underlying dedicated LinkedIn scheduling tool (outside the MCP layer, for teams that want a UI) is at LinkedIn Scheduler.

#Frequently Asked Questions

Can any LinkedIn MCP server post to a company Page? Only if it authenticates through the Community Management API with w_organization_social scope and you have admin rights on that Page as a registered legal entity. A server that only handles personal-profile auth cannot post to a Page.

Why do most "LinkedIn MCP server" search results not mention posting? Because LinkedIn restricts broad read access to profile and company data, most public MCP servers for LinkedIn are built around scraping rather than publishing, which requires going through LinkedIn's actual API and its approval process for company Pages.

Does Claude need direct access to my LinkedIn password? No. Authentication happens through LinkedIn's OAuth flow, handled by the MCP server's provider — Claude never sees your LinkedIn credentials or the raw access token, only the tool results.