能做什么
Company employee lists from LinkedIn public pages, by job title and city, via a hosted MCP server.
作者提供的原文
- 连接方式 在云端运行
- 账号或密钥 连接时登录该服务(OAuth)
- 分类 营销与社交媒体
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 6/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 26/100 |
质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 LinkedIn Company Employees。按照 https://mcp.popnx.com/i/johnisanerd-linkedin-company-employees.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/5 项检查 · 你的提问会经过开发者的服务器(mcp.apify.com) · ✓ 命令已检查 2026年11月20日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称LinkedIn Company EmployeesRemote MCP server URL · 地址https://mcp.apify.com/?tools=johnvc/linkedin-company-employees-api在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsLinkedIn Company Employees
试一试
用 LinkedIn Company Employees 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 LinkedIn Company Employees,或回答中出现 LinkedIn Company Employees 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称LinkedIn Company EmployeesConnection · 地址https://mcp.apify.com/?tools=johnvc/linkedin-company-employees-api在聊天中选择 LinkedIn Company Employees
开启新聊天,输入前先从插件列表中选择 LinkedIn Company Employees
试一试
用 LinkedIn Company Employees 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 LinkedIn Company Employees,或回答中出现 LinkedIn Company Employees 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user linkedin-company-employees 'https://mcp.apify.com/?tools=johnvc/linkedin-company-employees-api'在 Claude Code 中输入 /mcp
应能看到 LinkedIn Company Employees 在列表中并显示已连接
试一试
用 LinkedIn Company Employees 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 LinkedIn Company Employees,或回答中出现 LinkedIn Company Employees 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 LinkedIn Company Employees 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 LinkedIn Company Employees,或回答中出现 LinkedIn Company Employees 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 LinkedIn Company Employees 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 LinkedIn Company Employees,或回答中出现 LinkedIn Company Employees 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.apify.com/?tools=johnvc/linkedin-company-employees-apiJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user linkedin-company-employees 'https://mcp.apify.com/?tools=johnvc/linkedin-company-employees-api'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"linkedin-company-employees": {
"url": "https://mcp.apify.com/?tools=johnvc/linkedin-company-employees-api"
}
}
}VS Code (mcp.json)
{
"servers": {
"linkedin-company-employees": {
"type": "http",
"url": "https://mcp.apify.com/?tools=johnvc/linkedin-company-employees-api"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
它能做什么
服务器要求先登录,才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 johnisanerd 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于5天前
- ✕ 未通过
有许可证
仓库中没有找到许可证文件
- ✓ 通过
端点有响应
在 462 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
云端地址最近 5 次检查中有 5 次响应 · 最近一次 462 ms · 检查于 2026年11月19日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/johnisanerd-linkedin-company-employees)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“营销与社交媒体”中的其他服务器比较i
- 星标数多于此分类中其他 4243 个服务器的 91%
- 发布到注册中心的时间比此分类中其他 4243 个服务器的 37% 更新
- 基础检查结果等于或优于此分类中其他 4243 个服务器的 61%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
LinkedIn Company Employees 安全吗?
它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于5天前,最新版本(1.0.0)于2个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Relaticle
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
ChatbotX
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
X (Twitter) MCP Server by Xquik
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Betterlytics
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
| 本项 LinkedIn Company Employees | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 是 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | – | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
👥 LinkedIn Company Employees API: Company Employee List from Python and MCP
Get a company employee list from LinkedIn as JSON: name, job title, location and public profile URL for the people who work at a company, each checked against their own public profile.
- Actor: LinkedIn Company Employees API on Apify
- Input schema: input parameters
- Get a free API token: apify.com
This repo is a Python and MCP quick-start for the LinkedIn Company Employees API on Apify. Give it company names or LinkedIn company URLs and it returns a list of employees at each company, one row per person, with name, job title, headline, location and profile URL. By default it opens each person's public profile and keeps only the people who show a current role at the company, so a LinkedIn employee list from this API leaves out the people who have moved on. It needs no LinkedIn login, cookie or seat. Expect a partial list: the API can only find people whose public profiles show up in search results, which in testing was roughly 10 to 45% of a small company, 7 to 19% of a mid-size one and under 1% of a very large one. A fresh run with profile checks takes about 3 to 10 minutes per company.
Responsible use: the API returns only what LinkedIn shows signed-out visitors and collects no contact details such as emails or phone numbers, and you are responsible for using the data lawfully.
Video Walkthrough
Text walkthrough
The LinkedIn Company Employees API turns a company name or a LinkedIn company URL into a company employee list. You pass companies (up to 50 per run) and can narrow the list with titleKeywords such as "engineer" or "head of" and locations such as "New York". Each row carries fullName, currentTitle, headline, location, profileUrl and companyName, plus verified and matchReason, which record whether the person's public profile shows a current role at the company, and foundBy, the public search that found them. For talent mapping, a recruiter can pass Datadog's LinkedIn URL with titleKeywords: ["engineer"] and locations: ["New York"] and get the engineers there who are confirmed as current staff, with title and location. The run's RUN_SUMMARY record compares what was found with LinkedIn's own employee count, so you always know how much of the company a run reached. The default run in this repo asks for three people at one small company and costs well under a cent; a fresh verified run takes 3 to 10 minutes per company, and results served from the shared cache come back much faster.
Quick Start
Prerequisites
- Python 3.11 or higher
- An Apify account and API key (get a free key here)
- Clone the repository
git clone https://github.com/johnisanerd/Apify-LinkedIn-Company-Employees-API.git
cd Apify-LinkedIn-Company-Employees-API
- Install dependencies with UV
# Install UV if you do not have it:
curl -LsSf https://astral.sh/uv/install.sh | sh
Install project dependencies:
uv sync
- Configure your API key
cp .env.example .env
Edit .env and add your Apify API key
Get your free API key at: https://apify.com?fpr=9n7kx3
- Run the example
uv run python linkedin-company-employees-api-example.py
The script starts one run for Firecrawl with maxResultsPerCompany: 3, prints the run id, waits for the run to finish, then prints each person and the company's coverage line from RUN_SUMMARY. To try another input, replace RUN_INPUT at the top of the script with any JSON input from this README; the optional knobs are already there as comments.
The script starts a run and then reads the dataset instead of making one synchronous call on purpose. Apify's synchronous run endpoints stop waiting after 300 seconds, and a verified run for one company can take longer than that.
Alternative: set the API key directly
export APIFY_API_TOKEN="your_api_key_here"
uv run python linkedin-company-employees-api-example.py
Why Use This LinkedIn Company Employees API?
No LinkedIn login, cookie or seat
The API reads only what LinkedIn shows a signed-out visitor. There is no field for an account, a password or a session cookie, so no LinkedIn account is ever at risk, and anyone with a free Apify token can run it.
Each person checked against their public profile
With verifyEmployment on (the default), the API opens each person's public profile and keeps them only if it shows a current role at the company you asked about. A person whose profile shows another employer, or whose own headline says "Former" or "Retired", is dropped and never charged.
Rows you can audit
matchReason says how employment was decided and foundBy records the exact public search that found each person (or company-page for people listed on the company's own page), so any list can be checked and reproduced.
Coverage in every run
Every run writes RUN_SUMMARY with the people found and verified per company, LinkedIn's own employee count and the coverage ratio between the two.
Pay per person, never per search
Search requests and profile page reads are never charged on their own. You pay one small event per person delivered, plus one per stored row and one per run start (see Pricing).
Get a company employee list from LinkedIn
Paste company names straight from a CRM or a spreadsheet, or use LinkedIn company URLs. A URL is exact. A name is matched to its LinkedIn company page first, and a name that cannot be matched with confidence returns a CompanyNotFound error row instead of another company's people, so you can retry with the URL. One run takes up to 50 companies and returns a list of employees at each one:
{
"companies": [ "https://www.linkedin.com/company/stripe", "Datadog", "https://www.linkedin.com/company/vercel" ], "maxResultsPerCompany": 25 }
Each person comes back once per company with their name, title or headline, location and profile URL. Download the dataset as JSON, CSV or Excel, or open the run's Employees view for a flat LinkedIn employee list (name, title, company, location, verified, profile URL).
How to find employees of a company
By hand, you would open the company's LinkedIn page and scroll its People tab while signed in, or search the web for site:linkedin.com/in "Company Name" and open the profiles one at a time. The API runs those public searches for you, across about a dozen role slices for a company of up to 500 people and about 30 above that, then opens each profile and keeps only current employees.
To search employees of a company by role or by place, add titleKeywords and locations. Both narrow the list and add searches that surface more people: each title keyword is its own search, which reaches people that a plain company search ranks too deep to find, and every search names the place. For a large company, raise maxSearchQueriesPerCompany (up to 100) to reach more of it.
Talent mapping: see who works on a competitor's team
Talent mapping means charting who holds which roles at the companies you hire from, before you start sourcing. If you are comparing talent mapping tools or software, this one is a pay-per-person API you can call from a script, a spreadsheet workflow or an AI agent. One function in one city at a competitor:
{
"companies": ["https://www.linkedin.com/company/datadog"], "titleKeywords": ["engineer"], "locations": ["New York"], "maxResultsPerCompany": 30, "verifyEmployment": true }
Each verified row gives the person's title or headline, location and how the match was made. Work history appears only on the few profiles that show it to signed-out visitors, so read the result as a map of who is on the team now, not of where they came from. A large company returns a slice of its staff; titles and cities pick which slice.
Account mapping: the decision makers at each target account
In sales, account mapping means listing the people who make or shape buying decisions at each target account. Pass your accounts and the seniority words you care about:
{
"companies": ["Ramp", "Deel", "Vercel"], "titleKeywords": ["vp", "head of", "director"], "maxResultsPerCompany": 15, "verifyEmployment": true }
Seniority comes from title words only, because LinkedIn's internal seniority and function filters are not public. Title keywords match anywhere on a person's public page, so scan the titles in the result before you hand the list to outreach. The API returns no reporting lines and no emails.
CRM hygiene: confirm your contacts still work at the account
Contact records go stale as people change jobs. List who works at each account now, then match the result against your CRM by profileUrl or slug:
{
"companies": [ "https://www.linkedin.com/company/stripe", "https://www.linkedin.com/company/microsoft" ], "titleKeywords": ["procurement", "accounts payable"], "maxResultsPerCompany": 30, "verifyEmployment": true }
A contact who appears in the list is confirmed as current staff. A contact who is missing may simply not be indexed by search, so a missing name is not proof that the person left. There is no contact-list input: the API takes companies, not people.
Features
Core Capabilities
- A company employee list for up to 50 companies per run, from LinkedIn company URLs or plain company names
- Narrow by
titleKeywords(up to 20) andlocations(up to 10); both also add searches that surface more people verifyEmploymenton by default; off for a faster, search-level list- Up to 1,000 people per company with
maxResultsPerCompany, and up to 100 search slices per company withmaxSearchQueriesPerCompany - A shared cache for recent profiles, company pages and searches: repeat requests come back faster
- Datasets download as JSON, CSV or Excel, with a ready-made Employees view
- Works as an MCP tool in Claude, Cursor and ChatGPT (see the install sections below), and as an n8n community node (see Use from n8n)
Data Quality
verifiedandmatchReasonon every employee row; people whose profile shows no current role at the company are never returnedfoundByon every employee row, so each person can be traced to the search that found them- People whose own headline says "Former" or "Retired" are dropped
fromCacheandfetched_atshow whether a row came from the shared cache and when it was fetched- A company that cannot be matched or searched produces an error row (
CompanyNotFound,CompanyPageUnavailable,SearchUnavailableorInvalidInput), never a person charge RUN_SUMMARYreports found, verified, LinkedIn's employee count and coverage for every company
It pairs with the rest of the LinkedIn suite: the LinkedIn Company API for company size, industry and headquarters (Python example repo), the LinkedIn Profile API for full profiles from URLs you already have (Python example repo), and the LinkedIn People Search API to find people by name, job title, school or location across every company.
Coverage, speed and limits
- Partial coverage. The API finds people through public search results, so it returns the people search engines have indexe