Integration and Marketplace Presence Mapper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_marketplace_presenceA | Find which app marketplaces list a company. Give a company domain (for example klaviyo.com), optionally its name, or a list of domains. 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, and returns one row per company with, for each marketplace, the listing URL, listing name, installs, rating, review count, last update, a status (listed, not_found, blocked, skipped), and a match confidence (1.0 linked from the company site, 0.9 listing names the company domain, 0.7 name match only). Companies with no listing come back free with row_status not_listed. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and consumes Apify credits per listing found. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. Its purpose is clearly and narrowly defined by the name and description.
The single tool uses a clear snake_case verb_noun pattern: get_marketplace_presence. No competing conventions are present to create inconsistency.
The server has only one tool, which feels thin for a named 'Integration and Marketplace Presence Mapper' server. While the tool is comprehensive for its specific query, a single-operation surface is borderline for the apparent scope.
The read-only tool returns rich listing data across ten marketplaces, including statuses and confidence scores. It covers the core lookup need, though it lacks companion operations for filtering, pagination, or exporting the results.