com.mambabuilt/mcp-integration-marketplace-presence-mapper

Find which app marketplaces list a company, with installs, ratings, and listing URLs.

OtherTypeScriptv1.0.0

Integration and Marketplace Presence Mapper MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

An MCP server for the Mamba Labs Integration and Marketplace Presence Mapper actor on Apify. Give it a company domain. Each run checks ten app marketplaces and returns one row per company with the listings it found: listing URL, listing name, installs, rating, review count, and last update per marketplace.

What's Inside

What it does

Find which app marketplaces list a company. Give a company domain (for example klaviyo.com), optionally its name, or a list of domains. The actor checks HubSpot App Marketplace, Salesforce AppExchange, Slack Marketplace, Zapier, Shopify App Store, Atlassian Marketplace, Chrome Web Store, Microsoft Marketplace, Google Workspace Marketplace, and the WordPress plugin directory. It reads links on the company's own site first, then matches marketplace catalogs by company name and confirms each match on the listing page. Every listing carries a status and a match confidence: 1.0 when the company site links to it, 0.9 when the listing page names the company domain, 0.7 when only the name matches. A company with no listing comes back free with row_status not_listed.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

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

Restart the client. The get_marketplace_presence tool appears.

Prerequisites

Example prompts

  • "Which app marketplaces list klaviyo.com?"
  • "For gong.io, outreach.io, and pandadoc.com, who is on the HubSpot and Salesforce marketplaces?"
  • "Does docusign.com have a Chrome extension or a Google Workspace add-on, and how many users?"

Tool

get_marketplace_presence. One tool. Example arguments:

{
  "company_domain": "klaviyo.com"
}

Inputs

Every buyer facing input of the live actor, unchanged. Omitted inputs take the actor's own defaults. Give one of company_domain, company_name, or domains.

InputTypeRequiredDescription
company_domainstringnoA company website domain, for example klaviyo.com.
company_namestringnoThe name marketplaces show. Read from the homepage when omitted.
domainsarraynoSeveral company domains. Up to 500 per run.
marketplacesarraynohubspot, appexchange, slack, zapier, shopify, atlassian, chrome_web_store, microsoft, google_workspace, wordpress. Omit for all ten.
max_charge_usdstringnoOptional cost cap for the run.
skipCachestringnotrue checks again instead of the free 7 day cache. Default false.
proxy_modestringnoauto, direct, or residential. Default auto.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
listing-found, per marketplace listing found$0.002$0.0019$0.0018$0.0017
apify-actor-start, per run start$0.002$0.002$0.002$0.002

A company listed on 4 marketplaces is 4 events. Companies with no listing, blocked or skipped marketplaces, and cached rows are free.

Your keys

The actor needs no provider key. It reads public marketplace pages and sitemaps and the company's own website, and holds no key of its own. If a run uses the Apify proxy, that traffic adds nothing to your price: Mamba Labs pays the platform costs of the run. proxy_mode is a reliability setting.

Full actor documentation

apify.com/mambalabs/integration-marketplace-presence-mapper

License

MIT. See LICENSE.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @mambalabsdev/mcp-integration-marketplace-presence-mapper

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "com-mambabuilt-mcp-integration-marketplace-presence-mapper": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-integration-marketplace-presence-mapper"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@mambalabsdev/mcp-integration-marketplace-presence-mappernpm

Compatible MCP Clients

com.mambabuilt/mcp-integration-marketplace-presence-mapper works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More