Find which app marketplaces list a company, with installs, ratings, and listing URLs.
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.
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.
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.
APIFY_TOKEN. The server lists its tool without a token; a call needs one.get_marketplace_presence. One tool. Example arguments:
{
"company_domain": "klaviyo.com"
}
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.
| Input | Type | Required | Description |
|---|---|---|---|
company_domain | string | no | A company website domain, for example klaviyo.com. |
company_name | string | no | The name marketplaces show. Read from the homepage when omitted. |
domains | array | no | Several company domains. Up to 500 per run. |
marketplaces | array | no | hubspot, appexchange, slack, zapier, shopify, atlassian, chrome_web_store, microsoft, google_workspace, wordpress. Omit for all ten. |
max_charge_usd | string | no | Optional cost cap for the run. |
skipCache | string | no | true checks again instead of the free 7 day cache. Default false. |
proxy_mode | string | no | auto, direct, or residential. Default auto. |
Pay per event on Apify, billed to your Apify account. Prices in USD.
| Event | Free plan | Bronze | Silver | Gold |
|---|---|---|---|---|
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.
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.
apify.com/mambalabs/integration-marketplace-presence-mapper
MIT. See LICENSE.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @mambalabsdev/mcp-integration-marketplace-presence-mapperMerge 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.
{
"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@mambalabsdev/mcp-integration-marketplace-presence-mappernpmcom.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.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..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.