Skip to main content
Glama
linkedin-mcp-server

linkedin-mcp-server

by greg0r1

LinkedIn MCP Server

A Model Context Protocol (MCP) server that enables Claude Desktop to interact with your LinkedIn profile and company pages. Connect your LinkedIn account to Claude AI and manage your professional presence directly through conversations.

🎯 Features

βœ… Fully Supported (Standard API Access)

Personal Profile

  • Fetch your profile information

  • Create and publish posts

  • Read your posts

  • Delete posts

Company Pages

  • Publish posts on behalf of your company page

  • Read company page information

  • Get company posts

⚠️ Limited or Requires Special Access

Company Analytics

  • ⚠️ Requires Marketing Developer Platform access

  • Not available with standard API permissions

Job Search

  • ❌ LinkedIn deprecated the public job search API

  • Feature code exists but is not functional

Messaging

  • ❌ Requires additional LinkedIn API permissions

  • Not available with standard API access

  • Feature code exists but is not functional

Related MCP server: LinkedIn MCP Server

πŸš€ Quick Start

Prerequisites

  1. Node.js 18+ installed on your system

  2. A LinkedIn application - Create one here

  3. Claude Desktop - Download here

Installation Steps

1. Clone and install dependencies

git clone <your-repo-url>
cd linkedin-mcp-server
npm install

2. Create a LinkedIn Application

  1. Go to LinkedIn Developers

  2. Create a new app with these settings:

    • App name: Choose any name (e.g., "My LinkedIn MCP Server")

    • LinkedIn Page: Select your company page or create one

    • App logo: Optional

  3. In the Auth tab:

    • Add redirect URL: http://localhost:3000/auth/callback

    • Copy your Client ID and Client Secret

  4. In the Products tab, request access to:

    • "Sign In with LinkedIn using OpenID Connect"

    • "Share on LinkedIn"

3. Configure environment variables

cp .env.example .env

Edit .env and add your credentials:

LINKEDIN_CLIENT_ID=your_client_id_here
LINKEDIN_CLIENT_SECRET=your_client_secret_here
LINKEDIN_REDIRECT_URI=http://localhost:3000/auth/callback
LINKEDIN_COMPANY_ID=your_company_id_here  # Optional, for company page features

4. Build the project

npm run build

5. Authenticate with LinkedIn (one-time setup)

npm start

This step is only needed once to obtain your LinkedIn OAuth token:

  • Starts a temporary HTTP server on port 3000

  • Opens your browser to LinkedIn authentication

  • Saves your access tokens to ~/.linkedin-mcp-tokens.json (in your home directory)

  • The server will automatically close after authentication

Note: After this initial authentication, you don't need to run npm start again. Claude Desktop will use the saved token automatically.

πŸ”§ Claude Desktop Configuration

After building and authenticating, configure Claude Desktop to use your MCP server:

Add this configuration to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json Linux: ~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "linkedin": {
      "command": "node",
      "args": [
        "/ABSOLUTE/PATH/TO/linkedin-mcp-server/dist/index.js"
      ]
    }
  }
}

Important: Replace /ABSOLUTE/PATH/TO/linkedin-mcp-server with the actual path to your project directory.

To get the absolute path:

# On macOS/Linux
pwd

# On Windows (PowerShell)
Get-Location

Then restart Claude Desktop completely (quit and reopen).

How it works: Claude Desktop will automatically launch the MCP server (via dist/index.js) when needed. You don't need to run npm start - that was only for the initial OAuth authentication.

🎯 Usage

Once configured, you can ask Claude Desktop:

Personal Profile

"Get my LinkedIn profile information"
"Show me my LinkedIn profile"

Publishing Posts

"Post on LinkedIn: Just learned about MCP servers, amazing technology!"
"Show me my last 5 LinkedIn posts"
"Delete my last LinkedIn post"

Company Page (if configured)

"Post on my company page: We're hiring a Senior Developer!"
"Show posts from my company page"
"Get information about my company page"

Note: Job search and messaging features are not available with standard LinkedIn API access. See the Features section for details.

🏒 Getting Your Company ID (Optional)

To publish on your company page, you need to find your Company ID:

Method 1: Use the provided script

npm run get-company-id

This will authenticate and show all company pages you administrate.

Method 2: From LinkedIn URL

  1. Go to your company page on LinkedIn

  2. Look at the URL: linkedin.com/company/your-company-name/

  3. Use browser developer tools to find the numeric ID in the page source

Add the Company ID to your .env file:

LINKEDIN_COMPANY_ID=123456789

Note: You must be an administrator of the company page to post on its behalf.

πŸ“ Project Architecture

Built with Clean Architecture principles:

