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 分