MCP Meta Brand Presence Mapper

What mcp-meta-brand-presence-mapper MCP server does

mcp-meta-brand-presence-mapper resolves a company domain to Instagram, Threads, and Facebook accounts. It can also accept an Instagram handle, with or without @, to skip Instagram discovery. The result is a flat row designed for downstream enrichment workflows, including rows that join on company_domain.

The server is read-only. Instagram and Threads can return follower and post counts, while Facebook lookup is best effort because anonymous requests may encounter a Meta login wall. A blocked Facebook result means the profile could not be accessed; it does not mean the page has zero followers or posts.

How it works

The MCP tool starts the Mamba Labs Meta Brand Presence Mapper actor on Apify. When given a domain, the actor performs profile discovery and then fetches the selected platform data. Supplying an Instagram handle skips that discovery step and also supplies the Threads handle, since the implementation treats the Threads handle as the Instagram handle.

Use platforms to choose among Instagram, Threads, and Facebook. All three are selected by default. includeFollowerCounts defaults to true; setting it to false resolves profile URLs without fetching counts, which reduces cost and does not require a proxy. Successful lookups are cached for seven days unless skipCache is set to true.

Each platform has a _status value. ok indicates parsed data, not_found means no profile was found, not_extractable means the profile exists but the requested value was unavailable, and blocked means the platform refused access. identity_mismatch identifies a profile that belongs to someone else, while skipped indicates that the platform was not requested. Treat false as a confirmed negative and null as unknown.

Setup and configuration

mcp-meta-brand-presence-mapper runs through npx and requires Node.js 18 or newer. Configure it in an MCP client with the package @mambalabsdev/mcp-meta-brand-presence-mapper and provide APIFY_TOKEN in the server environment. The token comes from the Apify account integrations page.

The main tool is map_meta_brand_presence. Its required practical input is a company_domain such as shopify.com, or an optional handle. company_name is optional and improves discovery accuracy by supporting the identity check. The actor charges Apify credits per call, so platform selection, count fetching, and cache settings affect how much work each request performs.

Tools and capabilities

The server exposes one documented tool:

• map_meta_brand_presence: discovers or fetches Instagram, Threads, and Facebook profiles for a company, with optional follower counts, post counts, platform filtering, identity context, and cache bypassing.

Instagram and Threads counts include both a rounded integer and the platform’s display string. Facebook results may be unavailable because of access restrictions. The tool accepts company_domain, company_name, handle, platforms, includeFollowerCounts, and skipCache.

Limitations and notes

mcp-meta-brand-presence-mapper depends on the Apify actor and consumes credits for calls. Facebook is less reliable than the other two surfaces because anonymous clients can receive a login wall. A blocked or null value should therefore be treated as an unavailable result rather than evidence that a company has no Facebook presence.

Counts are not necessarily exact raw totals: Meta rounds Instagram and Threads counts, and the server preserves the platform’s display text alongside the rounded number. Use skipCache when a fresh lookup is needed; otherwise, successful results may be reused for seven days.