mambalabsdev/mcp-team-page-people-extractor

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": { "APIFYTOKEN": "your-apify-token" }
Get an Apify token at console.apify.com/account/integrations.
## Tool
### extractteampagepeople
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. |
| outputgrain | 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 peoplejson array plus the first five names and titles flattened into columns. |
| seniorityfilter | enum | no | all keeps everyone the page published. executive keeps founders and C-level only. leadership adds VPs, directors and heads. |
| maxpeople | 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. |
| includeemails | 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. |
| maxchargeusd | 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). |