Connector guide13-minute read38 MCP tools7 languages

Connect Sprinter to Meta Muse via MCP: Orders and Stock

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.

HCBy HelpCode teamUpdated 13 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

Sprinter Marketplace

Sprinter Marketplace

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.

tools

38

Region

ES

Category

E-commerce

Authentication

API Key

Required env vars

SPRINTER_API_KEY
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.

Guided setup

Connect Sprinter Marketplace to Meta Muse in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Sprinter 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 Sprinter Marketplace

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

Sprinter Marketplace · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

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

Sprinter Marketplace + Meta Muse

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter 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:

SPRINTER_API_KEY

Step 1 — Get credentials

Countries: Spain and Portugal. Spain and Portugal are two sales channels of the same shop, each with its own prices.

Who can sell: Sprinter takes applications through the form on its seller page; fees and commission are agreed with Sprinter. The connector needs a seller account that Sprinter has already opened.

Setting up takes about 5 minutes.

  1. Sign in to the Sprinter seller back office: https://sprinter-prod.mirakl.net/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 SPRINTER_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. Leave SPRINTER_SHOP_ID empty. Only if your user manages several shops on Sprinter, set SPRINTER_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 sprinter_get_account). Without it your default shop is used.
  4. Install and run sprinter_get_account: it returns the shop the key belongs to.

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

Products and competing offers: sprinter_get_products looks products up in the Sprinter catalog by EAN or another reference and returns the marketplace product SKU; sprinter_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. sprinter_accept_order accepts (or refuses) every line; after the customer is debited the order moves to SHIPPING. Then sprinter_update_tracking stores the carrier and tracking number (carrier codes come from sprinter_list_carriers) and sprinter_ship_order confirms the shipment (SHIPPED). Later states are TO_COLLECT, RECEIVED, CLOSED, REFUSED and CANCELED. Use sprinter_list_orders with order_state_codes=WAITING_ACCEPTANCE for the daily to-do list and has_incident=true for open incidents; sprinter_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 sprinter_list_order_documents.

Writes: confirm first. sprinter_accept_order, sprinter_update_tracking, sprinter_ship_order, sprinter_resolve_incident, sprinter_accept_return, sprinter_receive_return, sprinter_update_offers, sprinter_reply_thread, sprinter_create_order_thread and sprinter_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. sprinter_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): sprinter_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 (sprinter_get_offer or sprinter_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 sprinter_get_offer_import before reading the offer again. Condition codes for state_code come from sprinter_list_offer_conditions, logistic class codes from sprinter_list_logistic_classes.

File imports: sprinter_import_products (P41) and sprinter_import_offers (OF01) take the URL of a CSV, XLSX or XML file in the file format Sprinter asks for; the connector downloads it and uploads it to Sprinter. Track them with sprinter_list_product_imports / sprinter_get_product_import and sprinter_list_offer_imports / sprinter_get_offer_import.

Returns: sprinter_list_returns (RT11) lists return requests. Where Sprinter lets the shop decide, sprinter_accept_return accepts or refuses one in WAITING_ACCEPTANCE and sprinter_receive_return confirms the goods arrived. Refunds stay in the back office.

Messages: sprinter_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), sprinter_get_thread reads one with its messages, sprinter_reply_thread answers (recipient CUSTOMER or OPERATOR, which is Sprinter) and sprinter_create_order_thread opens a new conversation on an order. Reason codes for topics come from sprinter_list_reasons; leave its locale empty unless you know the marketplace has that language (an inactive locale answers 400).

Money: sprinter_list_invoices (IV01) lists the accounting documents Sprinter issues to the shop and sprinter_list_transactions (TL02) the transaction lines (sales, commissions, refunds, payouts). If Sprinter uses Enhanced Seller Invoicing, IV01 returns no new documents; use sprinter_list_document_requests (DR11) and the transactions then.

Reference lists: sprinter_list_channels (country sites), sprinter_list_carriers, sprinter_list_shipping_zones, sprinter_list_shipping_methods and sprinter_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 Sprinter can tighten them. Listing offers and orders is meant for interactive use, product and offer imports at most every 15 minutes, sprinter_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 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 shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

  1. In Muse, open Settings → Connectors and choose Add custom connector.
  2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
  3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
  4. In a chat, ask Muse for something that needs the Sprinter Marketplace tools.

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

