Posting, engagement, messaging, job search and analytics are the same session, so publishing something and reading its numbers two days later never involves the feed. The company tools are the exception the vendor marks itself: get_company_info and get_company_profile are described as limited access that may require a Marketing Solutions partnership, and update_partnerships exists to switch that on if you are granted it.
A LinkedIn client with 28 tools over an OAuth session: profile, posting and feed engagement, job search, connections, messaging and analytics.
- An OAuth session established against a standard LinkedIn Developer application, and revoked with the stored tokens cleared
- Your own profile over OpenID Connect, and profile lookups for other users by id
- Posts created with text and a visibility setting, your published posts with their engagement metrics, and the feed from your network
- Feed engagement: like, comment, and share with optional commentary
- Job search filtered by keywords, location, company, industry, function, experience level, job type, salary and date posted, plus job detail, saving, saved listings and application tracking
- People search by name, title, company, school, industry, location or keywords, connection requests sent with a personal message, incoming requests listed and accepted, and your full connection list
- Conversation threads, the messages in one, and direct messages sent to a connection
- Profile performance metrics, and per-post analytics by post id
A LinkedIn Developer application to authorize against; authenticate_linkedin runs the OAuth flow and revoke_linkedin_auth clears the stored tokens.
One command — npx -y linkedin-mcp-server