Apart from LinkedIn’s own apps, every LinkedIn MCP server is run by someone else, and what matters most is how it reaches LinkedIn. We group the servers in the official MCP Registry in four ways, by how they describe themselves:
- LinkedIn tools’ own servers, like the ones in the table. They act through your account with that tool, which posts through its own LinkedIn connection; ContentIn, Postiv and Supergrow say they use LinkedIn’s official API.
- Data services that return profiles, companies, jobs or posts for sales and recruiting research. They read other people’s data, not your account.
- Outreach servers that search people and send messages and connection requests from an account you connect. Several say you approve each message.
- Self-hosted browser servers that you run on your computer and that sign in to LinkedIn as you, through your own browser session, to read profiles, your inbox or your feed.
LinkedIn’s rules speak to the last two kinds most directly. Its User Agreement (section 8.2) asks members not to “Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement”, and not to “Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services”. Its help page on prohibited software says “we don’t permit the use of any third party software, including “crawlers”, bots, browser plug-ins, or browser extensions that scrape, modify the appearance of, or automate activity on LinkedIn’s website”, and that members who use such tools “they risk having their accounts restricted or shut down”. On invitations: “If you send an excessive number of invitations and we suspect the use of an automation tool, we may suspend or restrict your account.” On posts: “If we detect excessive post creation that indicates inauthentic activity, or the use of an automation tool, we may limit the visibility of those posts.”
The rules are about automated access and inauthentic engagement, not about who wrote the words. A post you draft with Claude and publish yourself never touches LinkedIn’s systems until you post it. A server that signs in as you and clicks through LinkedIn on its own is the kind of tool the help page describes. Tools in between post through LinkedIn’s API with your permission: LinkedIn’s developer docs list posting for a member as an open permission, “Post, comment and like posts on behalf of an authenticated member.”, and add that “Most permissions and partner programs require explicit approval from LinkedIn.” Some content tools’ servers now draft comments and replies from the chat too, and section 8.2 names commenting. We cannot judge any tool’s compliance for you: ask the vendor how each feature reaches your account, and decide what you are comfortable with.