LinkedIn MCP Server

Full-stack MCP server that lets your AI agent (batabeto/OpenClaw) control LinkedIn as you — post, comment, like, manage your network.

Architecture

AI Agent (batabeto) ──MCP/HTTP──► LinkedIn MCP Server ──REST──► LinkedIn API
                                         │
                                   OAuth2 + Token Store
                                         │
                                    Dashboard UI

Setup Guide

1. Create a LinkedIn App

1. Go to LinkedIn Developers
2. Click Create App
3. Fill in: App Name, LinkedIn Page, Logo
4. Under Auth tab → Add Authorized redirect URLs:

   http://YOUR_EC2_IP:3000/auth/callback
   

   (or your domain if using nginx)
5. Under Products tab → Request:
   • Share on LinkedIn (gives w_member_social scope)
   • Sign In with LinkedIn using OpenID Connect (gives openid profile email)
6. Copy your Client ID and Client Secret

2. Install & Configure

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

cp .env.example .env
nano .env

Fill in .env:

LINKEDIN_CLIENT_ID=your_client_id
LINKEDIN_CLIENT_SECRET=your_client_secret
BASE_URL=http://YOUR_EC2_IP:3000
PORT=3000
MCP_SECRET_KEY=$(openssl rand -hex 32)

3. Run the Server

# Production
npm start

# Development (auto-restart)
npm run dev

# As a systemd service (recommended for EC2)
sudo nano /etc/systemd/system/linkedin-mcp.service

systemd service file:

[Unit]
Description=LinkedIn MCP Server
After=network.target

[Service]
Type=simple
User=ubuntu
WorkingDirectory=/home/ubuntu/linkedin-mcp
ExecStart=/usr/bin/node server.js
Restart=always
RestartSec=5
EnvironmentFile=/home/ubuntu/linkedin-mcp/.env

[Install]
WantedBy=multi-user.target

sudo systemctl enable linkedin-mcp
sudo systemctl start linkedin-mcp
sudo systemctl status linkedin-mcp

4. Authenticate LinkedIn

1. Open: http://YOUR_EC2_IP:3000
2. Click Connect LinkedIn
3. Authorize the app on LinkedIn
4. You'll be redirected back — status shows ✅ Connected

5. Connect to Your AI Agent

For OpenClaw (batabeto):

Add to your agent's MCP config:

{
  "mcpServers": {
    "linkedin": {
      "url": "http://YOUR_EC2_IP:3000/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_SECRET_KEY"
      }
    }
  }
}

For Claude Desktop:

{
  "mcpServers": {
    "linkedin": {
      "command": "npx",
      "args": ["mcp-remote", "http://YOUR_EC2_IP:3000/mcp", "--header", "Authorization: Bearer YOUR_MCP_SECRET_KEY"]
    }
  }
}

Available Tools

Example Agent Prompts

"Post on LinkedIn: Excited to share that I just deployed a full Kubernetes cluster
 with ArgoCD GitOps! #DevOps #Kubernetes"

"Get my last 5 LinkedIn posts"

"Delete my LinkedIn post with ID urn:li:ugcPost:1234567890"

"Comment 'Great insight!' on post urn:li:ugcPost:9876543210"

"Check my LinkedIn connection status"

API Limitations (LinkedIn)

LinkedIn's public API is restricted. Here's what works vs what doesn't:

Security

• The MCP endpoint is protected by MCP_SECRET_KEY — keep it secret
• OAuth tokens are stored locally in data/tokens.json — don't commit this file
• LinkedIn tokens expire in 60 days; refresh tokens last 365 days
• The server auto-refreshes tokens when < 5 days remain

Open EC2 Port

# In AWS Security Group, allow inbound:
# Port 3000, TCP, from your agent's IP (or 0.0.0.0/0 for testing)

Or use nginx to proxy yourdomain.com/mcp → localhost:3000/mcp.