Instagram Facebook Brand Presence Mapper
Resolve a company domain to Instagram, Threads and Facebook accounts and counts.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@mambalabsdev/mcp-meta-brand-presence-mapperclaude mcp add instagram-facebook-brand-presence-mapper -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-meta-brand-presence-mapper@1.2.1{
"mcpServers": {
"instagram-facebook-brand-presence-mapper": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-meta-brand-presence-mapper@1.2.1"
],
"env": {
"APIFY_TOKEN": "<your apify_token>"
}
}
}
}Variables d'environnement
APIFY_TOKENobligatoire secret Apify API token from https://console.apify.com/account/integrations
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Instagram Facebook Brand Presence Mapper MCP Server
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:
{
"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 |
not_extractable | the profile exists and the value is not on the wire to us |
blocked | the platform refused us, worth retrying later |
identity_mismatch | we found a real profile and it belongs to someone else |
skipped | you did not ask for this platform |
false and null are never interchangeable. false means we looked and the
answer is no. null means we could not look. If you filter for companies with no
presence, filter on false, because null rows are unknown rather than absent.
Pricing
You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:
| Event | Price per event (USD) | Fires when |
|---|---|---|
apify-actor-start | $0.00005 | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). |
company-checked | $0.005 on the Free plan, down to $0.0035 on higher Apify plans | Once per company for which the discovery cascade completed and a non degraded row was produced, whether or not any Meta platform resolved. Does not fire on a degraded row, because on a degraded row the company site was never read and no presence was measured. |
platform-resolved | $0.003 on the Free plan, down to $0.0021 on higher Apify plans | Once per REQUESTED Meta platform whose candidate URL passed the identity gate. Fires on the validation work, not on a populated follower cell. A candidate dropped as an impersonator does not charge: the work was done and the answer is that there is no such profile. A platform the caller did not request never fires it. |
follower-count-extracted | $0.0025 on the Free plan, down to $0.00175 on higher Apify plans | Once per Meta platform where a numeric follower count was read off the public Open Graph card. Does not fire on not_extractable, blocked, identity_mismatch or a URL only run. Facebook therefore often does not fire it, which is correct: it is the platform we most often cannot read. |
The actor's Apify page carries the current prices. Running this server consumes Apify credits.
Full actor documentation
apify.com/mambalabs/meta-brand-presence-mapper
Mamba Labs GTM Suite
Mamba Labs builds a fleet of GTM enrichment actors that share one flat, Clay
ready output convention, so their rows join on company_domain with no cleaning
step. Full fleet: apify.com/mambalabs
License
MIT
Questions fréquentes
Qu'est-ce que Instagram Facebook Brand Presence Mapper ?
Resolve a company domain to Instagram, Threads and Facebook accounts and counts.
Comment installer Instagram Facebook Brand Presence Mapper ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add instagram-facebook-brand-presence-mapper -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-meta-brand-presence-mapper@1.2.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Instagram Facebook Brand Presence Mapper ?
Oui. Il attend APIFY_TOKEN, à renseigner dans sa configuration.
Instagram Facebook Brand Presence Mapper est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Instagram Facebook Brand Presence Mapper ?
Il est publié par mambalabsdev. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.