What it does
Find LinkedIn people by name, title, employer or school. Paid, on Apify's hosted MCP.
- Connects 在云端运行
- Account or key Sign in to the service when you connect (OAuth)
- Category 营销与社交媒体
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 LinkedIn People Search。按照 https://mcp.popnx.com/i/johnisanerd-linkedin-people-search.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.apify.com) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称LinkedIn People SearchRemote MCP server URL · 地址https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsLinkedIn People Search
试一试
用 LinkedIn People Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 LinkedIn People Search,或回答中出现 LinkedIn People Search 的工具名称,就表示连接成功
菜单名称已于 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 People SearchConnection · 地址https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api在聊天中选择 LinkedIn People Search
开启新聊天,输入前先从插件列表中选择 LinkedIn People Search
试一试
用 LinkedIn People Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 LinkedIn People Search,或回答中出现 LinkedIn People Search 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user linkedin-people-search 'https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api'在 Claude Code 中输入 /mcp
应能看到 LinkedIn People Search 在列表中并显示已连接
试一试
用 LinkedIn People Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 LinkedIn People Search,或回答中出现 LinkedIn People Search 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 LinkedIn People Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 LinkedIn People Search,或回答中出现 LinkedIn People Search 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 LinkedIn People Search 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 LinkedIn People Search,或回答中出现 LinkedIn People Search 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.apify.com/?tools=johnvc/linkedin-people-search-apiJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user linkedin-people-search 'https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"linkedin-people-search": {
"url": "https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api"
}
}
}VS Code (mcp.json)
{
"servers": {
"linkedin-people-search": {
"type": "http",
"url": "https://mcp.apify.com/?tools=johnvc/linkedin-people-search-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月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 johnisanerd 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于昨天
- ✓ 通过
有许可证
使用 MIT
- ✓ 通过
端点有响应
在 44 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/johnisanerd-linkedin-people-search)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“营销与社交媒体”中的其他服务器比较i
- 星标数多于此分类中其他 4196 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 4196 个服务器的 83% 更新
- 基础检查结果等于或优于此分类中其他 4196 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
LinkedIn People Search 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于昨天,最新版本(1.0.0)于6天前进入注册中心。
哪些应用可以使用它?
支持 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 People Search | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 是 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
LinkedIn People Search MCP server
Registry name: io.github.johnisanerd/linkedin-people-search. Maintained by AlphaOSINT (Apify developer johnvc, GitHub johnisanerd).
What it does
Find people by name, job title, employer, school or location and get profile URL, headline, current employer, location, and optionally about text, work history and education.
When to use it
Finds people you don't have profile links for yet, where profile tools need the URL first. Use it for prospect lists, recruiting searches and finding the right contact at a company.
How it works
The server runs on Apify's hosted MCP endpoint, so there is nothing to install or host. Its URL pins one Actor with ?tools=johnvc/linkedin-people-search-api, which gives your agent a single tool, johnvc--linkedin-people-search-api, whose parameters are the Actor's typed input schema. The agent can call that tool directly without searching for an Actor first, and it can't start other Actors through this server. For general access to the whole Apify Store, use https://mcp.apify.com without the tools parameter.
Pricing
Each tool call runs the Apify Actor johnvc/linkedin-people-search-api on your own Apify account and is billed there at the Actor's prices:
| Charge | Price (USD) | What it covers |
|---|---|---|
| Person found | $0.0006 | Fee per person delivered to the dataset, with their public LinkedIn profile URL, name, headline and current employer. Charged once per person, never per search page, and never twice for the same person in one run. |
| Person enriched | $0.0025 | Fee per person whose public profile page was opened and parsed, adding the about text, work history, education, follower count, photo and languages. Charged only when the enrichment actually returned data. |
Free-plan rates as of 2026-11-13; paid Apify plans pay less per event. Apify also bills a token amount per run start and stored row ($0.00001, $0.00001). Current prices are on the Actor's page: https://apify.com/johnvc/linkedin-people-search-api
Endpoint
- Transport: Streamable HTTP
- URL:
https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api - Auth: Apify OAuth (opens on first use), or the header
Authorization: Bearer(Apify Console → Settings → API & Integrations)
Setup
Claude Code
claude mcp add --transport http linkedin-people-search "https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api"
VS Code (.vscode/mcp.json)
{
"servers": { "linkedin-people-search": { "type": "http", "url": "https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api" } } }
Cursor (~/.cursor/mcp.json)
{
"mcpServers": { "linkedin-people-search": { "url": "https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api" } } }
Claude Desktop: Settings → Connectors → Add custom connector, and paste the URL. Older versions without remote connectors can bridge through mcp-remote in claude_desktop_config.json:
{
"mcpServers": { "linkedin-people-search": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.apify.com/?tools=johnvc/linkedin-people-search-api" ] } } }
Tools
| Tool | What it does |
|---|---|
johnvc--linkedin-people-search-api | Runs the Actor with the parameters below and returns the result rows. |
get-actor-run | Status of a run the tool started (for long runs). |
get-dataset-items | Pages through a run's full output when it is larger than the inline result. |
get-key-value-store-record | Reads a record a run stored. |
abort-actor-run | Stops a run. |
Apify's endpoint adds the four helper tools whenever an Actor tool is loaded.
Parameters of johnvc--linkedin-people-search-api
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
firstName | string | First name of the person to find, for example Jane. Combined with lastName into an exact-phrase search, so the two together find people by full name. Leave both name fields empty only if you are searching with the keywo… | ||
lastName | string | Last name of the person to find, for example Doe. Combined with firstName into an exact-phrase search. | ||
keywords | string | Extra search terms to add to the query, for example a skill, an employer or an industry word. Use this on its own to search without a specific name, or alongside a name to narrow the matches. | ||
jobTitle | string | Job title to require, for example Software Engineer. Only people whose public profile or search snippet mentions this title are returned. | ||
company | string | Employer name to require, for example Microsoft. Matches people whose public profile mentions this company, current or past. | ||
school | string | School or university name to require, for example Stanford University. | ||
location | string | Place to require, for example San Francisco or United Kingdom. Matched as text against the public profile, so a city, region or country all work. | ||
maxResults | integer | 25 | Stop after delivering this many people. You are charged only for the people actually returned. Each search fetches a full page of ten results at once, so a run returns at least ten people when the query has that many ma… | |
enrichProfiles | boolean | true | When enabled, each person's public LinkedIn profile page is opened to add their about text, work history with job titles, education, connection and follower counts, photo and languages. Turn this off for a faster, cheap… |
Example
Ask the agent in plain language, or call johnvc--linkedin-people-search-api with arguments such as:
{
"jobTitle": "CTO", "company": "Stripe", "maxResults": 10 }
Output
JSON rows with these fields:
| Field | Type | Description |
|---|---|---|
resultType | string: person, error | Row kind. 'person' is a matched person. 'error' reports a page that could not be read and is never charged. |
profileUrl | string | Canonical public LinkedIn profile URL, with all tracking parameters removed. |
publicIdentifier | string | The profile slug, which is the last path segment of the profile URL. Stable per person and useful as a deduplication key. |
fullName | string | The person's name as shown on their public profile. |
headline | string | The professional headline shown under the person's name, usually their role and employer. |
currentCompany | string | Employer the person currently lists first on their profile. |
currentCompanyUrl | string | LinkedIn company page for the current employer, when the profile links one. |
about | string | The person's public About/summary text. Present only when the profile was opened for enrichment. |
locationLocality | string | City or metropolitan area from the public profile. |
locationCountry | string | Two-letter country code from the public profile. |
profilePhotoUrl | string | Public profile photo. Absent when the person has no public photo. |
followerCount | integer | Number of followers shown on the public profile. |
experience | array | Positions listed on the public profile, most recent first. Each entry has organizationName, organizationUrl, organizationLocation, role, startDate and endDate where the profile shows them. |
education | array | Schools listed on the public profile. Each entry has organizationName, organizationUrl, startDate and endDate where shown. |
languages | array | Languages listed on the public profile. |
awards | array | Honours and awards listed on the public profile. |
isEnriched | boolean | True when the person's public profile page was opened and parsed. False when the row carries search-level data only, which happens when enrichment is off or the profile would not open. |
searchRank | integer | Position of this person in the search results, starting at 1. |
searchQuery | string | The exact public search query this run used, so every row can be traced back to what was asked. |
searchHeadline | string | The headline text the search result showed, kept when the opened profile page has its own headline (which then fills headline). Absent on rows that were not enriched, where headline is the search text. |
currentTitle | string | Job title at the current employer, from the public profile. Each experience entry also carries its own title when the profile shows one. |
connections | integer | Connection count shown on the public profile. LinkedIn caps the display at 500, so 500 means 500 or more; see connectionsText. |
connectionsText | string | The connection count as LinkedIn shows it, for example 500+. |
memberId | string | LinkedIn's numeric member id for the profile, when the public page exposes it. Stable even if the profile URL changes. |
positions | array | Every position in the profile's experience section, past roles included. Each entry has title, companyName, companyUrl, startDate, endDate, duration, location and isCurrent where the profile shows them. |
fromCache | boolean | True when this row was served from the shared result cache instead of a new request: the opened profile for an enriched row, the search page otherwise. Billed like a fresh row. Search result pages are reused for up to 1… |
fetchedAt | string | UTC time the row's data was fetched from LinkedIn's public pages (the profile page for an enriched row, the search page otherwise). For a cached row this is the original fetch time. |
errorType | string | Short error class on error rows: 'SearchUnavailable' when the search could not be served (retry later). Absent on other error rows and on people. |
errorMessage | string | Why a page could not be read. Only present on rows where resultType is 'error'. |
Data source and terms
Public LinkedIn profiles found through web search and read from their public pages, collected by scraping. No login or cookies are used. The server returns the data as published at the time of the call. You are responsible for using it in line with the source's terms and the laws that apply to you. AlphaOSINT is not affiliated with the source.
Links
- Actor on Apify: https://apify.com/johnvc/linkedin-people-search-api
- Docs page: https://alphaosint.com/mcp/linkedin-people-search/
- All AlphaOSINT MCP servers: index