MCP.so
ログイン

Linkedin MCP Server

@fredericbarthelet

Linkedin MCP Server について

An MCP Server for Linkedin API

基本情報

カテゴリ

その他

ランタイム

node

トランスポート

stdio

公開者

fredericbarthelet

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "linkedin": {
      "type": "http",
      "url": "http://localhost:3001/sse"
    }
  }
}

ツール

2

Get current logged in user infos (name, headline and profile picture)

Create a new post on LinkedIn

概要

What is Linkedin MCP Server?

An MCP server that integrates with the LinkedIn Community Management API. It allows users to retrieve their LinkedIn profile information and create posts via MCP tools. Designed for developers and AI assistants needing to interact with LinkedIn programmatically.

How to use Linkedin MCP Server?

Install dependencies with pnpm, set environment variables (LinkedIn client credentials and JWT_SECRET), and run with pnpm run dev. Configure an MCP client to connect to http://localhost:3001/sse. Debug using MCP Inspector via pnpm run inspector.

Key features of Linkedin MCP Server

  • Retrieve current user info (name, headline, profile picture)
  • Create new posts on LinkedIn
  • Uses HTTP+SSE transport for local or remote hosting
  • Implements draft third-party authorization flow with LinkedIn OAuth

Use cases of Linkedin MCP Server

  • Automate posting LinkedIn updates from an AI assistant
  • Fetch LinkedIn profile data for personal or automated workflows
  • Integrate LinkedIn posting capability into MCP-compatible clients

FAQ from Linkedin MCP Server

What dependencies are required?

Node 22 (lts/jod), pnpm 10, and a LinkedIn client with the Community Management API product installed and http://localhost:3001/callback as an authorized redirect URL.

How do I configure the LinkedIn client?

Create a .env file from .env.template and populate with your LinkedIn client credentials and a random JWT_SECRET value.

Does the server support remote hosting?

Yes, it uses HTTP+SSE transport, allowing it to be hosted locally or remotely.

What MCP clients support this server's authorization flow?

The draft Third-Party Authorization Flow is currently only implemented by the MCP Inspector; other clients may not support it.

How can I test the server locally?

Run pnpm run dev to start the server, then configure an MCP client to point to http://localhost:3001/sse. Use pnpm run inspector for debugging.

コメント

「その他」の他のコンテンツ