ToolWhat it does
sprinter_get_accountRead the shop behind the API key on this marketplace (A01): shop id and name, state, channels, currency, grade and approval rate, contact…
sprinter_list_ordersList orders (OR11) with their lines, customer, shipping address, prices, state and incidents. Filter by state (e.g. WAITING_ACCEPTANCE for…
sprinter_list_offersList the shop's offers (OF21): SKU, product, price and discount, all channel prices, quantity in stock, condition, lead time and whether…
sprinter_get_offerRead one offer in full by its offer id (OF22): every price field, discount, quantity, condition, logistic class, lead time and custom…
sprinter_list_offer_conditionsList the offer conditions (OF61) the marketplace accepts, e.g. new or used, with the code to put in state_code when updating offers
sprinter_list_offer_importsList offer imports and updates (OF04), from files and from sprinter_update_offers: status (WAITING, RUNNING, COMPLETE, FAILED), lines read…
sprinter_get_offer_importRead the status of one offer import or offer update (OF02) by its import_id, as returned by sprinter_update_offers or…
sprinter_export_offersStart 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 paging sprinter_list_offers
sprinter_get_offer_export_statusStatus of an offer export started with sprinter_export_offers (OF53): PENDING, COMPLETED or FAILED, and once COMPLETED the urls of the files
sprinter_get_offer_export_fileRead one file of a completed offer export (OF54): the offers with their SKU, product, quantity, prices and the other exported fields, as JSON or CSV
sprinter_list_product_importsList product imports (P51) with their status (WAITING, RUNNING, SENT, COMPLETE, FAILED, CANCELLED), the transformation counts and the…
sprinter_get_product_importRead the status of one product import (P42) by its import_id: import status, reason, transformation counts and the integration details…
sprinter_get_productsLook up products in the marketplace catalog by their identifiers (P31), e.g. EAN, and get the marketplace product SKU, title and category.…
sprinter_list_product_offersList the offers of every shop for given products (P11), sorted by best price, to compare your price with the competition. Give product_ids…
sprinter_list_threadsList message threads (M11) with customers and Sprinter: topic, linked order or offer, participants, last message date and since when a shop…
sprinter_get_threadRead one message thread (M10) with all its messages, senders, recipients, attachments and the linked order or offer
sprinter_list_returnsList return requests (RT11) with their state, return lines, reason, RMA, tracking and the linked order. Filter by state, order or date.…
sprinter_list_reasonsList the marketplace's reason codes (RE01): incident, cancellation, refund and message reasons, with their labels and whether the shop may…
sprinter_list_carriersList the carriers the marketplace knows (SH21) with their code, label and tracking URL. Use the code as carrier_code in…
sprinter_list_invoicesList the accounting documents Sprinter issues to the shop (IV01): invoices and credit notes with period, totals with and without tax…
sprinter_list_transactionsList the shop's transaction lines (TL02): order amounts, shipping, commissions, refunds, manual credits and payouts, with amount, type…
sprinter_list_document_requestsList accounting document requests (DR11), used when Sprinter runs Enhanced Seller Invoicing: invoices and credit notes that Sprinter or the…
sprinter_list_order_documentsList the documents attached to one or more orders (OR72): delivery notes, shipping labels, customer invoices and other files, with id, file…
sprinter_list_channelsList the marketplace's sales channels (CH11), usually one per country site, with code and label. Use the codes as channel_codes in…
sprinter_list_shipping_zonesList the active shipping zones of the marketplace (SH11) with code and label, e.g. mainland France or Corsica. Changes rarely: call it…
sprinter_list_shipping_methodsList the active shipping methods of the marketplace (SH12), e.g. standard, express or pick-up, with code, label, whether a tracking number…
sprinter_list_logistic_classesList the marketplace's logistic classes (SH31), the size or weight bands that decide shipping prices, with code and label. Use the code as…
sprinter_accept_orderAccept or refuse the lines of an order waiting for acceptance (OR21). Every line of the order must be listed. Refusing a line cancels it…
sprinter_update_trackingSet the carrier and tracking number of an order (OR23). Give carrier_code from sprinter_list_carriers, or carrier_name with carrier_url for…
sprinter_ship_orderConfirm that an order in SHIPPING has been shipped (OR24); it moves to SHIPPED and the customer is notified. Set the tracking first with…
sprinter_update_offersCreate or update offers, including price and stock (OF24). Replaces each offer completely: every field left out is reset (a missing…
sprinter_reply_threadReply in a message thread (M12) to the customer or Sprinter. The message is delivered at once and cannot be taken back: show the user the…
sprinter_create_order_threadStart a new message thread on an order (OR43) with the customer, Sprinter or both. The message is delivered at once: show the user the…
sprinter_resolve_incidentMark the open incident on one order line as resolved (OR64), once the customer's problem is solved. reason_code must be an INCIDENT_CLOSE…
sprinter_accept_returnAccept or refuse a return request in WAITING_ACCEPTANCE (RT21). Only when Sprinter handles returns in the seller back office and leaves the…
sprinter_receive_returnConfirm that the goods of an accepted return arrived at your warehouse (RT25). The return moves to RECEIVED. Acts on the live marketplace…
sprinter_import_productsSend 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…
sprinter_import_offersImport 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 Sprinter orders are waiting for my acceptance, and how many come from Portugal?"
  • "Set the price of my running shoes SKU RN-AIR-42 to 69.99 EUR."
  • "Which carriers does Sprinter accept, and what is the code for SEUR?"
  • "Show the customer messages that wait for a reply."
  • "List the transactions of my last payout."

FAQ

Where do I get the Sprinter API key? In the Sprinter 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. If your user has more than one shop, set SPRINTER_SHOP_ID; otherwise your default shop is used.

Who can sell on Sprinter, and which countries does it cover? Sprinter takes applications through the form on its seller page; fees and commission are agreed with Sprinter. The connector covers Spain and Portugal. Spain and Portugal are two sales channels of the same shop, each with its own prices.

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

Connect Sprinter Marketplace to Meta Muse in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Sprinter Marketplace in the guided setup, then add your MCP URL to Meta Muse. No code and no server to run.

Related guides

Connectors

Connect Sprinter to ChatGPT via MCP: Orders and Offers

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.

Connectors

Connect Sprinter to Claude via MCP: Orders and Stock

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.

Connectors

Connect Sprinter to Microsoft Copilot via MCP

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.

Connectors

Connect Sprinter to Cursor via MCP: Orders and Stock

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.

Connectors

Connect Sprinter to Gemini CLI via MCP: Orders and Offers

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.

Connectors

Sprinter MCP Server: Orders, Offers and Shipping

Run your shop on the Sprinter 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 Spain and Portugal; sign in with the shop API key from your Sprinter seller back office.