MCP Pinterest Brand Presence Mapper

What mcp-pinterest-brand-presence-mapper does

The mcp-pinterest-brand-presence-mapper MCP server connects an MCP client to the Mamba Labs Pinterest Brand Presence Mapper actor on Apify. It accepts a company domain, an optional company name, or a Pinterest handle, then identifies and fetches the relevant business profile.

A completed lookup can provide the profile URL, follower count, following count, pin count, board count, claimed website, verified merchant status, and date of the most recent pin. The output is arranged as a flat row suitable for joining with company data through the shared company_domain field used by Mamba Labs actors.

The result includes a platform status value. ok indicates that the value was retrieved, while not_found, not_extractable, blocked, identity_mismatch, and skipped describe other outcomes. Treat false as a confirmed negative and null as unavailable or unknown; they do not have the same meaning.

How it works

The map_pinterest_brand_presence tool performs discovery when given a domain. An optional company name helps the identity check compare a discovered profile with the intended business. Providing a known Pinterest handle bypasses discovery and goes directly to profile retrieval, which is useful when the domain and handle do not resemble each other.

Pinterest counts are returned as integers when extraction succeeds, so values such as followers, pins, and boards can be compared or added across multiple companies. A successful lookup is cached for seven days by default. Set skipCache to true when a new fetch is required.

Setup and configuration

The mcp-pinterest-brand-presence-mapper MCP server runs through the npm package with npx and requires Node.js 18 or newer. Configure it as an MCP server and provide an Apify API token through the APIFY_TOKEN environment variable. The token can be obtained from the Apify account integrations page.

The main input fields are:

• company_domain: bare domain such as shopify.com.
• company_name: optional business name used to improve discovery and identity matching.
• handle: optional Pinterest username; supplying it skips domain discovery.
• includeFollowerCounts: defaults to true; set it to false for profile URL resolution without follower extraction, which is cheaper and does not need a proxy.
• skipCache: defaults to false; set it to true to ignore a successful seven-day cached result.

Each call consumes Apify credits under the actor's pay-per-event pricing. The server is read-only.

Tools and capabilities

The mcp-pinterest-brand-presence-mapper MCP server exposes one documented tool: map_pinterest_brand_presence. It supports domain-to-account resolution, direct handle lookup, profile and audience-count extraction, merchant-verification checks, website-claim reporting, and last-pin-date reporting. Example uses include checking a company's Pinterest audience, comparing board counts across domains, and determining whether a profile is marked as a verified merchant.

Limitations and notes

Domain discovery can produce an identity_mismatch result when a real Pinterest profile is found but belongs to another entity. In that case, the server does not return that profile's counts. A blocked result may be worth retrying later, while not_extractable means the profile was found but the requested value was unavailable to the actor.

Results depend on Apify access, available credits, and Pinterest data that can be fetched at the time of the request. The project is licensed under MIT.