linkedin-mcp

What it does

Point any MCP-capable agent at it and it can read a LinkedIn profile, check a draft post and publish it, through the official LinkedIn API.

{
  "mcpServers": {
    "linkedin": {
      "command": "linkedin-mcp",
      "env": {
        "LINKEDIN_ENGINE_HOME": "/home/you/.config/linkedin-engine"
      }
    }
  }
}

Related MCP server: LinkedIn MCP Server

The part that makes it different

A server that any agent can connect to, that publishes to a public feed on request, is a footgun. Every automated posting tool has the same failure mode: it produces something that technically publishes and reads as though nobody wrote it.

So the quality gate lives inside the server. An agent cannot publish a post that reads like a generated one, because the gate runs on the way out and refuses it. The agent gets told what is wrong and fixes it.

Errors block the post. Warnings do not, but they are reported.

The tools

Two resources, linkedin://profile and linkedin://profile/written, and a prompt, linkedin_draft_post, that walks an agent through drafting a post about a real artefact and checking it.

Safety

Three rules, and they are not optional:

The token is never a tool argument. It is read from the credential store that linkedin-engine uses, and it never appears in a tool result, a log line or an error message. An agent cannot ask this server for it — which means a prompt injection in a web page cannot ask it for it either.

Publishing is off by default. Reads always work. Writes need LINKEDIN_ENGINE_ALLOW_PUBLISH=1 in the server's environment. A server that publishes on request from any agent that connects to it is a bad idea at best.

A dry run needs no token. linkedin_publish_post answers the only question that matters — would this post go out — without needing the application to be authorised first, so you can test the gate before the LinkedIn app is even created.

Setup

You need a LinkedIn application with the Sign In With LinkedIn product (self-serve) and the Share on LinkedIn product (review, and the one that grants w_member_social, without which you can read but not publish).

The setup, including the Company Page step that stops most people, is documented in linkedin-engine/docs/SETUP.md.

Authorise it once:

pip install linkedin-engine
linkedin-engine auth setup --client-id ... --client-secret ... --redirect-uri ...
linkedin-engine auth login

Then start the server:

linkedin-mcp            # stdio, for a local agent
linkedin-mcp --http     # streamable HTTP, for a shared server

Configuration

See also

• linkedin-engine — the command line tool this server is built on. Same credential store, same quality gate, plus draft generation from your GitHub activity.

• shipfree — the Agent Skill for deploying AI services on free tiers.

Development

pip install -e ".[dev]"
pytest
ruff check . && ruff format --check .
mypy

License

MIT — see LICENSE.

Built by Aryan Raj Maurya.