Extract the people a company publishes on its own team, leadership or about page.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Capabilities & Tool Schemas (1)
Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Team Page People Extractor.
extract_team_page_peopleGive 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.
Documentation Overview
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
Claude Desktop
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.
| 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.
Source
The actor is on the Apify Store. This wrapper is MIT licensed.
Built by Mamba Labs
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
npm downloads
243
Package downloads in the last 30 days.
Last commit
4d ago
Most recent push to the default branch.
Tools exposed
1
Callable tools this server registers over MCP.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about MCP Team Page People Extractor
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/mcp-team-page-people-extractor)HTML Embed
<a href="https://allmcps.com/mcp/mcp-team-page-people-extractor"><img src="https://allmcps.com/api/badge/mcp-team-page-people-extractor?style=directory" alt="MCP Team Page People Extractor on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
11/15 checks healthy over the last 46d
52Quality signal: Good · 52/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools23/30
Adoption & activity6/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 3d ago via OSV.dev · @mambalabsdev/mcp-team-page-people-extractor (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.