Linkedin MCP Server

LinkedIn MCP server — publish posts, articles, and media via the LinkedIn API

Local serverstdio

What is the Linkedin MCP server?

Most developer tooling work still happens through a UI a human drives. Linkedin MCP server moves it into the conversation instead. LinkedIn MCP server — publish posts, articles, and media via the LinkedIn API.

The short version

MCP server for publishing posts, articles, and media to LinkedIn. Part of the Human Agency Protocol.

The tools it exposes

The server publishes 7 tools. What each one is for:

  • create_post — Publish a text post
  • create_article_post — Publish a post with a link/article
  • create_image_post — Publish a post with an image
  • get_post — Get a post by URN
  • list_posts — List your recent posts
  • delete_post — Delete a post
  • get_profile — Get your LinkedIn profile

Getting it running

The server ships on npm as @humanagencyp/linkedin-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: LINKEDIN_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Linkedin's toolset — create_post, create_article_post, create_image_post and 4 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
create_postPublish a text post
create_article_postPublish a post with a link/article
create_image_postPublish a post with an image
get_postGet a post by URN
list_postsList your recent posts
delete_postDelete a post
get_profileGet your LinkedIn profile

How to install the Linkedin MCP server

{
  "mcpServers": {
    "linkedin-1": {
      "command": "npx",
      "args": ["-y", "@humanagencyp/linkedin-mcp"],
      "env": {
        "LINKEDIN_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LINKEDIN_ACCESS_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Linkedin to create post.
  • Use Linkedin to create article post.
  • Use Linkedin to create image post.

Frequently asked questions

It connects Linkedin to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (create_post, create_article_post, create_image_post, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Linkedin directly.