Summary
Run your shop on the vtwonen marketplace from an AI agent: orders, acceptance, tracking and shipping, incidents, offers with prices and stock, imports, messages, returns, invoices and transactions. The marketplace sells in the Netherlands and Belgium; sign in with the shop API key from your vtwonen seller back office.
Guided setup
Connect vtwonen Marketplace to Meta Muse in 2 minutes
Start a free trial on AnythingMCP Cloud, connect vtwonen Marketplace in the guided setup, then add your MCP URL to Meta Muse. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for vtwonen Marketplace
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → vtwonen Marketplace, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
vtwonen Marketplace + Meta Muse
Run your shop on the vtwonen marketplace from an AI agent: orders, acceptance, tracking and shipping, incidents, offers with prices and stock, imports, messages, returns, invoices and transactions. The marketplace sells in the Netherlands and Belgium; sign in with the shop API key from your vtwonen seller back office.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
VT_WONEN_API_KEY
Step 1 — Get credentials
Countries: the Netherlands and Belgium. The shop is in Dutch; sellers must deliver free of charge to the Netherlands and Flanders.
Who can sell: vtwonen chooses its suppliers and products through an internal committee; apply by e-mail ([email protected]). Sellers ship from their own stock, offer free delivery and free returns, and answer customer questions within 24 hours. The connector needs a seller account that vtwonen has already opened.
Setting up takes about 5 minutes.
- Sign in to the vtwonen seller back office:
https://shop-partnerplatform.vtwonen.nl/login. - In the back office open your user name (top right) > My user settings > API key and click Generate a new key (or copy the existing key). Paste it into
VT_WONEN_API_KEY. The key is sent as is in theAuthorizationheader, withoutBearer. Generating a new key invalidates the old one, so any other tool using it stops working. - Leave
VT_WONEN_SHOP_IDempty. Only if your user manages several shops on vtwonen, setVT_WONEN_SHOP_IDto the numeric id of the shop this connector should work on (shown on the dashboard of the back office next to Identifier or Shop ID, and returned asshop_idbyvt_wonen_get_account). Without it your default shop is used. - Install and run
vt_wonen_get_account: it returns the shop the key belongs to.
Where to start: vt_wonen_get_account shows the shop behind the key (id, name, state, currency and channels). For the daily work use vt_wonen_list_orders with order_state_codes=WAITING_ACCEPTANCE, vt_wonen_list_offers for prices and stock and vt_wonen_list_threads for messages that wait for a reply.
Products and competing offers: vt_wonen_get_products looks products up in the vtwonen catalog by EAN or another reference and returns the marketplace product SKU; vt_wonen_list_product_offers lists the offers of every shop for given products, best price first, at about 5 calls a minute.
Order workflow: a new order waits in WAITING_ACCEPTANCE. vt_wonen_accept_order accepts (or refuses) every line; after the customer is debited the order moves to SHIPPING. Then vt_wonen_update_tracking stores the carrier and tracking number (carrier codes come from vt_wonen_list_carriers) and vt_wonen_ship_order confirms the shipment (SHIPPED). Later states are TO_COLLECT, RECEIVED, CLOSED, REFUSED and CANCELED. Use vt_wonen_list_orders with order_state_codes=WAITING_ACCEPTANCE for the daily to-do list and has_incident=true for open incidents; vt_wonen_resolve_incident closes an incident on one order line once it is solved. Documents attached to orders (delivery notes, labels, customer invoices) are listed by vt_wonen_list_order_documents.
Writes: confirm first. vt_wonen_accept_order, vt_wonen_update_tracking, vt_wonen_ship_order, vt_wonen_resolve_incident, vt_wonen_accept_return, vt_wonen_receive_return, vt_wonen_update_offers, vt_wonen_reply_thread, vt_wonen_create_order_thread and vt_wonen_import_products act on the live marketplace. Before each call, show the user what will change (order id and lines, tracking number, offer SKU with the old and new price or stock, the message text and recipients) and wait for a yes. Refusing an order line cancels it for good. No tool here refunds, cancels orders or moves money; do that in the back office. vt_wonen_import_offers can delete offers (REPLACE mode deletes every offer missing from the file), so it is installed switched off.
Updating offers (prices and stock): vt_wonen_update_offers (OF24) replaces the whole offer. Every field you leave out is reset: a missing quantity becomes 0, a missing discount or description is deleted. Always read the offer first (vt_wonen_get_offer or vt_wonen_list_offers with sku) and send it back complete with only the intended change: shop_sku, product_id and product_id_type (from product_references), state_code, price, quantity, leadtime_to_ship, logistic_class (its code), min_quantity_alert, description, discount, all_prices, available_started / available_ended (read as available_start_date / available_end_date) and any offer_additional_fields. Leave update_delete empty or update. The call returns an import_id; the change is applied asynchronously, so check it with vt_wonen_get_offer_import before reading the offer again. Condition codes for state_code come from vt_wonen_list_offer_conditions, logistic class codes from vt_wonen_list_logistic_classes.
File imports: vt_wonen_import_products (P41) and vt_wonen_import_offers (OF01) take the URL of a CSV, XLSX or XML file in the file format vtwonen asks for; the connector downloads it and uploads it to vtwonen. Track them with vt_wonen_list_product_imports / vt_wonen_get_product_import and vt_wonen_list_offer_imports / vt_wonen_get_offer_import.
Returns: vt_wonen_list_returns (RT11) lists return requests. Where vtwonen lets the shop decide, vt_wonen_accept_return accepts or refuses one in WAITING_ACCEPTANCE and vt_wonen_receive_return confirms the goods arrived. Refunds stay in the back office.
Messages: vt_wonen_list_threads lists conversations (filter with entity_type=MMP_ORDER and entity_id=<order id> for one order; entity_id without entity_type is refused), vt_wonen_get_thread reads one with its messages, vt_wonen_reply_thread answers (recipient CUSTOMER or OPERATOR, which is vtwonen) and vt_wonen_create_order_thread opens a new conversation on an order. Reason codes for topics come from vt_wonen_list_reasons; leave its locale empty unless you know the marketplace has that language (an inactive locale answers 400).
Money: vt_wonen_list_invoices (IV01) lists the accounting documents vtwonen issues to the shop and vt_wonen_list_transactions (TL02) the transaction lines (sales, commissions, refunds, payouts). If vtwonen uses Enhanced Seller Invoicing, IV01 returns no new documents; use vt_wonen_list_document_requests (DR11) and the transactions then.
Whole catalogue: to read every offer (a stock or price check across the catalogue, counting offers), start an export with vt_wonen_export_offers, poll vt_wonen_get_offer_export_status about once a minute until it is COMPLETED, and read the files one by one with vt_wonen_get_offer_export_file; include_fields keeps only the columns you need. A full export is allowed once a day; for what changed since, pass last_request_date (a differential export, at most once a minute). Do not page through every offer with vt_wonen_list_offers: it is meant for a few offers at a time and answers 429 when paged through a large catalogue.
Several shops: every tool takes an optional shop_id. A user who manages several shops on this marketplace (an agency, or one shop per country) can work on all of them with one install: pass the shop's id on each call and check which shop it is with vt_wonen_get_account and the same shop_id. Without shop_id a call uses VT_WONEN_SHOP_ID, or the user's default shop when that is empty. Ask the user for the ids of their shops; the back office shows them.
Reference lists: vt_wonen_list_channels (country sites), vt_wonen_list_carriers, vt_wonen_list_shipping_zones, vt_wonen_list_shipping_methods and vt_wonen_list_logistic_classes change rarely; read them once per conversation.
Pagination: orders, offers, invoices and product imports page with max (at most 100) and offset. Threads, returns, transactions, document requests and offer imports return a next_page_token; pass it as page_token to get the next page (all other filters are then ignored) until it is missing.
Dates are ISO 8601, e.g. 2026-10-01T00:00:00Z; answers are in UTC.
Rate limits: Each API has its own limit and vtwonen can tighten them. Listing offers and orders is meant for interactive use, product and offer imports at most every 15 minutes, vt_wonen_get_account and the reference lists about once a day. A 429 carries a Retry-After header with the seconds to wait; do not retry in a loop.
Errors: 401 means the key is wrong or was replaced by a newer one, 403 that your user lacks the right for this action, 404 that the order, offer or thread does not exist for this shop or that the marketplace does not use that feature, such as returns, 400 a wrong parameter or an order in the wrong state (the message names it, e.g. ORDER_INVALID_STATE).
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Muse
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.
- In Muse, open Settings → Connectors and choose Add custom connector.
- Paste the MCP server URL
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. - Muse opens the AnythingMCP sign-in page: sign in and approve access.
- In a chat, ask Muse for something that needs the
vtwonen Marketplacetools.
You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:
Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
vt_wonen_get_account | Read the shop behind the API key on this marketplace (A01): shop id and name, state, channels, currency, grade and approval rate, contact… |
vt_wonen_list_orders | List orders (OR11) with their lines, customer, shipping address, prices, state and incidents. Filter by state (e.g. WAITING_ACCEPTANCE for… |
vt_wonen_list_offers | List the shop's offers (OF21): SKU, product, price and discount, all channel prices, quantity in stock, condition, lead time and whether… |
vt_wonen_get_offer | Read one offer in full by its offer id (OF22): every price field, discount, quantity, condition, logistic class, lead time and custom… |
vt_wonen_list_offer_conditions | List the offer conditions (OF61) the marketplace accepts, e.g. new or used, with the code to put in state_code when updating offers |
vt_wonen_list_offer_imports | List offer imports and updates (OF04), from files and from vt_wonen_update_offers: status (WAITING, RUNNING, COMPLETE, FAILED), lines read… |
vt_wonen_get_offer_import | Read the status of one offer import or offer update (OF02) by its import_id, as returned by vt_wonen_update_offers or… |
vt_wonen_export_offers | Start an export of all the shop's offers as files (OF52), the way to read the whole catalogue (every SKU with price and stock) instead of… |
vt_wonen_get_offer_export_status | Status of an offer export started with vt_wonen_export_offers (OF53): PENDING, COMPLETED or FAILED (with error.code and error.detail), and… |
vt_wonen_get_offer_export_file | Read one file of a completed offer export (OF54): the offers with their SKU, product, quantity, prices and the other exported fields, as… |
vt_wonen_list_product_imports | List product imports (P51) with their status (WAITING, RUNNING, SENT, COMPLETE, FAILED, CANCELLED), the transformation counts and the… |
vt_wonen_get_product_import | Read the status of one product import (P42) by its import_id: import status, reason, transformation counts and the integration details… |
vt_wonen_get_products | Look up products in the marketplace catalog by their identifiers (P31), e.g. EAN, and get the marketplace product SKU, title and category.… |
vt_wonen_list_product_offers | List the offers of every shop for given products (P11), sorted by best price, to compare your price with the competition. Give product_ids… |
vt_wonen_list_threads | List message threads (M11) with customers and vtwonen: topic, linked order or offer, participants, last message date and since when a shop… |
vt_wonen_get_thread | Read one message thread (M10) with all its messages, senders, recipients, attachments and the linked order or offer |
vt_wonen_list_returns | List return requests (RT11) with their state, return lines, reason, RMA, tracking and the linked order. Filter by state, order or date.… |
vt_wonen_list_reasons | List the marketplace's reason codes (RE01): incident, cancellation, refund and message reasons, with their labels and whether the shop may… |
vt_wonen_list_carriers | List the carriers the marketplace knows (SH21) with their code, label and tracking URL. Use the code as carrier_code in… |
vt_wonen_list_invoices | List the accounting documents vtwonen issues to the shop (IV01): invoices and credit notes with period, totals with and without tax… |
vt_wonen_list_transactions | List the shop's transaction lines (TL02): order amounts, shipping, commissions, refunds, manual credits and payouts, with amount, type… |
vt_wonen_list_document_requests | List accounting document requests (DR11), used when vtwonen runs Enhanced Seller Invoicing: invoices and credit notes that vtwonen or the… |
vt_wonen_list_order_documents | List the documents attached to one or more orders (OR72): delivery notes, shipping labels, customer invoices and other files, with id, file… |
vt_wonen_list_channels | List the marketplace's sales channels (CH11), usually one per country site, with code and label. Use the codes as channel_codes in… |
vt_wonen_list_shipping_zones | List the active shipping zones of the marketplace (SH11) with code and label, e.g. mainland France or Corsica. Changes rarely: call it… |
vt_wonen_list_shipping_methods | List the active shipping methods of the marketplace (SH12), e.g. standard, express or pick-up, with code, label, whether a tracking number… |
vt_wonen_list_logistic_classes | List the marketplace's logistic classes (SH31), the size or weight bands that decide shipping prices, with code and label. Use the code as… |
vt_wonen_accept_order | Accept or refuse the lines of an order waiting for acceptance (OR21). Every line of the order must be listed. Refusing a line cancels it… |
vt_wonen_update_tracking | Set the carrier and tracking number of an order (OR23). Give carrier_code from vt_wonen_list_carriers, or carrier_name with carrier_url for… |
vt_wonen_ship_order | Confirm that an order in SHIPPING has been shipped (OR24); it moves to SHIPPED and the customer is notified. Set the tracking first with… |
vt_wonen_update_offers | Create or update offers, including price and stock (OF24). Replaces each offer completely: every field left out is reset (a missing… |
vt_wonen_reply_thread | Reply in a message thread (M12) to the customer or vtwonen. The message is delivered at once and cannot be taken back: show the user the… |
vt_wonen_create_order_thread | Start a new message thread on an order (OR43) with the customer, vtwonen or both. The message is delivered at once: show the user the text… |
vt_wonen_resolve_incident | Mark the open incident on one order line as resolved (OR64), once the customer's problem is solved. reason_code must be an INCIDENT_CLOSE… |
vt_wonen_accept_return | Accept or refuse a return request in WAITING_ACCEPTANCE (RT21). Only when vtwonen handles returns in the seller back office and leaves the… |
vt_wonen_receive_return | Confirm that the goods of an accepted return arrived at your warehouse (RT25). The return moves to RECEIVED. Acts on the live marketplace… |
vt_wonen_import_products | Send a product file to the marketplace (P41) to create or enrich products in its catalog. file_url is the address of a CSV, XLSX or XML… |
vt_wonen_import_offers | Import an offer file (OF01) to create, update or delete offers in bulk. REPLACE mode deletes every offer that is not in the file, and… |
Example prompts
- "Which vtwonen orders are waiting for my acceptance?"
- "Which customer questions are older than 24 hours and still have no reply?"
- "Set the stock of my linen cushion cover SKU VTW-LIN-50 to 60 and keep the price."
- "Add PostNL tracking 3SXYZ9876543 to order 6620118-A and confirm the shipment."
- "Which return requests are waiting for my decision?"
FAQ
Where do I get the vtwonen API key, and what if I run several shops? In the vtwonen seller back office: your user name (top right), My user settings, API key, then Generate a new key (or copy the existing key). Generating a new key invalidates the old one. The key belongs to your user, not to one shop: with several shops on vtwonen, set VT_WONEN_SHOP_ID to the shop the connector should use by default, or ask the AI to pass shop_id on each call and work on all your shops with one install. Without either, your default shop is used.
Who can sell on vtwonen, and which countries does it cover? vtwonen chooses its suppliers and products through an internal committee; apply by e-mail ([email protected]). Sellers ship from their own stock, offer free delivery and free returns, and answer customer questions within 24 hours. The connector covers the Netherlands and Belgium. The shop is in Dutch; sellers must deliver free of charge to the Netherlands and Flanders.
Can it check my whole catalogue, and can it cancel orders, refund or delete offers? Yes to the catalogue: for a stock or price check across every offer, the AI starts an export with vt_wonen_export_offers, waits until vt_wonen_get_offer_export_status reports it complete and reads the files with vt_wonen_get_offer_export_file (a full export once a day, changes since a date once a minute). No tool refunds or cancels an order; do that in the vtwonen back office. Refusing a line when accepting an order cancels it for good, so the AI shows you every write and waits for a yes. vt_wonen_import_offers installs switched off, because its REPLACE mode deletes every offer that is missing from the file; switch it on on the connector page only if the AI should use it.
Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.
Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.
Next steps
Was this guide helpful?