Chinese B2B Supplier & Product Finder by Province: MCP config, n8n workflow and API
Product and supplier records from Made-in-China.com with price tiers, MOQ, specifications, supplier firmographics, audit metadata, contact page fields, and a computed lead score.
Fastest route, in Claude Code:
claude mcp add --transport http chinese-b2b-supplier-and-product-finder "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder" One click, signs in with Apify on first use:
Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):
npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder" --name chinese-b2b-supplier-and-product-finder Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
- MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
- n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- example input: 5 of 5 (All 1 required input field is present; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
- code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
- SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)
What a run costs
Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.
| Results in one run | Start | Results | Run total |
|---|---|---|---|
| 10 | $0.40 | $0.010 | $0.41 |
| 100 | $0.40 | $0.10 | $0.50 |
| 1,000 | $0.40 | $0.99 | $1.39 |
Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.
MCP config
One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:
Claude Code configterminal or .mcp.json
claude mcp add --transport http chinese-b2b-supplier-and-product-finder "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder" Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup
Claude Desktop configclaude_desktop_config.json
{
"mcpServers": {
"chinese-b2b-supplier-and-product-finder": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--tools",
"fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
} Easiest: open Customize, then Connectors, choose Add custom connector, paste the server URL (the ChatGPT tab shows it on its own) and sign in to Apify. Full Claude Desktop setup
Cursor config~/.cursor/mcp.json
{
"mcpServers": {
"chinese-b2b-supplier-and-product-finder": {
"url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder",
"headers": {
"Authorization": "Bearer ${env:APIFY_TOKEN}"
}
}
}
} Save as ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project. Merge with servers you already have. Full Cursor setup
VS Code config.vscode/mcp.json
{
"inputs": [
{
"type": "promptString",
"id": "apify-token",
"description": "Apify API token",
"password": true
}
],
"servers": {
"chinese-b2b-supplier-and-product-finder": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder",
"headers": {
"Authorization": "Bearer ${input:apify-token}"
}
}
}
} Save as .vscode/mcp.json in your workspace. Full VS Code setup
ChatGPT configPlugins > Add custom MCP server
https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder In ChatGPT on the web, open Plugins, select + and choose Add custom MCP server. Full ChatGPT setup
Codex CLI config~/.codex/config.toml
[mcp_servers.chinese-b2b-supplier-and-product-finder]
url = "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder"
bearer_token_env_var = "APIFY_TOKEN" Add the block to ~/.codex/config.toml, or .codex/config.toml in a project. Full Codex CLI setup
Gemini CLI configterminal (writes ~/.gemini/settings.json)
gemini mcp add -t http -s user -H "Authorization: Bearer $APIFY_TOKEN" chinese-b2b-supplier-and-product-finder "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder" Export APIFY_TOKEN first: the shell expands it and Gemini CLI saves the header, token included, in plain text in ~/.gemini/settings.json (keep that file private). In PowerShell write $env:APIFY_TOKEN instead of $APIFY_TOKEN. Drop -s user to save it in the project's .gemini/settings.json. Full Gemini CLI setup
n8n AI Agent configMCP Client Tool node
https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder Add an AI Agent node, then attach an MCP Client Tool node to its tool input. Full n8n AI Agent setup
Tools your agent gets
Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).
fetch-actor-detailsreads the input schemadataspryva--chinese-b2b-supplier-and-product-finderruns the Actor and returns its resultsget-actor-runchecks a run's statusget-dataset-itemsreads a run's resultsget-key-value-store-recordreads a stored record such as a file or summaryabort-actor-runstops a run that is still going
n8n workflow
A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.
- Run by hand
- Every day
- Run Apify Actor
n8n workflowchinese-b2b-supplier-and-product-finder.n8n.json
{
"name": "Chinese B2B Supplier & Product Finder by Province to n8n only",
"nodes": [
{
"id": "95f415b2-199b-45ec-a7d8-f1491d63fddb",
"name": "Run by hand",
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
0,
0
],
"parameters": {}
},
{
"id": "40fb8e72-e166-4a3e-a555-45db7cf5decb",
"name": "Every day",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
0,
200
],
"parameters": {
"rule": {
"interval": [
{
"triggerAtHour": 8
}
]
}
},
"notes": "Activate the workflow to run on this schedule."
},
{
"id": "cdb4d76e-073b-4cb7-ac1f-bf929321242b",
"name": "Run Apify Actor",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
260,
100
],
"parameters": {
"method": "POST",
"url": "https://api.apify.com/v2/actors/dataspryva~chinese-b2b-supplier-and-product-finder/run-sync-get-dataset-items",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\n \"mode\": \"searchProducts\",\n \"searchQueries\": [\n \"industrial pump\"\n ],\n \"goldSupplierOnly\": false,\n \"auditedSupplierOnly\": false,\n \"leadingFactoryOnly\": false,\n \"securedTradingOnly\": false,\n \"sampleAvailableOnly\": false,\n \"maxItems\": 3,\n \"maxPagesPerQuery\": 1,\n \"includeProductDetails\": false,\n \"includeSupplierProfile\": false,\n \"includeContactDetails\": false\n}",
"options": {
"timeout": 310000
}
},
"notes": "Actor: dataspryva/chinese-b2b-supplier-and-product-finder. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
"notesInFlow": false
},
{
"id": "49a7022a-7ccf-4bde-a2f3-1fc7b89caa87",
"name": "Setup",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
0,
-370
],
"parameters": {
"content": "## Chinese B2B Supplier & Product Finder by Province\n\nSource: [dataspryva/chinese-b2b-supplier-and-product-finder](https://apify.com/dataspryva/chinese-b2b-supplier-and-product-finder) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
"height": 340,
"width": 460,
"color": 6
}
}
],
"connections": {
"Run by hand": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
},
"Every day": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
}
},
"pinData": {},
"active": false,
"settings": {
"executionOrder": "v1"
},
"meta": {
"templateCredsSetupCompleted": false
},
"tags": []
} Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.
All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.
Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).
Download the long-run workflow11 of 11 checks pass, not executed
Call it from code
Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.
curl
curl -X POST "https://api.apify.com/v2/actors/dataspryva~chinese-b2b-supplier-and-product-finder/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"mode":"searchProducts","searchQueries":["industrial pump"],"goldSupplierOnly":false,"auditedSupplierOnly":false,"leadingFactoryOnly":false,"securedTradingOnly":false,"sampleAvailableOnly":false,"maxItems":3,"maxPagesPerQuery":1,"includeProductDetails":false,"includeSupplierProfile":false,"includeContactDetails":false}' Install: pip install "apify-client>=3"
Python
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run_input = {
"mode": "searchProducts",
"searchQueries": [
"industrial pump",
],
"goldSupplierOnly": False,
"auditedSupplierOnly": False,
"leadingFactoryOnly": False,
"securedTradingOnly": False,
"sampleAvailableOnly": False,
"maxItems": 3,
"maxPagesPerQuery": 1,
"includeProductDetails": False,
"includeSupplierProfile": False,
"includeContactDetails": False,
}
run = client.actor("dataspryva/chinese-b2b-supplier-and-product-finder").call(run_input=run_input)
if run is None:
raise RuntimeError("The Actor run could not be started")
print(run.status, "dataset", run.default_dataset_id)
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item) Install: npm install apify-client
JavaScript
import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
"mode": "searchProducts",
"searchQueries": [
"industrial pump"
],
"goldSupplierOnly": false,
"auditedSupplierOnly": false,
"leadingFactoryOnly": false,
"securedTradingOnly": false,
"sampleAvailableOnly": false,
"maxItems": 3,
"maxPagesPerQuery": 1,
"includeProductDetails": false,
"includeSupplierProfile": false,
"includeContactDetails": false
};
const run = await client.actor("dataspryva/chinese-b2b-supplier-and-product-finder").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]); Example input
These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.
Actor inputinput.json
{
"mode": "searchProducts",
"searchQueries": [
"industrial pump"
],
"goldSupplierOnly": false,
"auditedSupplierOnly": false,
"leadingFactoryOnly": false,
"securedTradingOnly": false,
"sampleAvailableOnly": false,
"maxItems": 3,
"maxPagesPerQuery": 1,
"includeProductDetails": false,
"includeSupplierProfile": false,
"includeContactDetails": false
} | Field | Type | What it does |
|---|---|---|
mode required | string (6 options) | What to scrape from Made-in-China.com. |
searchQueries | array | One or more product or supplier keywords. Used by 'Search products' and 'Find suppliers' modes (e.g. 'industrial pump', 'LED lights'). |
categoryPaths | array | Made-in-China.com catalog paths (or full catalog URLs) to browse in 'Browse a product category' mode, e.g. 'Agriculture-Food-Catalog/Beverage'. |
productUrls | array | Product page URLs or product IDs to scrape in 'Scrape these product URLs/IDs' mode. A bare ID is resolved through the site's own search. |
supplierUrls | array | Supplier storefront URLs or subdomains, e.g. 'allslorm.en.made-in-china.com' or just 'allslorm'. Used by 'Scrape these supplier storefronts' and 'Scrape a supplier's catalog'. |
province | string (35 options) | Only return listings whose supplier is located in this Chinese province, municipality, or region. Leave blank for no filter. |
businessType | string (5 options) | Only return suppliers of this business type. Leave blank for no filter. Used by product and supplier search modes. |
goldSupplierOnly | boolean | Only return listings from suppliers with a Gold Member, Diamond Member, or higher paid membership badge. |
auditedSupplierOnly | boolean | Only return listings whose supplier carries an 'Audited Supplier' badge from an independent inspection agency. |
leadingFactoryOnly | boolean | Only return listings whose supplier holds an 'Industry-leading Audited Factory' badge. |
securedTradingOnly | boolean | Only return listings that offer Secured Trading (payment protection and after-sales support through Made-in-China.com). |
rdCapacity | string (5 options) | Only return products from suppliers with this R&D or production capability. Leave blank for no filter. |
certification | string (6 options) | Only return products from suppliers who advertise this quality or safety certification. Leave blank for no filter. |
sampleAvailableOnly | boolean | Only return products whose supplier offers a paid sample order ('Buy Sample'). |
maxItems | integer | Maximum number of records to return across all keywords, categories, or URLs. |
maxPagesPerQuery | integer | Maximum listing pages to walk for each keyword, category, or supplier catalog. Each page holds about 24-30 records. |
includeProductDetails | boolean | Open each product page to add description, specifications, price tiers, images, video, categories, FAQ, and deeper supplier data. Adds one request per product. |
includeSupplierProfile | boolean | Open supplier storefront and company-profile pages to add firmographics, trade terms, audit report, product groups, and verification data. Adds requests per supplier. |
includeContactDetails | boolean | Open the public contact page in supplier modes to add contact person, position, postal code, and showroom URL. Phone and email are not public. |
3 more optional fields on the Store input tab.
What your agent receives
Each run returns a list of records. The Actor publishes 17 fields, starting with title, priceMin, priceMax, priceCurrency.
| Field |
|---|
title |
priceMin |
priceMax |
priceCurrency |
minOrder |
supplier |
supplierProvince |
supplierRating |
auditedSupplier |
productUrl |
7 more fields
| Field |
|---|
businessType |
membership |
employees |
leadScore |
supplierUrl |
recordType |
price |
Agent skill
A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.
SKILL.mdchinese-b2b-supplier-and-product-finder/SKILL.md
---
name: chinese-b2b-supplier-and-product-finder
description: "Product and supplier records from Made-in-China.com with price tiers, MOQ, specifications, supplier firmographics, audit metadata, contact page fields, and a computed lead score. Runs the Apify Actor dataspryva/chinese-b2b-supplier-and-product-finder. Use when the user needs Chinese B2B Supplier data with fields such as title, priceMin, priceMax, priceCurrency, minOrder, supplier and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
actor: "dataspryva/chinese-b2b-supplier-and-product-finder"
store-url: "https://apify.com/dataspryva/chinese-b2b-supplier-and-product-finder"
---
# Chinese B2B Supplier & Product Finder by Province
Use this skill to fetch Chinese B2B Supplier data with the Apify Actor `dataspryva/chinese-b2b-supplier-and-product-finder` and work with the returned rows.
## Before running
1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.
## Input fields
| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `searchProducts`, `searchSuppliers`, `categoryBrowse`, `productDetails`, `supplierDetails`, `supplierProducts`, required | What to scrape from Made-in-China.com. |
| `searchQueries` | array | One or more product or supplier keywords. Used by 'Search products' and 'Find suppliers' modes (e.g. 'industrial pump', 'LED lights'). |
| `categoryPaths` | array | Made-in-China.com catalog paths (or full catalog URLs) to browse in 'Browse a product category' mode, e.g. 'Agriculture-Food-Catalog/Beverage'. |
| `productUrls` | array | Product page URLs or product IDs to scrape in 'Scrape these product URLs/IDs' mode. A bare ID is resolved through the site's own search. |
| `supplierUrls` | array | Supplier storefront URLs or subdomains, e.g. 'allslorm.en.made-in-china.com' or just 'allslorm'. Used by 'Scrape these supplier storefronts' and 'Scrape a supplier's catalog'. |
| `province` | string | Only return listings whose supplier is located in this Chinese province, municipality, or region. Leave blank for no filter. |
| `businessType` | one of `Manufacturer/Factory`, `Trading Company`, `Group Corporation`, `Other` | Only return suppliers of this business type. Leave blank for no filter. Used by product and supplier search modes. |
| `goldSupplierOnly` | boolean | Only return listings from suppliers with a Gold Member, Diamond Member, or higher paid membership badge. |
| `auditedSupplierOnly` | boolean | Only return listings whose supplier carries an 'Audited Supplier' badge from an independent inspection agency. |
| `leadingFactoryOnly` | boolean | Only return listings whose supplier holds an 'Industry-leading Audited Factory' badge. |
| `securedTradingOnly` | boolean | Only return listings that offer Secured Trading (payment protection and after-sales support through Made-in-China.com). |
| `rdCapacity` | one of `OEM`, `ODM`, `Own Brand`, `Others` | Only return products from suppliers with this R&D or production capability. Leave blank for no filter. |
| `certification` | one of `CE`, `ISO`, `RoHS`, `CCC`, `ISO9001` | Only return products from suppliers who advertise this quality or safety certification. Leave blank for no filter. |
| `sampleAvailableOnly` | boolean | Only return products whose supplier offers a paid sample order ('Buy Sample'). |
Example `input.json` (the Actor's published prefill):
```json
{
"mode": "searchProducts",
"searchQueries": [
"industrial pump"
],
"goldSupplierOnly": false,
"auditedSupplierOnly": false,
"leadingFactoryOnly": false,
"securedTradingOnly": false,
"sampleAvailableOnly": false,
"maxItems": 3,
"maxPagesPerQuery": 1,
"includeProductDetails": false,
"includeSupplierProfile": false,
"includeContactDetails": false
}
```
## Run
```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~chinese-b2b-supplier-and-product-finder/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d @input.json > results.json
```
The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~chinese-b2b-supplier-and-product-finder/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.
## Output
Each item is one record. Published fields include: `title`, `priceMin`, `priceMax`, `priceCurrency`, `minOrder`, `supplier`, `supplierProvince`, `supplierRating`, `auditedSupplier`, `productUrl`, `businessType`, `membership`, `employees`, `leadScore`, `supplierUrl`, `recordType`, `price`.
Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.
- Claude Code: save it as
~/.claude/skills/chinese-b2b-supplier-and-product-finder/SKILL.md, or.claude/skills/chinese-b2b-supplier-and-product-finder/SKILL.mdin a project. - Codex and other agents:
~/.agents/skills/chinese-b2b-supplier-and-product-finder/SKILL.md, or.agents/skills/chinese-b2b-supplier-and-product-finder/in a project. - Or let the skills CLI place it for your agent:
npx skills add https://recipeforagents.com --skill chinese-b2b-supplier-and-product-finder - Set
APIFY_TOKENin the agent's environment.
Troubleshooting
Why does the client say Unauthorized or invalid token?
Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.
Source: Apify MCP server README
Why did my agent's tool list change after an update?
Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.
Source: Apify MCP server README
What happens when the agent sends input the Actor rejects?
The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.
Source: Apify MCP server README
Questions
How do I connect Chinese B2B Supplier & Product Finder by Province to Claude?
In Claude Code run: claude mcp add --transport http chinese-b2b-supplier-and-product-finder "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/chinese-b2b-supplier-and-product-finder and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.
What input does Chinese B2B Supplier & Product Finder by Province need?
The published input schema requires mode. The example on this page uses the Actor's own Store prefill.
What does Chinese B2B Supplier & Product Finder by Province cost to run?
The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.
Which tools does the MCP config give my agent?
6 tools: fetch-actor-details, dataspryva--chinese-b2b-supplier-and-product-finder, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run. Apify's MCP server listed them for this exact URL on 2026-11-11.
More on the products and prices shelf
Amazon Review Aggregates & Extended History Scraper
Collect Amazon customer reviews and rating summaries by product URL, ASIN, or keyword across 19…
28 fields$0.99 per 1,000 resultsAmazon Deals Grid Tracker by Category & Discount
Pull Amazon's Today's Deals grid across 23 marketplaces, with deal price, list price, savings…
8 fields$0.99 per 1,000 resultsAmazon Multi-Domain Product Price & Detail Scraper
Pull pricing, ratings, seller, variant and technical detail for Amazon products by URL or ASIN, across 21…
9 fields$0.99 per 1,000 resultsEtsy Product Listings & Shop Research Scraper
Collect Etsy product listings from keyword searches, category pages, and individual shops, with prices…
8 fields$0.99 per 1,000 resultsLowe's Price, Stock & Specification Scraper
Search Lowe's products by keyword, browse a category, or fetch details by item ID or URL. Get price…
10 fields$0.99 per 1,000 resultsM.Video Russia Electronics Product & Review Scraper
Search, browse categories, or fetch full product detail from mvideo.ru, including price, rating…
9 fields$0.99 per 1,000 results