Extract the people a company publishes on its own team, leadership or about page.
Team Page People Extractor (MCP) Server — com.mambabuilt/mcp-team-page-people-extractor
This MCP server extracts people a company publishes on its own team, leadership, or about page. It is designed to read those pages and return the relevant people entities associated with the organization’s published content.
🛠️ Key Features
Extracts people from a company’s team page
Extracts people from leadership pages
Extracts people from about pages
🚀 Use Cases
Build structured datasets of a company’s published leadership or team members
Populate internal directories from public team/leadership/about pages
⚡ Developer Benefits
Targets specific page types commonly used to publish people
Produces extracted people information from company-owned pages
⚠️ Limitations
Scope is limited to people published on the company’s own team, leadership, or about pages
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.
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.
Billing
You are charged per person found, plus a small actor start fee. A company that publishes nobody costs only the start fee.
Pricing 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.
