Probo Connect MCP server

Read from the package source without running it. The installed server may list more.

• bulkPlaceOrders

  Place multiple orders in sequence. Returns per-order success/failure. Honors current mode (see setMode).

• cancelOrderwrite action

  Cancel a pending order. Only works if the order has NOT yet entered production. IMPORTANT: - Use the order ID from placeOrder (e.g. "order-1776164807276"), NOT the Probo supplier_order_number - Orders with status "in_production" or later CANNOT be cancelled — you'll get an error - The supplier_order_number (e.g. "1260224369") from getAllOrders is Probo's internal number and will NOT work here - Af

• compareProducts

  Fetch full details for multiple products and return a side-by-side comparison (dimensions, options, categories).

• configureProduct

  Configure a product with options and get pricing. Call first without options to see available options, then call again with selected options. NOTE: This tool uses "productCode" as parameter name. When placing an order with placeOrder, the same code goes in products[].code — different parameter name, same value. IMPORTANT — How options work: - Numeric options (width, height, amount): send {code, va

• createDraftwrite action

  Create a draft order that can be reviewed and edited on the Probo platform before being submitted. Same as placeOrder but saved as draft instead of submitted.

• createProjectwrite action

  Create a new project to group related orders together.

• createTicketwrite action

  Create a support ticket for an order issue. Describe the problem and suggest a solution.

• createUploaderwrite action

  Create a file uploader for a configured product BEFORE placing the order. Returns upload URL(s) and uploader IDs. NOTE: For most cases, using uploader:true directly in placeOrder is simpler — Probo returns the upload URL(s) in the order response. Use createUploader only when you need the upload URL BEFORE placing the order (e.g. to pre-validate files or for a custom upload flow). Pre-order upload

• deleteAliaswrite action

  Delete a saved alias and unregister its prompt.

• deleteFavoritewrite action

  Remove a saved favorite.

• deleteOrderTemplatewrite action

  Delete a saved order template.

• elicitMissingFields

  Ask the AI client (via MCP elicitation) for missing order fields. Falls back gracefully if the client does not support elicitation.

• getAllOrders

  List all orders with optional filters. Returns order history with references, dates, prices, delivery addresses, and status. ID fields in the response: - "number" = Probo's supplier_order_number (visible in Probo dashboard) - "customer_order_id" = the order ID from placeOrder (use this for getOrderStatus and cancelOrder) - "customer_reference" = your reference string from placeOrder

• getApiProductDetail

  Get full details of a single custom API product by its customer code. Shows options, dimensions, and configuration for customer-configured products.

• getApiProducts

  List your custom API products (customer-configured products with custom codes).

• getCapabilities

  Show everything Probo Connect MCP can do. Triggered by: "what can you do", "wat kan je", "help", "hulp", "capabilities", "mogelijkheden", "welke tools".

• getCuratedTemplates

  Get a library of curated starter templates (banner, fabric, roll-up) that users can start from before customizing.

• getFavorites

  List all saved favorite products.

• getImagePreview

  Fetch an image URL (e.g. order preview from getAllOrders "converted_preview_small_url") and return it inline so the user can see it.

• getMode

  Return the current runtime order mode (test/production).

• getOrderStatswrite action

  Aggregate statistics for your recent orders: total, breakdown by status, total spent, average, top products.

• getOrderStatuswrite action

  Check the status of one or more orders. Returns status code, delivery date, tracking info, and package details. IMPORTANT: - Use the EXACT order ID returned by placeOrder (e.g. "order-1776164561402") - Newly placed orders need ~30 seconds before Probo processes them — if you get "Order(s) not found", wait and retry - Test orders (isTest: true) are auto-cancelled and may not appear in status - Use

• getOrderTemplateswrite action

  List all saved order templates.

• getPlacedOrderHistorywrite action

  Return the local history of orders this MCP instance has placed (auto-saved). Independent of Probo API — works offline.

• getPrice

  Calculate the price for one or more products before placing an order. Returns purchase price, sales price, shipping costs, and delivery dates.

• getPricingTiers

  Get pricing tiers for a product. Shows volume discounts — price per unit at different quantities.

• getProductDetails

  Get full details for a single product including all available options, dimensions, and configuration. Use this to understand what options a product supports before configuring it.

• getProjects

  List all projects. Projects group related orders together.

• getRecommendations

  Get personalized product recommendations based on the user profile focus (e.g. banners, textiles). Falls back to top products if no profile set.

• getSavedAddresses

  List all saved delivery addresses. Addresses persist across sessions in ~/.probo-connect/.

• getShippingMethods

  List available shipping methods and carriers. Shows codes, carrier names, and whether email/phone is required.

• getTickets

  List support tickets. Tickets are used to report issues with orders.

• getUserProfile

  Get the current user profile. Use this to personalize responses — check preferred language, company, and product focus.

• getVersion

  Show Probo Connect MCP version and status. Triggered by: "version", "versie", "welke versie", "what version", "is this up to date", "ben ik up to date", "probo info", "probo status".

• getWebhookEvents

  Return Probo order callback events received by the built-in webhook listener. Only works in --http mode when running stdio locally. In remote/HTTP server mode the tool is disabled to prevent cross-tenant event leakage.

• listAliases

  List all saved aliases. Each alias is also exposed as an MCP prompt named alias-<name>.

• placeOrderwrite action

  Place a print order with Probo. Returns order ID and confirmation. IMPORTANT — Product field naming: - Use "code" (e.g. "banner-510") or "customer_code" for products — NOT "productCode" (that's only for configureProduct) - Options: flat array. Radio/selection: {code:"finishing-all-sides"} (child code only, no value). Numeric: {code:"amount",value:1} IMPORTANT — Configuration products require files

• placeOrderFromTemplatewrite action

  Place an order from a saved template. You can override reference, address, or options.

• placeOrderWithApprovalwrite action

  Place an order only after an LLM sanity-check of the configuration via MCP sampling. Falls back to direct order if client does not support sampling.

• predictDeliveryETA

  Estimate delivery timing based on the user's historical delivered orders (days from placed to delivered).

• releaseOrderwrite action

  Release a held order for production. Use when an order needs manual approval before going into production.

• runAliaswrite action

  Resolve a saved alias to the underlying tool name and merged arguments. The LLM should then call that tool directly. Optional overrides are shallow-merged on top of the saved args.

• saveAddress

  Save a delivery address for reuse. Persists across sessions in ~/.probo-connect/. Give it a name like "office" or "warehouse".

• saveAlias

  Save a named alias for any Probo tool with pre-filled arguments. The alias shows up as a dynamic MCP prompt (alias-<name>) in the client's slash menu. Persists in ~/.probo-connect/.

• saveFavorite

  Save a product as favorite for quick access. Persists in ~/.probo-connect/.

• saveOrderTemplatewrite action

  Save a complete order configuration as a reusable template. Persists in ~/.probo-connect/. Use placeOrderFromTemplate to re-order.

• saveUserProfile

  Save user profile information for personalized responses. Persists across sessions in ~/.probo-connect/. Call this after learning about the user.

• searchProducts

  Search the Probo product catalog. Returns product names, codes, categories, and pricing. Use without query to browse all products.

• setMode

  Switch between test and production order mode at runtime without restarting the server. Affects placeOrder defaults.

• uploadFileToUploaderwrite action

  Upload a local file directly to an existing Probo uploader URL. Use after createUploader. Flow: 1. configureProduct → get calculation_id 2. createUploader({calculationId, callbackUrl}) → get uploadUrl 3. uploadFileToUploader({uploadUrl, filePath}) → file is uploaded Supports .pdf, .jpg, .jpeg, .png files up to Probo's size limit.

• uploadFolderToUploaderwrite action

  Upload all print files from a local folder to an uploader URL (non-recursive). Filters by extension.

• Code scan29 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Safety score

55/100

higher than 10% of 2,174 E-commerce servers

Tools

51

the typical E-commerce server has 6

Tools that change things

39%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

16

more than 4% of 411 E-commerce servers with a package

Probo Connect: common questions

Is Probo Connect MCP server safe?

With care: it is graded C, so read the findings first (55/100). Read the Probo Connect safety report

How do I install Probo Connect?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Probo Connect need an API key?

Yes. The registry entry asks for PROBO_API_KEY.

Is Probo Connect maintained?

The latest release is v2.13.0.

What can I use instead of Probo Connect?

Servers from other publishers that do the same job: Mercado Libre MCP server, WebCake Storefront MCP server and Shopware MCP server.

How does Probo Connect compare with other E-commerce MCP servers?

safety score 55/100 (higher than 10% of 2,174 E-commerce servers); tools 51 (the typical E-commerce server has 6); tools that change things 39% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.