MCP Tools Directory
← Browse integrations

Developer tools

com.mambabuilt/mcp-tiktok-brand-presence-mapper

Free account · sign-in required

Contact com.mambabuilt/mcp-tiktok-brand-presence-mapper

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

Resolve a TikTok handle or company domain to the brand account with follower counts.

Transport
stdio
Authentication
api-key
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
1.0.0
Package
@mambalabsdev/mcp-tiktok-brand-presence-mapper
Last compatibility test
Not independently tested

Connect your agent

@mambalabsdev/mcp-tiktok-brand-presence-mapper

Publisher README and package manifest reviewed. Identity-mismatch and unknown statuses must remain distinct from a confirmed absence; no profile lookup was executed.

Capabilities: Resolve a brand TikTok account, Return profile and audience metrics, Report identity and retrieval status

Connected profiles

Additional details

Registry identifier

com.mambabuilt/mcp-tiktok-brand-presence-mapper

Source ↗ · Checked 2026-09-17
Published version

1.0.0

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Required configuration names

APIFY_TOKEN

Source ↗ · Checked 2026-09-17
Source artifact

@mambalabsdev/mcp-tiktok-brand-presence-mapper

Source ↗ · Checked 2026-09-19
Source manifest version

1.0.0

Source ↗ · Checked 2026-09-19
Unattended configuration

The publisher documents a client-managed MCP server backed by an Apify actor. It was reviewed from frozen documentation and was not executed.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

An Apify API token is required and configured through APIFY_TOKEN; calls consume Apify credits.

Source ↗ · Checked 2026-09-19
Connection configuration

The reviewed client configuration launches the npm package with npx over the existing stdio connection.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19