Find a company contact page and extract role emails, a phone number and a postal address.
This MCP server locates a company contact page and extracts contact details from it. Specifically, it extracts role-based email addresses, a phone number, and a postal address. The server is identified by the slug com-mambabuilt-mcp-company-contact-details-extractor.
🛠️ Key Features
Find a company contact page
Extract role emails
Extract a phone number
Extract a postal address
🚀 Use Cases
Retrieve company contact information from a contact page
Collect emails by role for outreach or internal directories
Capture phone and mailing address details
⚡ Developer Benefits
Structured extraction of specific contact fields (role emails, phone, postal address)
Targeted workflow focused on contact-page content
⚠️ Limitations
Limited to contact pages and the three extracted data types (role emails, phone number, postal address)
An MCP server that finds a company contact page and extracts role emails, a phone number and a postal address. It wraps the Mamba Labs Company Contact Details Extractor actor on Apify and returns a Clay-ready flat JSON row to any MCP client.
Give it a company domain and it finds that company's contact page, then returns the role email addresses published on it, a main phone number in E.164 where the country resolves, and a postal address. One flat row per company.
Named individuals are never returned. An address is kept only when its domain belongs to the company and its local part is in the role vocabulary, so info@, support@, sales@ and privacy@ survive and a person's address is dropped by an allow list rather than by a name detector. The row reports how many addresses were found and how many were rejected and why, so a thin result is never mistaken for a site that publishes nothing.
All of the extraction runs on Apify. This package is a thin client that calls the actor and hands back the result unchanged.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
"Get the sales email for figma.com and skip the phone number."
"Pull contact details for this local plumbing company and allow free mailboxes."
"Extract the support address for notion.com, reading a second page if the contact page has nothing."
Inputs
company_domain (required by this tool): bare company domain, for example stripe.com. This is the lookup key and the join key for every other actor in the fleet. The tool returns an error naming the field when it is missing, before any run starts.
company_name (optional): used in the row and in logging. This tool gates addresses on the email domain rather than on the company name, so supplying a name does not change which addresses are kept.
emailTypes (optional): which classes of role address to return. One of all, general, support, sales, privacy, general_support or sales_only. all is the default and returns general, support, sales and privacy. The narrower settings return only what they name and leave the other columns null, which is a different answer from not finding one.
includePhones (optional): when true (the default) the contact page is scanned for a main phone number. Set false to skip phone extraction entirely.
includeAddress (optional): when true (the default) a postal address is read from JSON-LD first and from the footer second. Set false to skip it.
allowFreeMailboxes (optional): when false (the default) an address at Gmail, Outlook or another free provider is rejected, because it cannot be checked against the company domain. Set true for small business and local company lists, where a free mailbox on the contact page is often the real contact point.
crawlDepth (optional): how many pages to read after the homepage. 1 (the default) reads the contact page. 2 also reads a support or legal page when the contact page yielded nothing. This is a cost and thoroughness dial, not a change of answer.
skipCache (optional): when false (the default) a successful lookup is cached for seven days and reused. Set true to force a fresh fetch.
How a call runs
The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. The run is allowed 1,800 seconds. If it is still going two minutes after that, the call stops waiting and returns the run ID with a link to it in the Apify Console, where the results land when it finishes. A run that does not succeed comes back as an error with its run ID and status.
Output
The tool returns the actor's flat JSON row for the company, with 27 snake_case fields and no nested objects. emails_rejected_count and emails_rejected_reasons account for what was dropped, contact_page_method says how the contact page was found, and fetch_status says whether the read succeeded. See the Apify Store page for the full output schema.
Role email addresses only, never a named individual
Main phone number and postal address when the company publishes them
Contact page URL, plus how that page was found
Rejection accounting in emails_rejected_reasons, so a thin read is visible
Coverage reported per row
27 flat snake_case fields, one row per company
Full actor documentation
This server is a thin client and holds no extraction logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:
This server is one of the Mamba Labs GTM Suite MCP servers. Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything. The actor behind this server is the Company Contact Details Extractor, immutable Apify actor ID 4mMncKaJykiq94grz.
