Skip to main content
Glama
Team Page People Extractor MCP Server

Team Page People Extractor MCP Server

Team Page People Extractor MCP Server

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

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

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

Claude Desktop

{
  "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.

Related MCP server: Company Discovery List Builder MCP Server

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.

Input

Type

Required

Notes

domain

string

yes

A single company domain, for example swishdata.com. Protocol and path are stripped.

output_grain

enum

no

person 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_filter

enum

no

all keeps everyone the page published. executive keeps founders and C-level only. leadership adds VPs, directors and heads.

max_people

string

no

Sent 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_emails

boolean

no

Off 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 user@domain.com 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.

skipCache

enum

no

false uses the 14 day result cache. true re-crawls the company from scratch.

max_charge_usd

number

no

Optional 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:

Event

Price per event (USD)

Fires when

apify-actor-start

$0.00005

Charged 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 plans

Charged 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

Available Tools

1 tool
extract_team_page_peopleExtract Team Page PeopleA
Read-onlyIdempotent

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.

Inputs: domain (required), skipCache, max_people, output_grain, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of selecting the wrong tool. The tool's purpose is clearly defined and distinct.

    Naming Consistency5/5

    The single tool name 'extract_team_page_people' follows a clear verb_noun pattern and is descriptive. No other tool names exist to create inconsistency.

    Tool Count4/5

    The server offers just one tool, which is at the lower end of the scale. However, the tool is highly configurable and the server's purpose is narrowly scoped, so the count feels appropriate rather than deficient.

    Completeness5/5

    The tool covers all aspects of its stated purpose: extracting people, handling empty results, filtering by seniority, and optional email extraction. There are no apparent missing operations for the read-only domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to analyze any company domain and determine its AI maturity tier (commercialized, deployed, declared, or none) with supporting evidence, via a single tool backed by an Apify actor.
      1
      88 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the Mamba Labs People Finder & Email Verifier actor on Apify. Give it a company domain, name or LinkedIn URL and it returns the people at that company who match your role, seniority and department filters, each as a structured contact record with an optional verified business email.
      1
      121 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Classifies job titles into department and seniority using deterministic rules, and optionally verifies if a person is listed on their employer's website via the Mamba Labs Contact Classifier Apify actor.
      1
      68 npm
      MIT