linkedin-ops
MCP server that enables AI assistants to search LinkedIn for job posts, save them locally, and manage them via a React dashboard.
README
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
- Authenticate — A browser window opens for you to log into LinkedIn. Session cookies are saved locally for future use.
- Search — Your AI assistant scrapes LinkedIn posts by keyword using Chromium. The browser is visible by default, with an optional headless mode.
- Store — All posts are saved to a local SQLite database. Nothing leaves your machine.
- Dashboard — A React web UI at
http://localhost:4327lets you browse, filter, and track posts visually. - Dual control — Manage posts through natural language AI commands or point-and-click in the dashboard. Changes sync both ways in real time.
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
| Tool | Description | Example prompt |
|---|---|---|
auth |
Sign in, check the LinkedIn session, or clear saved credentials. | “Check LinkedIn auth status” |
search_posts |
Search LinkedIn posts and save new results locally. | “Find React developer posts, 5 pages, headless” |
manage_posts |
Read, count, or delete stored posts. Supports keyword, text, ID, applied, saved, limit, and offset filters. | “Show posts I haven't applied to” |
dashboard_filters |
Read or update filters shared with the dashboard. | “Show only unapplied posts” |
start_dashboard |
Open the local dashboard at http://localhost:4327. |
“Open the dashboard” |
stop_dashboard |
Stop the local dashboard server. | “Stop the dashboard” |
debug_page |
Inspect a LinkedIn page’s DOM while using the saved session. | “Inspect the LinkedIn search results page structure” |
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.
| Platform | Location |
|---|---|
| Windows | %APPDATA%\linkedin-mcp\ |
| macOS/Linux | ~/.linkedin-mcp/ |
Scripts
| Command | Description |
|---|---|
npm run build |
Full build (TypeScript + React) |
npm run dev |
Start dashboard at localhost:4327 |
npm run kill |
Kill dashboard process |
npm run clean |
Delete dist/ |
npm run typecheck |
TypeScript check without building |
License
MIT — see LICENSE for details.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。