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.
A LinkedIn client that runs on your own LinkedIn Developer App. You authorize once over OAuth and the session persists; after that, posting, engagement, job search and analytics happen in the conversation.
- OAuth sign-in and a revoke tool that clears the stored tokens when you are done
- Posts created with text and a visibility setting, plus your published posts read back with engagement metrics
- Engagement on other people's posts: like, comment, and share with your own commentary
- Your feed read back with posts from your network
- Job search across keywords, location, company, job type, salary, date posted and experience level, one posting's full detail, jobs bookmarked for later, and the status of applications you have made
- People search by name, title, company, school, industry and location, any profile read by id, and your own profile over OpenID Connect
- Connection work: your connections listed, requests sent with a personal message, incoming requests reviewed and accepted
- Messaging: conversation threads listed, messages read from one thread, and a direct message sent to a connection
- Profile and per-post analytics
- A partnership setting that records which special LinkedIn access — Sales, Talent or Marketing Solutions, or Community Management — you have been approved for
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.
One command plus a key — npx -y linkedin-mcp-server, then supply credentials