Connect B&Q Marketplace to Claude via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → B&Q Marketplace, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

B&Q Marketplace + Claude

Run your shop on the B&Q 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 United Kingdom; sign in with the shop API key from your B&Q 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:

B_AND_Q_API_KEY

Step 1 — Get credentials

Countries: the United Kingdom.

Who can sell: B&Q takes applications through the Kingfisher Merchant Hub; the business must be VAT-registered. The connector needs a seller account that B&Q has already opened.

B&Q belongs to Kingfisher, which is why the seller platform is on a Kingfisher address.

Setting up takes about 5 minutes.

1. Sign in to the B&Q seller back office: https://marketplace.kingfisher.com/login.
2. 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 B_AND_Q_API_KEY. The key is sent as is in the Authorization header, without Bearer. Generating a new key invalidates the old one, so any other tool using it stops working.
3. Sellers on B&Q are known to set the shop id, also with a single shop. If your user has more than one shop, set B_AND_Q_SHOP_ID to 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 as shop_id by b_and_q_get_account); to work on several shops, install the connector once per shop. Without it your default shop is used.
4. Install and run b_and_q_get_account: it returns the shop the key belongs to.

Where to start: b_and_q_get_account shows the shop behind the key (id, name, state, currency and channels). For the daily work use b_and_q_list_orders with order_state_codes=WAITING_ACCEPTANCE, b_and_q_list_offers for prices and stock and b_and_q_list_threads for messages that wait for a reply.

Products and competing offers: b_and_q_get_products looks products up in the B&Q catalog by EAN or another reference and returns the marketplace product SKU; b_and_q_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. b_and_q_accept_order accepts (or refuses) every line; after the customer is debited the order moves to SHIPPING. Then b_and_q_update_tracking stores the carrier and tracking number (carrier codes come from b_and_q_list_carriers) and b_and_q_ship_order confirms the shipment (SHIPPED). Later states are TO_COLLECT, RECEIVED, CLOSED, REFUSED and CANCELED. Use b_and_q_list_orders with order_state_codes=WAITING_ACCEPTANCE for the daily to-do list and has_incident=true for open incidents; b_and_q_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 b_and_q_list_order_documents.

Writes: confirm first. b_and_q_accept_order, b_and_q_update_tracking, b_and_q_ship_order, b_and_q_resolve_incident, b_and_q_accept_return, b_and_q_receive_return, b_and_q_update_offers, b_and_q_reply_thread, b_and_q_create_order_thread and b_and_q_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. b_and_q_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): b_and_q_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 (b_and_q_get_offer or b_and_q_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 b_and_q_get_offer_import before reading the offer again. Condition codes for state_code come from b_and_q_list_offer_conditions, logistic class codes from b_and_q_list_logistic_classes.

File imports: b_and_q_import_products (P41) and b_and_q_import_offers (OF01) take the URL of a CSV, XLSX or XML file in the file format B&Q asks for; the connector downloads it and uploads it to B&Q. Track them with b_and_q_list_product_imports / b_and_q_get_product_import and b_and_q_list_offer_imports / b_and_q_get_offer_import.

Returns: b_and_q_list_returns (RT11) lists return requests. Where B&Q lets the shop decide, b_and_q_accept_return accepts or refuses one in WAITING_ACCEPTANCE and b_and_q_receive_return confirms the goods arrived. Refunds stay in the back office.

Messages: b_and_q_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), b_and_q_get_thread reads one with its messages, b_and_q_reply_thread answers (recipient CUSTOMER or OPERATOR, which is B&Q) and b_and_q_create_order_thread opens a new conversation on an order. Reason codes for topics come from b_and_q_list_reasons; leave its locale empty unless you know the marketplace has that language (an inactive locale answers 400).

Money: b_and_q_list_invoices (IV01) lists the accounting documents B&Q issues to the shop and b_and_q_list_transactions (TL02) the transaction lines (sales, commissions, refunds, payouts). If B&Q uses Enhanced Seller Invoicing, IV01 returns no new documents; use b_and_q_list_document_requests (DR11) and the transactions then.

Reference lists: b_and_q_list_channels (country sites), b_and_q_list_carriers, b_and_q_list_shipping_zones, b_and_q_list_shipping_methods and b_and_q_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 B&Q can tighten them. Listing offers and orders is meant for interactive use, product and offer imports at most every 15 minutes, b_and_q_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, 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 Claude

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 shows YOUR_SERVER_ID.

Recommended path: works on claude.ai web without editing any config file.

1. In Claude, open Customize → Connectors.
2. Click +, then Add custom connector.
3. Enter a name, e.g. B&Q Marketplace, and the remote MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Add.
4. Click Connect and sign in to AnythingMCP (OAuth) to allow access.

All tools below appear in your chat: start typing prompts.

Available tools

Example prompts

• "Which B&Q orders are waiting for acceptance, and what is their total value in GBP?"
• "Set the stock of my garden hose reel SKU HR-30M to 40 on B&Q."
• "Mark the incident on line 2 of order 7012345-A as resolved; the customer received the missing screws."
• "Which of my B&Q offers are not active, and what reason does B&Q give?"
• "Show the invoices B&Q issued me this quarter with their commission totals."

FAQ

Does it work with Claude Code as well as Claude Desktop? Yes, point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.

Where do I get the B&Q API key? In the B&Q 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. Sellers on B&Q are known to set the shop id, also with a single shop. With more than one shop, set B_AND_Q_SHOP_ID to the shop this connector should work on.

Who can sell on B&Q, and which countries does it cover? B&Q takes applications through the Kingfisher Merchant Hub; the business must be VAT-registered. The connector covers the United Kingdom. B&Q belongs to Kingfisher, which is why the seller platform is on a Kingfisher address.

Can it cancel orders, refund or delete offers? No tool refunds or cancels an order; do that in the B&Q 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. b_and_q_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.

Next steps

• Connector landing page
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse
• Connect to Microsoft Copilot