M
mambalabsdev/mcp-meta-brand-presence-mapper
MCP server for the Mamba Labs Instagram Facebook Brand Presence Mapper actor on Apify.
updated 2026-11-05
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · mambalabsdev/mcp-meta-brand-presence-mapper · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
mambalabsdev/mcp-meta-brand-presence-mapper;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Instagram Facebook Brand Presence Mapper MCP Server
Excerpted from the repository README (abridged)
MCP server for the Mamba Labs Instagram Facebook Brand Presence Mapper actor on Apify.
Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts.
## What it does
Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts, as one flat Clay ready row. The Threads handle is derived from the resolved Instagram handle at no extra discovery cost. Instagram and Threads counts are rounded by Meta and the row carries both the rounded integer and the platform's own display string. Facebook is best effort: Meta serves a login wall to anonymous clients, so blocked is a normal answer there and never a zero. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.
## Quick start
Add this to your MCP client configuration:
json
"mcpServers": {
"mamba-meta-brand-presence-mapper": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-meta-brand-presence-mapper"],
"env": { "APIFY_TOKEN": "your-apify-token" }
## Prerequisites
Node.js 18 or newer
An Apify API token from console.apify.com/account/integrations
The actor is pay per event and consumes Apify credits per call. Pricing is on the
actor page.
## Example prompts
"Get the Instagram and Threads follower counts for glossier.com."
"Has oatly.com adopted Threads yet, and how many posts do they have?"
"Find the Facebook Page for everlane.com."
## Tool and inputs
Tool: map_meta_brand_presence
| Input | Type | Meaning |
| company_domain | string | Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to the fetch. |
| company_name | string | Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches. |
| handle | string | Optional. The Instagram handle with or without the leading @. Supplying it skips Instagram discovery AND gives Threads its handle for free, because Threads handles are Instagram handles (5 of 5 measured). |
| platforms | array | Which of the three Meta surfaces to map. Default is all three. Dropping Facebook is the common choice: it is the least reliable of the three and it costs a fetch to find that out. |
| includeFollowerCounts | boolean | Default true: the profile page is fetched and the follower counts are extracted. Set false to resolve the profile URL only, which is cheaper and needs no proxy. |
| skipCache | boolean | Default false: a successful lookup is cached for seven days and reused. Set true to force a fresh fetch. |
| max_charge_usd | number | 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. |
## Reading the output
Every row carries a per platform _status field, and it is the field to read
first. The vocabulary is the same across the whole Mamba Labs social family:
| Status | Meaning |
| ok | fetched and parsed, the value is there |
| not_found | we looked and there is no such profile |
Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts.
## What it does
Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts, as one flat Clay ready row. The Threads handle is derived from the resolved Instagram handle at no extra discovery cost. Instagram and Threads counts are rounded by Meta and the row carries both the rounded integer and the platform's own display string. Facebook is best effort: Meta serves a login wall to anonymous clients, so blocked is a normal answer there and never a zero. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.
## Quick start
Add this to your MCP client configuration:
json
"mcpServers": {
"mamba-meta-brand-presence-mapper": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-meta-brand-presence-mapper"],
"env": { "APIFY_TOKEN": "your-apify-token" }
## Prerequisites
Node.js 18 or newer
An Apify API token from console.apify.com/account/integrations
The actor is pay per event and consumes Apify credits per call. Pricing is on the
actor page.
## Example prompts
"Get the Instagram and Threads follower counts for glossier.com."
"Has oatly.com adopted Threads yet, and how many posts do they have?"
"Find the Facebook Page for everlane.com."
## Tool and inputs
Tool: map_meta_brand_presence
| Input | Type | Meaning |
| company_domain | string | Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to the fetch. |
| company_name | string | Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches. |
| handle | string | Optional. The Instagram handle with or without the leading @. Supplying it skips Instagram discovery AND gives Threads its handle for free, because Threads handles are Instagram handles (5 of 5 measured). |
| platforms | array | Which of the three Meta surfaces to map. Default is all three. Dropping Facebook is the common choice: it is the least reliable of the three and it costs a fetch to find that out. |
| includeFollowerCounts | boolean | Default true: the profile page is fetched and the follower counts are extracted. Set false to resolve the profile URL only, which is cheaper and needs no proxy. |
| skipCache | boolean | Default false: a successful lookup is cached for seven days and reused. Set true to force a fresh fetch. |
| max_charge_usd | number | 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. |
## Reading the output
Every row carries a per platform _status field, and it is the field to read
first. The vocabulary is the same across the whole Mamba Labs social family:
| Status | Meaning |
| ok | fetched and parsed, the value is there |
| not_found | we looked and there is no such profile |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mambalabsdev-mcp-meta-brand-presence-mapper/)
- Source
- awesome · https://github.com/mambalabsdev/mcp-meta-brand-presence-mapper
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.