@hoyasumii/linkedin

An unofficial MCP server and TypeScript SDK to create, edit and delete your own LinkedIn posts.

Documentation: hoyasumii.github.io/linkedin (English and Português), also as llms.txt and llms-full.txt for LLMs. linkedin docs opens it.

Unlike its siblings @hoyasumii/plane, @hoyasumii/signoz and @hoyasumii/libretranslate, this package delivers an MCP server and an SDK. Its CLI only signs you in and registers the server in your AI clients.

1. MCP server (@hoyasumii/linkedin/mcp, bin linkedin-mcp, stdio): linkedin_create_post, linkedin_edit_post, linkedin_delete_post, linkedin_list_posts, linkedin_get_post and linkedin_whoami.

2. SDK (createLinkedInClient): posts with text, images (1 to 20), a video (uploaded in parts), a document or an article link; edit the text; delete. Generated by orval from an OpenAPI 3.1 spec written for this package, with LinkedIn's little text format escaped for you.

3. CLI (bin linkedin): linkedin mcp config --web signs you in to LinkedIn from a local page; linkedin mcp install registers the server in Claude Code, Codex or OpenCode.

Installation

npm i -g @hoyasumii/linkedin     # or: pnpm add -g, or clone + pnpm build + npm i -g .

Create your LinkedIn app once (a Company Page, the Share on LinkedIn and Sign In with LinkedIn using OpenID Connect products, and the redirect URL http://localhost:3769/callback), then:

linkedin mcp config --web        # paste the Client ID and Secret, sign in on LinkedIn
linkedin mcp install             # register linkedin-mcp in Claude Code / Codex / OpenCode

The token lasts 60 days: run linkedin mcp config --web again when linkedin mcp status says it expired.

Related MCP server: linkedin-mcp

SDK

import { createLinkedInClient } from "@hoyasumii/linkedin";

const linkedin = createLinkedInClient({ accessToken: process.env.LINKEDIN_ACCESS_TOKEN! });

const { urn, url } = await linkedin.createPost({ text: "Shipped v1.0 (finally) #release" });
await linkedin.createPost({ text: "Screens", images: ["a.png", { file: "b.png", altText: "The dashboard" }] });
await linkedin.createPost({ text: "Demo", video: { file: "demo.mp4", title: "Demo" }, visibility: "CONNECTIONS" });
await linkedin.createPost({ text: "Our roadmap", document: "roadmap.pdf" });
await linkedin.editPost(urn, { text: "Shipped v1.0.1" });
await linkedin.deletePost(url);

A non-2xx answer throws LinkedInApiError (status, code, serviceErrorCode, body); an expired or missing sign-in throws LinkedInAuthError. The token is never in an error.

MCP server

By hand: claude mcp add linkedin -s user -- npx -y -p @hoyasumii/linkedin linkedin-mcp. The server reads the saved sign-in on every call; LINKEDIN_ACCESS_TOKEN in its environment overrides it.

Windows

Native Windows 10/11 (PowerShell, cmd) and WSL. From WSL, linkedin mcp install also reaches the clients installed on the Windows side. See Windows and WSL.

Development

pnpm install
pnpm codegen        # spec/openapi.yml → src/generated/ (orval)
pnpm test:unit      # a fake LinkedIn on node:http, no network
pnpm test:live      # posts, edits and deletes on the real LinkedIn (.env.test, see env.example)
pnpm docs:dev       # the docs site

See CONTRIBUTING.md.

Releasing

Every push to main runs .github/workflows/cd.yml: lint, format, types, knip, unit tests and the build. Then:

• when package.json's version is not on npm yet, it publishes it with provenance through npm Trusted Publishing (OIDC, no token in the repository), tags it v<version> and opens a GitHub release;

• when the push touches website/ or src/, it rebuilds the docs site and deploys it to the gh-pages branch.

# bump "version" in package.json, then:
git commit -am "chore: release 0.1.1"
git push origin main

License

MIT © Alan Reis Anjos