LinkedIn Ops

No more manual LinkedIn scrolling. Search for jobs on LinkedIn blazing fast with your favorite coding agent, including Claude Code, Codex, and more. Then manage them using the web frontend.

Overview

LinkedIn Ops is a Model Context Protocol (MCP) server that lets your AI assistant (Claude Code, Codex, Claude Desktop, Cursor, or any MCP-compatible client) search LinkedIn for job posts, save them locally, and manage them through a React dashboard.

Job opportunities often appear in LinkedIn posts before they hit traditional job boards. This tool helps you catch them early.

How it works

1. Authenticate — A browser window opens for you to log into LinkedIn. Session cookies are saved locally for future use.

2. Search — Your AI assistant scrapes LinkedIn posts by keyword using Chromium. The browser is visible by default, with an optional headless mode.

3. Store — All posts are saved to a local SQLite database. Nothing leaves your machine.

4. Dashboard — A React web UI at http://localhost:4327 lets you browse, filter, and track posts visually.

5. Dual control — Manage posts through natural language AI commands or point-and-click in the dashboard. Changes sync both ways in real time.

Related MCP server: job-search-mcp

Project Structure

./app/
├── lib/              # Shared: auth, database, utilities
├── client/           # React dashboard (Vite + TailwindCSS)
└── servers/
    ├── mcp/          # MCP server entry point + tools
    └── api/          # Express REST API (serves dashboard)

Installation

Install from source

git clone https://github.com/yasir-ali/linkedin-ops.git
cd linkedin-ops
npm run install:all
npm run build

For local development, run npm link after the build if you want to invoke your checkout with the linkedin-ops command. This creates a global symlink on your machine; it does not publish anything to npm.

Claude Code

This repository includes a project-level .mcp.json for Claude Code. After cloning, replace its args[0] value with the absolute path to your own clone:

{
  "mcpServers": {
    "linkedin-ops": {
      "command": "node",
      "args": ["/absolute/path/to/linkedin-ops/dist/servers/mcp/index.js"]
    }
  }
}

Restart Claude Code or start a new chat in the project. The shared .claude/settings.json contains project settings; .claude/settings.local.json is intentionally ignored because it is machine-specific.

Codex

This repository includes a project-scoped .codex/config.toml. Replace the path in args with the absolute path to your own clone, then reopen the project or start a new Codex chat.

In Codex, use /mcp to confirm that linkedin-ops is connected. If the project configuration is not loaded, add the same command manually under Settings → MCP servers as a STDIO server:

Command: node
Path: /absolute/path/to/linkedin-ops/dist/servers/mcp/index.js

MCP Tools

Dashboard

Run manually if needed:

npm run dev    # start dashboard at http://localhost:4327
npm run kill   # kill whatever is holding port 4327

Features:

• Table and card views

• Filter by keyword, date, status, and saved state

• Mark posts as interested, applied, not interested, or saved

• Refreshes automatically every 3 seconds

Data Storage

Data remains local. Nothing is sent to external servers.

Scripts

License

MIT — see LICENSE for details.