About Linkedin MCP Server
Linkedin MCP Server is an MCP server for the LinkedIn Community Management API that can run locally or remotely over HTTP+SSE. It implements the draft Third-Party Authorization Flow, delegating authorization to LinkedIn's OAuth server. The project requires users to supply their own LinkedIn client credentials.
Key features
- 01HTTP+SSE transport for local or remote hosting
- 02Draft third-party authorization flow implementation
- 03user-info tool for current user details
- 04create-post tool for publishing LinkedIn posts
Use cases
- 01Reading the logged-in user's name, headline and picture
- 02Publishing posts to LinkedIn from an MCP client
- 03Testing the draft MCP authorization flow with MCP Inspector
MCP support
This is an MCP server that exposes the user-info and create-post tools to MCP clients through the /sse endpoint.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMELinkedin MCP Server
MCP server for interacting with Linkedin Community Management API.
This MCP server:
- Can be hosted locally or remotely : uses HTTP+SSE transport defined in MCP
- Implements the Draft Third-Party Authorization Flow from MCP specs to delegate authorization to LinkedIn's OAuth authorization server
⚠️ Disclaimer: The Third-Party Authorization Flow proposal status is currently in draft. The only MCP client, to my knowledge, that currently implements this specification of the protocol is the MCP Inspector
Features
Tools
user-info- Get current logged in user infos (name, headline and profile picture)create-post- Create a new post on LinkedIn
Installation
Follow those instructions to run Linkedin MCP server on your host. You'll need to provide your own Linkedin client.
Requirements
- Node 22 (
lts/jod) - pnpm 10
- a Linkedin client with
Community Management APIproduct installed andhttp://localhost:3001/callbackadded to the authorized redirect URLs
Instructions
- Install dependencies:
pnpm install
- Create env file and populate with your Linkedin client credentials and a random string secret value for
JWT_SECRET:
cp .env.template .env && vi .env
- Run the server:
pnpm run dev
- Configure your favorite MCP client to use this new server:
{
"mcpServers": {
"linkedin": {
"url": "http://localhost:3001/sse"
}
}
}
Debugging
Start the MCP Inspector to debug this server, which is available as a package script:
pnpm run inspector
Access the inspector in your browser at http://localhost:5173
Acknowledgment
- Den Delimarsky that bravely gave a first shot at this new authorization flow with Microsoft Entra ID and detailed his results in his blog post: https://den.dev/blog/auth-modelcontextprotocol-entra-id/
- Matt Pocock and his always welcome neat TS tricks specifically in the context of writting your own MCP server on AI Hero: https://www.aihero.dev/publish-your-mcp-server-to-npm
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.