mcp-partner-member-directory-extractor
LocalAbout mcp-partner-member-directory-extractor
An Apify-backed MCP server that extracts company records from partner directories and member lists. It returns domains, websites, tiers, and other published listing details for directory research.
Key features
- 01Reads supported partner and member directories
- 02Company domains and websites
- 03Tiers, tags, and locations
- 04Published ratings and contact details
- 05Optional domain deduplication
Use cases
- 01Build a list of partner companies
- 02Collect Shopify partner details
- 03Turn association listings into company domains
MCP support
Exposes the `extract_directory_companies` tool to MCP clients. It starts the Apify actor, waits for completion, and returns dataset rows.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @mambalabsdev/mcp-partner-member-directory-extractorAPIFY_TOKENSecretApify API token from https://console.apify.com/account/integrationsLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
1Saved tool list · updated 6d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| max_pages | string | No | Shopify and member list directories: listing pages to read, 1 to 100. Default 10. |
| max_listings | string | No | Listings per directory, 1 to 5000. Each company row is billed. Default 100. |
| directory_url | string | No | One directory page URL. |
| dedupe_domains | enum | No | Return a company listed more than once only once; skipped repeats are free. Default true.true | false |
| directory_urls | array | No | Up to 20 directory page URLs. |
| max_charge_usd | string | No | Optional. The run stops before any row that would take its charges over this amount. |
| include_details | enum | No | PartnerPage directories: true adds tags, location, and the listed email with one more request per listing. Default true.true | false |
Details
From the project READMEPartner and Member Directory Extractor MCP Server
An MCP server for the Mamba Labs Partner and Member Directory Extractor actor on Apify. Give it a partner directory or a member list URL. Each listed company comes back as one row with its website, domain, tier, tags, and location.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Tool
- Inputs
- Pricing
- Your keys
- Full actor documentation
- License
What it does
The actor reads three directory families: directories built on PartnerPage (Clay's Solutions Partner Directory and the Zapier partner directory among them), read through PartnerPage's public listing API; the Shopify Partner Directory; and member lists that link to one profile page per member, such as a trade association directory. Each row carries listing_name, company_domain, website, listing_url, tier, tags, location, rating, review_count, partner_since, and the listed_email and listed_phone the directory publishes. robots.txt is checked before every request. A directory that builds its list in the browser returns one free row with row_status unsupported.
All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:
{
"mcpServers": {
"mamba-partner-member-directory-extractor": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-partner-member-directory-extractor"
],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}
Restart the client. The extract_directory_companies tool appears.
Prerequisites
- Node.js 18 or newer.
- An Apify API token from console.apify.com/account/integrations, set as
APIFY_TOKEN. The server lists its tool without a token; a call needs one.
Example prompts
- "List every agency in the Clay experts directory with its website and tier."
- "Pull 100 Shopify partners that do store migrations, with their rating and location."
- "Turn the IAB UK member directory into a list of company domains."
Tool
extract_directory_companies. One tool. Example arguments:
{
"directory_url": "https://www.clay.com/en/experts",
"max_listings": "200"
}
Inputs
Every buyer facing input of the actor. Omitted inputs take the actor's own defaults. Numbers and yes or no inputs are sent as text.
| Input | Type | Description |
|---|---|---|
directory_url | string | One directory page |
directory_urls | array | Up to 20 directory pages |
max_listings | string | Listings per directory, 1 to 5000. Default 100 |
max_pages | string | Shopify and member lists: listing pages to read. Default 10 |
include_details | string | PartnerPage: tags, location, and email. Default true |
dedupe_domains | string | Return a repeated company once. Default true |
max_charge_usd | string | Optional cost cap for the run |
Pricing
Pay per event on Apify, billed to your Apify account. Prices in USD.
| Event | Free plan | Bronze | Silver | Gold |
|---|---|---|---|---|
company-listed, per company row | $0.004 | $0.0038 | $0.0036 | $0.0034 |
apify-actor-start, per run start (one per GB of run memory) | $0.0015 | $0.0015 | $0.0015 | $0.0015 |
Skipped repeats, and no listings, robots disallowed, blocked, unsupported, and error rows are free.
Your keys
The actor needs no key. Proxy traffic adds nothing to your price: Mamba Labs pays the platform costs of the run.
Full actor documentation
apify.com/mambalabs/partner-member-directory-extractor
License
MIT. See LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.