Mcp Team Page People Extractor

com.mambabuilt由 mambabuilt.com 发布v1.2.1更新于 Nov 7, 2026

Extract the people a company publishes on its own team, leadership or about page.

概览

AI 生成的概览

通过 Apify actor 抓取公司官网上团队、管理层或关于页面公开的人员,返回姓名、职位和来源页面。

可以做什么
  • 按公司域名提取其官网团队、管理层或关于页面公开的人员,含姓名、职位与来源页面
  • 按资历筛选(全部、仅高管,或含副总裁、总监和负责人的管理层),并可限制返回人数
  • 选择输出粒度:每人一行,或每家公司一行并附人员数组及展平的姓名与职位
  • 可选返回页面上的邮箱,仅出现在公司行上
  • 报告实际访问到的页面,便于区分“公司未公开人员”与“网站无法读取”
  • 可跳过 14 天结果缓存,重新完整抓取
适用场景
适合需要从公司自有网站快速获取其公开管理层或团队成员名单的场景,例如为潜在客户或客户名单补充信息。它不是人员搜索或职业社交网络工具,不会找到公司自己未公开的人员。
运行要求
通过 npx(Node.js)以 stdio 方式在本机运行。需要 Apify 账户,并通过 APIFY_TOKEN 环境变量提供 Apify API 令牌。需要访问 Apify 的网络连接,且每次运行会消耗 Apify 额度。
安装前请注意
每次运行都会消耗 Apify 额度:包含启动费与按人数计费,费用随找到的人数增加;可用 max_charge_usd 限制单次调用花费。APIFY_TOKEN 是可计费的凭据,应妥善保密。邮箱提取默认关闭,开启后地址只附在公司行上,不会关联到具体个人。输入与输出都会经过第三方 Apify actor。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mcp Team Page People Extractor,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Team Page People Extractor MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Team Page People Extractor MCP server]

MCP server for the Mamba Labs Team Page People Extractor actor on Apify.

Give it a company domain and it returns the people that company publishes on its own team, leadership or about page: names, titles, and the page each one came from. Nothing here reads LinkedIn or any other profile network.

Install

bash
npx -y @mambalabsdev/mcp-team-page-people-extractor

Claude Desktop

json
{  "mcpServers": {    "mamba-team-page-people-extractor": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-team-page-people-extractor"],      "env": { "APIFY_TOKEN": "your-apify-token" }    }  }}

Get an Apify token at console.apify.com/account/integrations.

Tool

extract_team_page_people

Give it a company domain and it returns the people that company publishes on its own team, leadership or about page: names, titles, and the page each one came from. Nothing here reads LinkedIn or any other profile network.

InputTypeRequiredNotes
domainstringyesA single company domain, for example swishdata.com. Protocol and path are stripped.
output_grainenumnoperson returns one row per person, which is the default and what most Clay tables want. company returns one row per company with a people_json array plus the first five names and titles flattened into columns.
seniority_filterenumnoall keeps everyone the page published. executive keeps founders and C-level only. leadership adds VPs, directors and heads.
max_peoplestringnoSent as a string so Clay can map a column into it. Clamped to 1 to 200. People are ordered by seniority before the cap applies, and anything dropped is logged with the count.
include_emailsbooleannoOff by default and you should probably leave it off. Across three domains that published an email on a team page we found one role mailbox, one placeholder in example content, and one literal [email protected] template string. Not one was a real person's address. When on, emails come back on the COMPANY row only, never attached to a named person, because nothing on these pages proves which address belongs to whom.
skipCacheenumnofalse uses the 14 day result cache. true re-crawls the company from scratch.
max_charge_usdnumbernoOptional spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged.

Billing

You are charged per person found, plus a small actor start fee. A company that publishes nobody costs only the start fee.

Prices from the live pricing record, read 2026-10-16:

EventPrice per event (USD)Fires when
apify-actor-start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
person-found$0.006 on the Free plan, down to $0.0051 on higher Apify plansCharged once per person returned. A company with no readable team page returns a summary row and costs nothing beyond the run. In company grain the charge is once per person in the people array, not once per row, so a single row carrying 17 people bills 17 events.

The current price is on the actor's Apify page. Running this server consumes Apify credits.

What this server does and does not do

It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.

Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.

Source

The actor is on the Apify Store. This wrapper is MIT licensed.

Built by Mamba Labs

来源:README.md,提交 5d634e1

工具

1

extract_team_page_people

Extract Team Page People

Extract the people a company publishes on its own team, leadership or about page, and return their names, titles and the page each one came from. It also reports which pages it actually reached, so an empty result tells you whether the company publishes nobody or whether the site could not be read, which are very different answers. output_grain person returns one row per person and is what most tables want; output_grain company returns one row per company with a people_json array plus the first five names and titles flattened into columns. seniority_filter narrows to founders and C level, or adds VPs, directors and heads. People are ordered by seniority before max_people applies, and anything dropped is logged with a count. include_emails is off by default and should usually stay off: across the domains tested, the addresses published on team pages were role mailboxes, placeholders and literal template strings rather than real people, so when it is on the emails come back on the company row only and are never attached to a named person. Results are cached for 14 days. Nothing here scrapes LinkedIn or any profile network; it reads only what the company published itself. Requires an APIFY_TOKEN and consumes Apify credits. Read only.

输入参数domain必填skipCachemax_peopleoutput_graininclude_emailsmax_charge_usdseniority_filter

版本历史

5
  1. v1.2.1最新Nov 5, 2026
  2. v1.2.0Oct 16, 2026
  3. v1.1.1Oct 6, 2026
  4. v1.1.0Oct 6, 2026
  5. v1.0.1Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分