Skip to main content
Glama
Sign In
deenesjakoruzh
mcp-meta-brand-presence-mapper

mcp-meta-brand-presence-mapper

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Instagram Facebook Brand Presence Mapper MCP Server

Glama score npm version npm downloads license

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.

Related MCP server: Company Social Presence Mapper MCP Server

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

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

Available Tools

1 tool
map_meta_brand_presenceMap Instagram Threads and Facebook PresenceA
Idempotent

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.

Inputs: handle, platforms, skipCache, company_name, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of misselection or overlap. Its purpose (domain → Meta account resolution) is unambiguous from the name and description.

    Naming Consistency5/5

    The single tool follows a clean verb_noun snake_case pattern (map_meta_brand_presence) that clearly states the action and resource. With one tool there is no convention mixing to penalize.

    Tool Count3/5

    A single tool is thin even for a narrow enrichment server, sitting below the typical 3-15 range. The scope (one read-only resolution call) plausibly justifies it, but there is no separate tool for batched input or per-platform retries.

    Completeness4/5

    The tool covers the stated domain end to end: domain resolution into Instagram, Threads, and Facebook with counts, and it honestly documents Facebook's best-effort limitation. Minor gaps exist—no bulk/multi-domain input, no retry or credential-check companion tool—but core coverage is solid.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers