LinkedIn MCP Server

Lets Claude Code post to your own LinkedIn: write, preview, save drafts, schedule, comment and react, all by talking to Claude. Nothing is published until you type a confirmation keyword.

What you need

• Claude Code

• Node.js 20 or newer (node -v to check)

• macOS or Linux (Windows is untested)

• A LinkedIn account

• About 10 minutes

Related MCP server: @isteam/linkedin-mcp

Setup

1. Create your own LinkedIn app (5 minutes)

LinkedIn only lets software post for you through an "app" that you own. It is free and nobody else sees it.

1. Go to linkedin.com/developers/apps and click Create app.

2. Fill in:

   • App name: anything, e.g. "My Claude MCP"

   • LinkedIn Page: any company page you admin. If you have none, create a blank one first; LinkedIn insists on it.

   • App logo: any image

3. Open the Products tab and request both:

   • Share on LinkedIn

   • Sign In with LinkedIn using OpenID Connect

4. Open the Auth tab and add this redirect URL exactly: http://localhost:8585/callback

5. Still on the Auth tab, copy your Client ID and Client Secret. Keep the secret private; it is a password.

2. Install

The easy way: open Claude Code and paste this, with your two values filled in.

Clone https://github.com/ayushnagvanshi101098-ship-it/linkedin-mcp-server.git into ~/linkedin-mcp-server, run npm install and npm run build in it, then add it to Claude Code as a user-scope MCP server named linkedin that runs node ~/linkedin-mcp-server/dist/index.js with the env vars LINKEDIN_CLIENT_ID=your_client_id and LINKEDIN_CLIENT_SECRET=your_client_secret.

Or by hand in a terminal:

git clone https://github.com/ayushnagvanshi101098-ship-it/linkedin-mcp-server.git ~/linkedin-mcp-server
cd ~/linkedin-mcp-server
npm install
npm run build

claude mcp add linkedin --scope user \
  -e LINKEDIN_CLIENT_ID=your_client_id \
  -e LINKEDIN_CLIENT_SECRET=your_client_secret \
  -- node ~/linkedin-mcp-server/dist/index.js

3. Connect your LinkedIn

Quit and reopen Claude Code, then say:

authenticate with linkedin

A browser tab opens. Approve it and you are connected. To check at any time, ask "what's my linkedin status".

LinkedIn logins expire after roughly two months. When posting stops working, say "authenticate with linkedin" again.

4. Post

Post this to LinkedIn: [your text]

Claude shows a preview of how it will look in the feed. Nothing goes out until you type POST IT.

Things you can say

• "Post this to LinkedIn: ..." (text, or with an image, or a PDF document/carousel)

• "Preview this post" / "Lint this post"

• "Save this as a draft" / "Show my drafts" / "Publish draft 3"

• "Schedule draft 3 for tomorrow at 9am"

• "Show my post history"

• "Delete that post"

The safety keywords

Every action that changes something waits for you to type a keyword.

Good to know

• The post checker is opinionated. It blocks em dashes, a few cliché phrases ("game-changer", "move the needle") and anything over 3,000 characters. If you want to post anyway, say OVERRIDE LINT. The rules live in src/lint/rules.ts.

• Video posts do not work yet. Text, image and PDF posts do. Upload videos on LinkedIn directly for now.

• Scheduled posts need the scheduler, and it is macOS only. Say "install the linkedin scheduler" once. Your Mac must be awake at the scheduled time.

• Commenting and reacting on other people's posts needs LinkedIn's Community Management API, which most personal apps do not have. On your own posts it works.

Optional: reading LinkedIn (inbox, profiles, search)

These tools read things the official API cannot, by driving a real browser logged in as you. You do not need them to post.

cd ~/linkedin-mcp-server && npx playwright install chromium   # about 280 MB, once

Then say "linkedin scrape login" and log in by hand in the window that opens.

LinkedIn's terms discourage automated browsing. Calls are slowed down and run one at a time, but this part is at your own risk. The posting tools above use the official API and are unaffected.

Where your data lives

All on your machine, nothing is sent anywhere except LinkedIn.

Never share these files or your Client Secret. Anyone holding them can act as you on LinkedIn.

All tools

Settings

Set these next to the Client ID and Secret if you need them. Most people need none.

Troubleshooting

• "Port 8585 is already in use" during login: something else is on that port. Close it and try again.

• Login page says the redirect does not match: the redirect URL in step 1.4 must be exactly http://localhost:8585/callback.

• Claude does not see the tools: quit and reopen Claude Code, then run claude mcp list and check linkedin is connected.

• Something failed mid-action: a report is written to ~/.linkedin-mcp/diagnostics/.