MCP Tiktok Brand Presence Mapper

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

The mcp-tiktok-brand-presence-mapper MCP server connects an MCP client to the Mamba Labs TikTok Brand Presence Mapper actor on Apify. It accepts a TikTok handle or a company domain and attempts to associate the input with the brand's official TikTok account. An optional company name can improve discovery and is used during identity validation.

The result is a flat, Clay-ready row containing the resolved profile URL and available account details. Depending on the lookup, fields can include follower, following, like, and video counts; verification state; display name; bio; and the outbound link in the bio. TikTok may round larger counts, and the output indicates when counts are approximate.

A guessed profile is not treated as the brand automatically. If the identity check finds that the account belongs to another entity, the result uses identity_mismatch and does not provide counts for that account.

How it works

The available tool is map_tiktok_brand_presence. Use handle as the primary input, with or without @. Supply company_domain when the handle must be discovered or when the supplied handle needs an identity check. company_name is optional but can make matching more accurate.

By default, the lookup fetches the profile page and extracts counts. Setting includeFollowerCounts to false requests profile resolution without fetching the counts, which uses fewer resources. Successful lookups are cached for seven days by default; set skipCache to true when a fresh fetch is needed. escalateOnBlock controls whether a blocked request is escalated after TikTok's bot-detection response.

Read _status before interpreting values. ok, not_found, not_extractable, blocked, identity_mismatch, and skipped distinguish successful, unavailable, blocked, mismatched, and deliberately omitted results. A boolean false means the system checked and found no presence, while null means the answer is unknown.

Setup and configuration

The mcp-tiktok-brand-presence-mapper MCP server requires Node.js 18 or newer and an Apify API token. Configure it as an stdio server by running the npm package with npx and provide the token through the APIFY_TOKEN environment variable:

{
  "mcpServers": {
    "mamba-tiktok-brand-presence-mapper": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-tiktok-brand-presence-mapper"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

The token is obtained from the Apify account integrations page. Calls are pay-per-event and consume Apify credits; check the actor's Apify page for pricing.

Tools and capabilities

• Resolve a TikTok handle to a profile.
• Discover a TikTok account from a company domain.
• Check account identity using a company name or domain.
• Return profile counts, verification, display name, bio, and outbound bio link.
• Request profile resolution without counts.
• Reuse successful results for seven days or force a refresh.

Limitations and notes

The mcp-tiktok-brand-presence-mapper MCP server is read-only. It does not publish, modify, or interact with TikTok accounts. TikTok blocks some requests with bot-detection pages, so a result may have blocked status and be suitable for a later retry. Some profile values may not be available to the fetcher and are then reported as not_extractable rather than inferred.

The service depends on Apify availability, token configuration, and paid actor usage. Do not treat null as proof that a company lacks TikTok presence; use the explicit false result when filtering for confirmed absence. Counts above roughly ten thousand may be rounded by TikTok, with the row indicating that condition.