Bol.com MCP server for your agent
To give Claude, Cursor, ChatGPT or another MCP client Bol.com data, add Apify's hosted MCP server with the Actors ticked below as tools (one by default); the URL is in every config. Sign in with your Apify account or pass an API token; each call runs the Actor and returns Bol.com records to the agent.
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/bol-com-product-search-price-and-stock-extractor" --name bol-com-product-search-price-and-stock-extractor - Catalogue Actors
- 1
- In this bundle
- 1
- Official API
- Partners only
- Data checked
- 2026-11-12
Config for your client
Claude Code configterminal or .mcp.json
claude mcp add --transport http bol-com-product-search-price-and-stock-extractor "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/bol-com-product-search-price-and-stock-extractor" - Run the command in your project folder. Add --scope user to make it available in every project.
- Start Claude Code, type /mcp, pick the server and sign in to Apify in the browser window.
- No browser sign-in? Add --header "Authorization: Bearer YOUR_APIFY_TOKEN" to the command instead.
Sign-in: OAuth sign-in on first use, or a token header.
Claude Desktop configclaude_desktop_config.json
{
"mcpServers": {
"bol-com-product-search-price-and-stock-extractor": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--tools",
"fetch-actor-details,dataspryva/bol-com-product-search-price-and-stock-extractor"
],
"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.
- Local alternative (needs Node.js): merge this into claude_desktop_config.json (Settings, Developer, Edit config) and replace YOUR_APIFY_TOKEN.
- Restart Claude Desktop and enable the server from the tools menu in a chat.
Sign-in: Connector with OAuth, or a token in the local config.
Cursor config~/.cursor/mcp.json
{
"mcpServers": {
"bol-com-product-search-price-and-stock-extractor": {
"url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/bol-com-product-search-price-and-stock-extractor",
"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.
- Set APIFY_TOKEN in the environment Cursor starts from, or replace ${env:APIFY_TOKEN} with your token.
- Open Cursor Settings, then MCP, and check that the server lists its tools.
Sign-in: Token read from the APIFY_TOKEN environment variable.
VS Code config.vscode/mcp.json
{
"inputs": [
{
"type": "promptString",
"id": "apify-token",
"description": "Apify API token",
"password": true
}
],
"servers": {
"bol-com-product-search-price-and-stock-extractor": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/bol-com-product-search-price-and-stock-extractor",
"headers": {
"Authorization": "Bearer ${input:apify-token}"
}
}
}
} - Save as .vscode/mcp.json in your workspace.
- Start the server from the file or the MCP servers view. VS Code asks for the token once and stores it securely.
- Use the tools from Copilot Chat in agent mode.
Sign-in: Token prompted once and stored by VS Code.
ChatGPT configPlugins > Add custom MCP server
https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/bol-com-product-search-price-and-stock-extractor - In ChatGPT on the web, open Plugins, select + and choose Add custom MCP server.
- Name it, paste the URL under Connection as the Server URL and choose OAuth for authentication.
- Accept the risk warning (I understand and want to continue), select Create as a plugin, then install the plugin from your plugins, sign in to Apify and use it in a new chat.
Sign-in: OAuth sign-in with your Apify account.
Codex CLI config~/.codex/config.toml
[mcp_servers.bol-com-product-search-price-and-stock-extractor]
url = "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/bol-com-product-search-price-and-stock-extractor"
bearer_token_env_var = "APIFY_TOKEN" - Add the block to ~/.codex/config.toml, or .codex/config.toml in a project.
- Export APIFY_TOKEN in the shell that starts Codex. Or skip the token line and run codex mcp login to sign in.
- Start codex and type /mcp to check that the tools are listed.
Sign-in: Token read from the APIFY_TOKEN environment variable.
Gemini CLI configterminal (writes ~/.gemini/settings.json)
gemini mcp add -t http -s user -H "Authorization: Bearer $APIFY_TOKEN" bol-com-product-search-price-and-stock-extractor "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/bol-com-product-search-price-and-stock-extractor" - 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.
- Start gemini and type /mcp to check that the server is connected and lists its tools.
- Saved by hand, a remote server uses the httpUrl key for streamable HTTP (url means the older SSE transport).
Sign-in: Token header saved by gemini mcp add.
n8n AI Agent configMCP Client Tool node
https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/bol-com-product-search-price-and-stock-extractor - Add an AI Agent node, then attach an MCP Client Tool node to its tool input.
- Paste the URL as the endpoint and choose HTTP Streamable as the transport.
- Choose Bearer auth and create a credential that holds your Apify token.
Sign-in: Bearer auth credential.
Validated, not executed: 7 of 7 checks pass
- 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
Official API or an Actor?
Bol.com limits its official API to approved partners
The Marketing Catalog API is a read-only product information API offered to all affiliates registered with the bol affiliate program; products are identified by EAN. The Retailer API serves bol sellers with a retailer account.
No price for the API is published; access comes with an affiliate or retailer account.
Rate limits are applied and reported in x-ratelimit response headers; fixed figures are not published.
bol Marketing Catalog API (affiliates) and Retailer API (sellers) documentation
bol's general terms page blocked automated checks; API use also falls under the affiliate terms; not legal advice.
Every Bol.com Actor in the catalogue
| Actor | Returns | Fields | Store price | Last update |
|---|---|---|---|---|
| Bol.com Product Search, Price & Stock Extractor | Bol.com products with current price, list price, availability, seller, EAN, rating, images, specifications, reviews, and optional seller… Fields include title, brand, price. | 7 | $0.99 per 1,000 results | 2026-10-21 |
Store links: bol-com-product-search-price-and-stock-extractor
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
Claude Code shows Needs authentication. Why?
The server is added but not signed in. Type /mcp in an interactive session and authenticate, or run claude mcp login with the server name. Headless runs with claude -p cannot complete OAuth, so sign in once interactively or use the --header token variant.
Source: Claude Code MCP documentation
Claude Code warns that a tool result is too large. What can I change?
Claude Code warns above 10,000 tokens of tool output and caps it at 25,000 by default (MAX_MCP_OUTPUT_TOKENS raises it). Ask the agent for fewer results per call, for example a lower result limit for the Actor.
Source: Claude Code MCP documentation
Cursor does not show the server's tools. What should I check?
Open the Output panel and pick MCP Logs to see the connection error. A deeplink install that does nothing usually means an older Cursor build; update it or paste the JSON into mcp.json by hand.
Source: Cursor MCP documentation
Sources
- Apify MCP server documentation, checked 2026-11-10
- bol Marketing Catalog API (affiliates) and Retailer API (sellers) documentation, checked 2026-11-11
- api.bol.com/marketing/docs/catalog-api/ratelimits.html, checked 2026-11-11
- api.bol.com/retailer/public/Retailer-API/retailer-getting-started.html, checked 2026-11-11
- developers.bol.com/en, checked 2026-11-11
- Bol.com terms