src/
β”œβ”€β”€ domain/              # Business entities
β”‚   β”œβ”€β”€ entities/       # LinkedIn entities
β”‚   └── interfaces/     # Contracts & interfaces
β”œβ”€β”€ application/        # Use cases
β”‚   └── use-cases/     # Business logic
β”œβ”€β”€ infrastructure/     # External services
β”‚   β”œβ”€β”€ linkedin/      # LinkedIn API client
β”‚   └── storage/       # Token storage
β”œβ”€β”€ presentation/       # MCP layer
β”‚   └── tools/         # Exposed MCP tools
└── index.ts           # Entry point

πŸ” Security

  • ⚠️ NEVER commit your .env file

  • ⚠️ OAuth tokens are stored locally in ~/.linkedin-mcp-tokens.json (in your home directory)

  • ⚠️ Keep .env in .gitignore

  • ⚠️ Tokens are automatically refreshed when needed

  • ⚠️ You can customize the token storage path with the TOKEN_STORAGE_PATH environment variable

πŸ› οΈ Development

# Build TypeScript (required before using with Claude Desktop)
npm run build

# Development mode with auto-reload (for testing changes)
npm run dev

# Authenticate with LinkedIn (one-time setup only)
npm start

# Get your company ID (for posting on company pages)
npm run get-company-id

Important:

  • npm run build is required before using the MCP server with Claude Desktop

  • npm start is only needed once for OAuth authentication

  • After authentication, Claude Desktop launches the server automatically via the config file

πŸ“š Resources

πŸ› Troubleshooting

"Invalid environment variables"

Check that your .env file contains valid values (not placeholders like your_client_id_here)

"Authentication failed"

  1. Verify your Redirect URI matches exactly: http://localhost:3000/auth/callback

  2. Check that you've requested access to required Products in LinkedIn Developer Portal

  3. Delete ~/.linkedin-mcp-tokens.json and try authenticating again

MCP server not starting in Claude Desktop

  1. Verify the path in claude_desktop_config.json is absolute and correct

  2. Ensure npm run build completed successfully

  3. Check Claude Desktop logs:

    • macOS: ~/Library/Logs/Claude/mcp*.log

    • Windows: %APPDATA%\Claude\logs\mcp*.log

"Company not found"

Make sure you're an administrator of the company page on LinkedIn

"Failed to retrieve LinkedIn posts" or rate limit errors

LinkedIn API has strict rate limits and restrictions:

  • Personal posts (get_my_posts): May be limited or require additional permissions

  • Company posts (get_company_posts): May require Marketing Developer Platform access

  • Try reducing the number of posts requested (use a smaller limit)

  • Check your LinkedIn app's permissions and products in the Developer Portal

  • Some endpoints may not be available with standard API access

MCP protocol errors or "broken pipe"

If you see errors in Claude Desktop logs about the MCP protocol:

  • This has been fixed in recent versions - ensure you have the latest code

  • All logging now goes to stderr (not stdout) to avoid interfering with the MCP protocol

  • Restart Claude Desktop after updating

πŸ“ License

MIT

πŸ‘€ Author

Created with ❀️ by Grégory Dernaucourt

🀝 Contributing

Contributions, issues, and feature requests are welcome!

⭐ Show your support

Give a ⭐️ if this project helped you connect your LinkedIn to Claude AI!

Available Tools

7 tools
linkedin_create_company_postA

Create and publish a post on behalf of a company page

Inputs: text (required), companyId (required), visibility.

linkedin_create_postB

Create and publish a post on your LinkedIn profile

Inputs: text (required), visibility.

linkedin_delete_postB

Delete one of your LinkedIn posts

Inputs: postId (required).

linkedin_get_company_pageB

Get information about a LinkedIn company page (e.g., GD Dev Solutions)

Inputs: companyId (required).

linkedin_get_company_postsA

Get recent posts from a company page

Inputs: companyId (required), limit.

linkedin_get_my_postsB

Get your recent LinkedIn posts

Inputs: limit.

linkedin_get_profileA

Get your LinkedIn profile information (name, email, etc.)

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: profile, user posts, and company posts are clearly separated. The verb+noun naming makes it impossible to confuse create_post with create_company_post or get_my_posts with get_company_posts.

    Naming Consistency5/5

    All tools follow the linkedin_<verb>_<target> pattern with consistent verbs (get, create, delete). Singular/plural usage matches the action (create one post, get multiple posts), and prefixes remain uniform.

    Tool Count5/5

    Seven tools is well-scoped for a LinkedIn server covering profiles, user posts, and company pages. Each tool serves a clear purpose with no redundancy.

    Completeness4/5

    Core workflows are covered: profile retrieval, post creation/listing/deletion for users, and company page info with post creation/listing. Missing update operations and company post deletion, but these are minor gaps for typical use.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers