LabscoMCP early access ↗
souravdasbiswasMCP SERVER

LinkedIn Posts & Events MCP

Post to LinkedIn from chat — text, articles or images — then list, comment on, react to or delete posts, and create events, on a LinkedIn app of your own.

by souravdasbiswas ↗Social Media Accounts & PostingCommunity

LABSCO SUMMARY

Your own LinkedIn app, driven from the conversation you were already drafting in.

Because it runs on credentials you create rather than a shared integration, what it can do is exactly what LinkedIn granted your app — the self-serve products cover sign-in and posting, and the wider surfaces sit behind LinkedIn's partner programmes. Budget ten minutes for the app setup: the redirect URL has to match character for character, and the first authorization ends with you pasting a browser URL back into the chat because nothing is listening on the callback port.

What it is

A LinkedIn client that runs on your own LinkedIn Developer App. You authorize once over OAuth and the session persists; after that, posting, comments, reactions and events happen in the conversation.

What you get

  • OAuth sign-in and a revoke tool that clears the stored tokens when you are done
  • Posts created as text, an article or an image — linkedin_create_post, linkedin_upload_image — and the posts you made through the server listed back or deleted — linkedin_list_my_posts, linkedin_delete_post
  • Reactions and comments on a post — linkedin_react_to_post, linkedin_create_comment
  • Your own profile and email over OpenID Connect — linkedin_get_my_profile, linkedin_get_my_email
  • Events created and read back — linkedin_create_event, linkedin_get_event — and your current rate-limit usage — linkedin_get_rate_limits
  • Extra modules switched on automatically when your app has Community Management API or Advertising API approval — the server only exposes tools your granted scopes allow

Requirements

Your own LinkedIn Developer App, with LINKEDIN_CLIENT_ID and LINKEDIN_CLIENT_SECRET from its Auth tab and http://localhost:3000/callback registered as the redirect URL — matched exactly, no trailing slash. Two products have to be enabled on the app, Sign In with LinkedIn using OpenID Connect and Share on LinkedIn, which gives the openid, profile, email and w_member_social scopes. Node.js 20 or newer; the server is cloned and built, then launched as node dist/index.js. Company lookups are marked limited access and may require a Marketing Solutions partnership. Authorization is a paste-back flow: LinkedIn redirects to a port nothing is listening on, so you copy the resulting URL out of the address bar.

Setup effort

Build from source — git clone https://github.com/souravdasbiswas/linkedin-mcp-server.git

See installation options