Manufacturer and Supplier Finder 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 |
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 |
|---|---|
| find_suppliersA | Find manufacturers, wholesalers, and distributors for a product in one of 20 countries. Give product (for example cast iron cookware) and optionally country, role, and max_results. The actor searches Google, checks each company's own website with the Mamba Labs Website Phrase and Business Model Classifier, and returns one row per supplier: company_name, domain, website_url, roles_detected, product_evidence_text and role_evidence_text quoted from the site with their page URLs, and a 0.6 to 0.95 confidence. Directories, marketplaces, and social networks are never returned. When nothing qualifies, one free summary row says why. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per supplier returned plus the classifier's price per site checked. |
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
With only one tool, there is no possibility of confusion with another operation. Its purpose is clearly stated as supplier discovery.
The sole tool follows a clear verb_noun snake_case convention (find_suppliers). There are no inconsistent names to compare against.
A single tool is thin even for a narrow discovery server. The parameterization is rich, but the surface offers no companion operations such as listing supported countries, roles, or retrieving supplier details.
The core discovery workflow is covered, including country, role, max_results, and evidence-rich rows. However, there are notable gaps: no follow-up supplier detail retrieval, no supported-country/role listing, and no batch or refinement operations.