Is Team Page People Extractor free?

Yes, Team Page People Extractor is free to use.

How do I install Team Page People Extractor?

Team Page People Extractor is a local plugin. Install it using npm package: @mambalabsdev/mcp-team-page-people-extractor and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Team Page People Extractor safe to use?

Yes. Team Page People Extractor passed MCP Marketplace's automated security scan with a score of 9.3/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Team Page People Extractor need?

Team Page People Extractor requires the following credentials or environment variables: APIFY_TOKEN. You can find setup instructions on the server detail page.

What AI apps work with Team Page People Extractor?

Team Page People Extractor uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Team Page People Extractor MCP Server

by mambabuilt

Developer ToolsLow Risk9.3Local

Free

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

About

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

Security Report

9.3

Low Risk9.3Low Risk

Valid MCP server (2 strong, 3 medium validity signals). 1 known CVE in dependencies (0 critical, 1 high severity) Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (160/160 approved).

9 files analyzed · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

What You'll Need

Set these up before or after installing:

Apify API token from https://console.apify.com/account/integrationsRequired

Environment variable: APIFY_TOKEN

How to Install

Add this to your MCP configuration file:

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

Documentation

View on GitHub

From the project's GitHub README.

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

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.

Tool

`extract_team_page_people`

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.