Summary
Run your shop on The Knot 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 States; sign in with the shop API key from your The Knot seller back office.
Guided setup
Connect The Knot Marketplace to Cursor in 2 minutes
Start a free trial on AnythingMCP Cloud, connect The Knot Marketplace in the guided setup, then add your MCP URL to Cursor. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for The Knot 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 → The Knot Marketplace, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
The Knot Marketplace + Cursor
Run your shop on The Knot 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 States; sign in with the shop API key from your The Knot 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:
THE_KNOT_API_KEY
Step 1 — Get credentials
Countries: the United States.
Who can sell: The Knot chooses the brands it sells in its registry store; no public application page was found, so ask The Knot or your integrator for an introduction. Sellers ship from the United States. The connector needs a seller account that The Knot has already opened.
The seller address of this connector is the one the platform assigns to this retailer; no seller guide names it yet. If your seller back office opens at a different address, tell us in the chat so we can correct it.
Setting up takes about 5 minutes.
- Sign in to The Knot seller back office:
https://knot-prod.mirakl.net/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
THE_KNOT_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
THE_KNOT_SHOP_IDempty. Only if your user manages several shops on The Knot, setTHE_KNOT_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_idbythe_knot_get_account). Without it your default shop is used. - Install and run
the_knot_get_account: it returns the shop the key belongs to.
Where to start: the_knot_get_account shows the shop behind the key (id, name, state, currency and channels). For the daily work use the_knot_list_orders with order_state_codes=WAITING_ACCEPTANCE, the_knot_list_offers for prices and stock and the_knot_list_threads for messages that wait for a reply.
Products and competing offers: the_knot_get_products looks products up in The Knot catalog by EAN or another reference and returns the marketplace product SKU; the_knot_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. the_knot_accept_order accepts (or refuses) every line; after the customer is debited the order moves to SHIPPING. Then the_knot_update_tracking stores the carrier and tracking number (carrier codes come from the_knot_list_carriers) and the_knot_ship_order confirms the shipment (SHIPPED). Later states are TO_COLLECT, RECEIVED, CLOSED, REFUSED and CANCELED. Use the_knot_list_orders with order_state_codes=WAITING_ACCEPTANCE for the daily to-do list and has_incident=true for open incidents; the_knot_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 the_knot_list_order_documents.
Writes: confirm first. the_knot_accept_order, the_knot_update_tracking, the_knot_ship_order, the_knot_resolve_incident, the_knot_accept_return, the_knot_receive_return, the_knot_update_offers, the_knot_reply_thread, the_knot_create_order_thread and the_knot_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. the_knot_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): the_knot_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 (the_knot_get_offer or the_knot_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 the_knot_get_offer_import before reading the offer again. Condition codes for state_code come from the_knot_list_offer_conditions, logistic class codes from the_knot_list_logistic_classes.
File imports: the_knot_import_products (P41) and the_knot_import_offers (OF01) take the URL of a CSV, XLSX or XML file in the file format The Knot asks for; the connector downloads it and uploads it to The Knot. Track them with the_knot_list_product_imports / the_knot_get_product_import and the_knot_list_offer_imports / the_knot_get_offer_import.
Returns: the_knot_list_returns (RT11) lists return requests. Where The Knot lets the shop decide, the_knot_accept_return accepts or refuses one in WAITING_ACCEPTANCE and the_knot_receive_return confirms the goods arrived. Refunds stay in the back office.
Messages: the_knot_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), the_knot_get_thread reads one with its messages, the_knot_reply_thread answers (recipient CUSTOMER or OPERATOR, which is The Knot) and the_knot_create_order_thread opens a new conversation on an order. Reason codes for topics come from the_knot_list_reasons; leave its locale empty unless you know the marketplace has that language (an inactive locale answers 400).
Money: the_knot_list_invoices (IV01) lists the accounting documents The Knot issues to the shop and the_knot_list_transactions (TL02) the transaction lines (sales, commissions, refunds, payouts). If The Knot uses Enhanced Seller Invoicing, IV01 returns no new documents; use the_knot_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 the_knot_export_offers, poll the_knot_get_offer_export_status about once a minute until it is COMPLETED, and read the files one by one with the_knot_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 the_knot_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 the_knot_get_account and the same shop_id. Without shop_id a call uses THE_KNOT_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: the_knot_list_channels (country sites), the_knot_list_carriers, the_knot_list_shipping_zones, the_knot_list_shipping_methods and the_knot_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 The Knot can tighten them. Listing offers and orders is meant for interactive use, product and offer imports at most every 15 minutes, the_knot_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 Cursor
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.
Cursor reads MCP servers from ~/.cursor/mcp.json. Add this entry:
{
"mcpServers": {
"anythingmcp": {
"url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of
YOUR_MCP_API_KEY. - Save the file and restart Cursor.
- Open Cursor → Settings → MCP and check that
anythingmcpis listed and connected. - Start chatting — the agent can now call the
The Knot Marketplacetools.
Available tools
| Tool | What it does |
|---|---|
the_knot_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… |
the_knot_list_orders | List orders (OR11) with their lines, customer, shipping address, prices, state and incidents. Filter by state (e.g. WAITING_ACCEPTANCE for… |
the_knot_list_offers | List the shop's offers (OF21): SKU, product, price and discount, all channel prices, quantity in stock, condition, lead time and whether… |
the_knot_get_offer | Read one offer in full by its offer id (OF22): every price field, discount, quantity, condition, logistic class, lead time and custom… |
the_knot_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 |
the_knot_list_offer_imports | List offer imports and updates (OF04), from files and from the_knot_update_offers: status (WAITING, RUNNING, COMPLETE, FAILED), lines read… |
the_knot_get_offer_import | Read the status of one offer import or offer update (OF02) by its import_id, as returned by the_knot_update_offers or… |
the_knot_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… |
the_knot_get_offer_export_status | Status of an offer export started with the_knot_export_offers (OF53): PENDING, COMPLETED or FAILED (with error.code and error.detail), and… |
the_knot_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… |
the_knot_list_product_imports | List product imports (P51) with their status (WAITING, RUNNING, SENT, COMPLETE, FAILED, CANCELLED), the transformation counts and the… |
the_knot_get_product_import | Read the status of one product import (P42) by its import_id: import status, reason, transformation counts and the integration details… |
the_knot_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.… |
the_knot_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… |
the_knot_list_threads | List message threads (M11) with customers and The Knot: topic, linked order or offer, participants, last message date and since when a shop… |
the_knot_get_thread | Read one message thread (M10) with all its messages, senders, recipients, attachments and the linked order or offer |
the_knot_list_returns | List return requests (RT11) with their state, return lines, reason, RMA, tracking and the linked order. Filter by state, order or date.… |
the_knot_list_reasons | List the marketplace's reason codes (RE01): incident, cancellation, refund and message reasons, with their labels and whether the shop may… |
the_knot_list_carriers | List the carriers the marketplace knows (SH21) with their code, label and tracking URL. Use the code as carrier_code in… |
the_knot_list_invoices | List the accounting documents The Knot issues to the shop (IV01): invoices and credit notes with period, totals with and without tax… |
the_knot_list_transactions | List the shop's transaction lines (TL02): order amounts, shipping, commissions, refunds, manual credits and payouts, with amount, type… |
the_knot_list_document_requests | List accounting document requests (DR11), used when The Knot runs Enhanced Seller Invoicing: invoices and credit notes that The Knot or the… |
the_knot_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… |
the_knot_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… |
the_knot_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… |
the_knot_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… |
the_knot_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… |
the_knot_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… |
the_knot_update_tracking | Set the carrier and tracking number of an order (OR23). Give carrier_code from the_knot_list_carriers, or carrier_name with carrier_url for… |
the_knot_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… |
the_knot_update_offers | Create or update offers, including price and stock (OF24). Replaces each offer completely: every field left out is reset (a missing… |
the_knot_reply_thread | Reply in a message thread (M12) to the customer or The Knot. The message is delivered at once and cannot be taken back: show the user the… |
the_knot_create_order_thread | Start a new message thread on an order (OR43) with the customer, The Knot or both. The message is delivered at once: show the user the… |
the_knot_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… |
the_knot_accept_return | Accept or refuse a return request in WAITING_ACCEPTANCE (RT21). Only when The Knot handles returns in the seller back office and leaves the… |
the_knot_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… |
the_knot_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… |
the_knot_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 The Knot orders are waiting for my acceptance, and what are they worth in USD?"
- "Set the stock of my linen table runner SKU TK-RUN-90 to 35 and keep the price."
- "Add UPS tracking 1Z999AA10123456825 to order 2201234-A and confirm the shipment."
- "Which customer messages still need a reply?"
- "Export my catalogue and list every offer with fewer than 5 units in stock."
FAQ
Where do I get The Knot API key, and what if I run several shops? In The Knot 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 The Knot, set THE_KNOT_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 The Knot, and which countries does it cover? The Knot chooses the brands it sells in its registry store; no public application page was found, so ask The Knot or your integrator for an introduction. Sellers ship from the United States. The connector covers the United States. The seller address of this connector is the one the platform assigns to this retailer; no seller guide names it yet. If your seller back office opens at a different address, tell us in the chat so we can correct it.
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 the_knot_export_offers, waits until the_knot_get_offer_export_status reports it complete and reads the files with the_knot_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 Knot 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. the_knot_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.
Does Cursor support custom MCP servers on the free tier? Yes — MCP is available on Hobby, Pro and Business plans.
Next steps
Was this guide helpful?