LinkedIn MCP Server

warnings

linkedin.run.mcp.com.ai

LinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP.

https://linkedin.run.mcp.com.ai/mcpWebsiteOAuthMCP 2025-06-18v0.6.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 446 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://www.linkedin.com
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✕plain MCP requires S256; a client that implements only that has no method in common with this server.
Grant types	authorization_code
Scopes	profile, email, openid, w_member_social, offline_access
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 3 tools listable
Documentation	https://api.linkedin.com/swagger

What the probe found

3 tools usable without signing in

The server exposes a public surface before authorization: createSharePost, getSharePosts, getPersonProfile.

Tools

createSharePostgetPersonProfilegetSharePosts

Contract history

24 Aug 2026v0.6.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/linkedin-mcp-server/badge.svg)](https://mcpi.app/servers/linkedin-mcp-server)