Mcp Team Page People Extractor

com.mambabuiltPublished by mambabuilt.comv1.2.1Updated Nov 7, 2026

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

Overview

AI-generated overview

Extracts the people a company lists on its own team, leadership or about page, returning names, titles and source pages via an Apify actor.

What you can do
  • Extract people from a company's own team, leadership or about page by domain, with names, titles and the page each came from
  • Filter results by seniority (all, executive, or leadership including VPs, directors and heads) and cap the number of people returned
  • Choose output shape: one row per person, or one row per company with a people array plus flattened names and titles
  • Optionally include emails found on the page, reported on the company row only
  • Report which pages were actually reached, so an empty result can be told apart from an unreadable site
  • Re-crawl a company from scratch instead of using the 14-day result cache
When to use it
Useful when you need a quick list of a company's publicly published leadership or team members from its own website, for example to enrich a prospect or account list. It is not a people-search or profile-network tool, so it will not find people a company does not publish itself.
Requirements
Runs locally via npx (Node.js) as a stdio process. Requires an Apify account and an Apify API token supplied in the APIFY_TOKEN environment variable. Network access to Apify is needed, and Apify credits are consumed per run.
Before you install
Every run spends Apify credits: a start fee plus a per-person charge, so costs scale with the number of people found; an optional max_charge_usd cap can limit a call. The APIFY_TOKEN is a billable credential and should be kept private. Email extraction is off by default and, when enabled, addresses are attached only to the company row, not to named individuals. Input and output pass through the third-party Apify actor.

Installation

In SourceWeft

  1. Open Mcp Team Page People Extractor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit 5d634e1

Tools

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.

ParametersdomainrequiredskipCachemax_peopleoutput_graininclude_emailsmax_charge_usdseniority_filter

Version history

5
  1. v1.2.1LatestNov 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

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts