AutoID Product Catalog & Support

ro.autoid由 autoid.ro 發布官方發布者v0.3.0更新於 Nov 2, 2026

Read-only AutoID Romania MCP for product search, live stock/prices, specs, and technical support.

已驗證Streamable HTTP可網頁執行知識與記憶商業與電商

概覽

AI 產生的概覽

面向 AutoID 羅馬尼亞產品目錄的唯讀遠端 MCP:產品搜尋、即時價格與庫存、相關配件以及技術支援資料。

可以做什麼
  • 搜尋與瀏覽目錄:依型號、SKU 或文字尋找產品,並分頁瀏覽產品群組、產品、品牌與分類
  • 讀取精確 SKU 資料:標準產品資訊、含全新/翻新/二手價格與庫存的目前報價,以及群組型號下的各 SKU
  • 尋找相關產品:某型號或 SKU 的配件、耗材、軟體與服務合約,以及相容品與缺貨品的彙總數量
  • 查詢技術支援:搜尋手冊、驅動程式、韌體、軟體、影片與疑難排解文章,並取得單筆結果的完整查證文字
  • 檢查資料來源健康狀態:目錄 API 與支援資料來源
適用情境
適合需要回答 AutoID 羅馬尼亞產品問題的情境,例如某個 SKU 的目前價格與庫存、某款印表機或行動電腦適用哪些配件或耗材,或某型號的手冊與韌體在哪裡。
執行需求
遠端 streamable HTTP 端點;未宣告需要帳號、API 金鑰或請求標頭。若自行部署,伺服器本身需要 Node.js 20+ 並能透過 HTTPS 連線至 AutoID 網站。
安裝前請注意
服務為唯讀,不暴露 WordPress 憑證,但端點未宣告任何身分驗證,能連上該位址的人都能查詢目錄。價格與庫存來自第三方商業資料來源,報價前應再次確認;RON 顯示價屬店面前台資料,並非 EUR 商業權威價。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 AutoID Product Catalog & Support,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ro.autoid%2Fautoid-support/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "autoid-product-catalog-support": {
      "type": "http",
      "url": "https://mcp.autoid.ro/mcp"
    }
  }
}

README

AutoID MCP Server v0.3.1

Read-only MCP server over the AutoID canonical WordPress/WooCommerce API.

This release includes the product, offer, grouped-variant and related-product behavior validated with the AutoID canonical API plugin v0.3.9.

MCP tools

  • search_products
  • get_product_group
  • list_product_variants
  • get_product
  • get_product_offer
  • get_related_products
  • get_related_products_summary
  • search_support
  • fetch_support
  • autoid_support_health
  • autoid_api_health

Source of truth

The MCP server does not read WordPress SQL and does not calculate commercial or compatibility data itself. It reads the canonical API at:

https://www.autoid.ro/wp-json/autoid-ai/v1

Authoritative commercial fields:

  • exact SKU MSRP EUR ex VAT: pret_lista
  • exact SKU AutoID price EUR ex VAT: pret_autoid_euro
  • grouped catalog MSRP from: grp_pret_lista_mic
  • grouped catalog AutoID from: grp_pret_autoid_mic
  • AutoID stock: stock_autoid
  • distribution stock: stock_distributie

For a current exact-SKU price/stock answer, use get_product_offer. For Romanian customer-facing price output, use the canonical ron_display projection and prefer the inc-VAT value. RON is sourced from WooCommerce _regular_price / _sale_price; do not convert authoritative EUR prices into RON inside MCP.

RON display pricing

Canonical API v0.3.9 adds a compact RON projection without changing commercial authority.

Exact SKU cards use pricing.ron_display; exact live offers use price.ron_display. Typical fields are msrp_ex_vat, msrp_inc_vat, autoid_ex_vat, and autoid_inc_vat. Grouped products use FROM fields such as msrp_from_inc_vat and autoid_from_inc_vat.

Rules:

  • customer-facing Romanian answer: prefer RON inc_vat
  • B2B/ex-VAT context: RON ex_vat may also be shown
  • EUR pret_lista / pret_autoid_euro remain the commercial authority
  • RON values are WooCommerce storefront display/validation data
  • never calculate RON by applying an FX rate to the EUR authority inside MCP

Related-product contract

get_related_products reads:

/wp-json/autoid-ai/v1/relations/{sku-or-model}

Supported relation types:

  • accessory - stock-managed
  • consumable - stock-managed
  • software - not stock-managed
  • service_contract - not stock-managed
  • all

Compatibility is accepted only from the canonical API's product_tag evidence. WooCommerce product_cat determines whether the related entity is an accessory, consumable, software item or service contract.

For accessories and consumables, MCP defaults to availability=available:

stock_autoid > 0 OR stock_distributie > 0

The canonical API ranks AutoID stock before distribution-only stock. Out-of-stock items are intentionally extra catalog information and are not returned by default. Request availability=out_of_stock or availability=all only when needed.

For large consumable sets, filter using an exact category slug. Validated ZT610 examples include:

  • ribboane-imprimanta
  • role-de-etichete
  • intretinere-imprimante

get_related_products_summary queries availability=all with a one-item page, then returns a compact projection of the canonical summary. Use it for total compatibility counts and out-of-stock counts without loading hundreds of catalog items into MCP context.

Validated datasets

MC9300 full relation graph at validation time:

  • 85 accessories
  • 23 software entities = 22 exact SKUs + 1 grouped product
  • 130 service contracts
  • 0 consumables
  • 238 related entities total

ZT610 full relation graph at validation time:

  • 85 accessories
  • 752 consumables
  • 29 software entities = 28 exact SKUs + 1 grouped product
  • 69 service contracts
  • 935 related entities total

ZT610 consumables at validation time:

  • 32 with AutoID stock
  • 206 supplier-only
  • 514 out of stock

These numbers are validation snapshots, not hard-coded production data. MCP always reads the live canonical API.

Requirements

  • Node.js 20+
  • public HTTPS hostname, recommended mcp.autoid.ro
  • outbound HTTPS access to www.autoid.ro

No WordPress DB access, WooCommerce API key or WordPress administrator credentials are required.

Fresh install

bash
unzip autoid-mcp-v0.3.1.zipcd autoid-mcp-v0.3.1npm installcp .env.example .envnpm run buildnpm run smoke:apinpm start

Environment variables:

env
AUTOID_API_BASE=https://www.autoid.ro/wp-json/autoid-ai/v1MCP_PUBLIC_HOST=mcp.autoid.roPORT=3000AUTOID_API_TIMEOUT_MS=15000

The public MCP endpoint is:

https://mcp.autoid.ro/mcp

HTTP process health:

https://mcp.autoid.ro/health

Canonical API readiness check:

https://mcp.autoid.ro/ready

Upgrade from v0.1.0 with systemd

Assuming the live application directory is /opt/autoid-mcp:

bash
sudo systemctl stop autoid-mcpsudo cp -a /opt/autoid-mcp /opt/autoid-mcp-backup-v0.1.0sudo rm -rf /opt/autoid-mcpsudo mkdir -p /opt/autoid-mcpsudo cp -a ./autoid-mcp-v0.3.1/. /opt/autoid-mcp/sudo cp /opt/autoid-mcp-backup-v0.1.0/.env /opt/autoid-mcp/.envcd /opt/autoid-mcpsudo npm installsudo npm run smoke:apisudo npm run buildsudo chown -R www-data:www-data /opt/autoid-mcpsudo cp deploy/autoid-mcp.service /etc/systemd/system/autoid-mcp.servicesudo systemctl daemon-reloadsudo systemctl enable autoid-mcpsudo systemctl restart autoid-mcpsudo systemctl status autoid-mcp

Then verify:

bash
curl -s https://mcp.autoid.ro/healthcurl -s https://mcp.autoid.ro/ready

Docker

The included Dockerfile intentionally uses npm install because this release archive does not include a generated lock file.

bash
docker compose -f deploy/docker-compose.yml up -d --build

The container binds only to 127.0.0.1:3000; expose it through the supplied Nginx reverse-proxy configuration.

First MCP validation

After deployment, validate these tool calls in an MCP client:

text
autoid_api_health({})get_product_group({ model: "MC9300" })list_product_variants({ model: "MC9300", availability: "available", limit: 20 })get_product_offer({ sku: "MC930B-GSHDG4RW" })get_related_products({ target: "MC9300", relation_type: "accessory", availability: "available", limit: 20 })get_related_products({ target: "ZT610", relation_type: "consumable", category: "ribboane-imprimanta", availability: "available", limit: 20 })get_related_products_summary({ target: "ZT610", relation_type: "consumable" })

HestiaCP deployment note

If the host is managed by HestiaCP and a domain template already proxies mcp.autoid.ro to port 3000, do not overwrite Hestia Nginx or Certbot configuration. Replace/build only the application files and restart the existing Node process through the host administrator's preferred supervisor.

Security

v0.3.1 is read-only. It exposes no WordPress credentials and performs no writes. The canonical API remains the data and security boundary.

Before adding write tools such as RFQ creation, add authentication, authorization, audit logging and abuse controls separately.

Public root

Opening https://mcp.autoid.ro/ in a browser returns a small human landing page with links to /health, /ready, and /mcp. The Node process binds to 127.0.0.1:3000 and is intended to be published only through the existing HestiaCP/Nginx reverse proxy.

Support Center tools — v0.3.1

The public endpoint https://mcp.autoid.ro/mcp now exposes the existing catalog tools plus three Support Center tools:

  • search_support — search models, manuals, drivers, firmware, software, videos and troubleshooting resources.
  • fetch_support — fetch one exact model:<id> or resource:<id> returned by search.
  • autoid_support_health — verify the read-only Support Center source.

Support data is proxied from the existing first-party AutoID Support MCP source (AUTOID_SUPPORT_MCP_URL, default https://www.autoid.ro/mcp/). The Node service does not read WordPress SQL, filesystem or admin APIs. Product data continues to come from AUTOID_API_BASE.

search_support is intent-aware in v0.3.1: it merges the original query with model-wide and requested-resource-type searches, deduplicates results, and ranks requested types above generic resources. A multi-intent query such as MC9300 firmware manual should surface both the firmware/LifeGuard entry and the documentation/manual entry before unrelated generic resources.

For chat integrations, the recommended OpenAI Responses API configuration is one read-only remote MCP tool pointing to https://mcp.autoid.ro/mcp, with an explicit allowed_tools list and require_approval: never. Current price/stock questions should use get_product_offer; technical support resources should use search_support followed by fetch_support.

來源:README.md,提交 daab33c

工具

15

search_products

Search AutoID products

Search the official AutoID catalog by model, SKU or text. Use this first when the exact SKU is unknown. Results come from the first-party AutoID canonical API. Prefer exact product groups and SKUs over loosely related resources. Customer-facing RON prices are exposed under pricing.ron_display when available; prefer the inc-VAT value for Romanian storefront answers and never convert EUR yourself.

輸入參數limitquery必填

list_product_groups

List AutoID product groups

Enumerates canonical grouped-product models for exhaustive catalog synchronization. This is a discovery tool, not search: clients should page through the complete result set using limit and offset. Results come only from the first-party AutoID canonical API and must not be reconstructed from search queries.

輸入參數brandlimitoffsetlifecycle

list_products

List all AutoID products

Exhaustive read-only product registry for catalog synchronization. Pages through every published WooCommerce product, including grouped models and standalone/exact products. Use entity_type=grouped or single to filter without approximating completeness from search.

輸入參數limitoffsetentity_type

list_brands

List AutoID brands

Returns the complete canonical WooCommerce brand/manufacturer taxonomy used by AutoID. This taxonomy is authoritative for brand archives and is never inferred from product titles.

無需輸入參數。

list_categories

List AutoID product categories

Returns the complete canonical WooCommerce product_cat taxonomy with parent/depth/path data for category archives and catalog filters.

無需輸入參數。

get_product_group

Get AutoID product group

Returns authoritative grouped-product information for an AutoID model such as MC9300. Group prices are FROM prices, not exact SKU prices. Distinguish catalog_from from available_from; available_from only considers members with stock_autoid > 0 or stock_distributie > 0. Customer-facing RON display prices are exposed by the canonical API under pricing.ron_display; they are WooCommerce display/validation values, not the commercial authority.

輸入參數model必填

list_product_variants

List AutoID product variants

Lists exact SKUs belonging to an AutoID grouped product. Each SKU may expose independent offers.new, offers.refurbished and offers.used records when the canonical API provides the condition contract. condition=refurbished or used filters only source-declared enabled offers and never infers condition from price or text. Default availability=available. AutoID stock is prioritized before distribution-only stock.

輸入參數limitmodel必填offsetconditionavailability

get_product

Get exact AutoID SKU

Returns canonical data for an exact AutoID SKU. The same SKU can carry NEW, REFURBISHED and USED commercial offers without cloning the WooCommerce product. Use condition to project a source-declared condition when present. For current commercial data always call get_product_offer as well; condition data is never inferred when the canonical source has not exposed it.

輸入參數sku必填condition

get_product_offer

Get live AutoID offers by condition

Returns the current authoritative commercial offer data for one exact SKU. A single SKU may expose offers.new, offers.refurbished and offers.used with independent price and stock. Refurbished/Used may also include grade, warranty, note, Google eligibility, professional reconditioning/refurbisher and component-condition fields. ALWAYS use this tool before answering current price, stock, availability or delivery questions. The MCP never manufactures a condition: if the canonical API has not exposed offers.refurbished/offers.used, condition requests explicitly report source_support=false instead of treating the condition as unavailable.

輸入參數sku必填condition

search_support

Search AutoID technical support

Search the official AutoID Support Center for a model, manual, driver, firmware, software, troubleshooting article, video or other verified technical resource. The search layer is intent-aware: model-wide and resource-type matches are merged and ranked so requested resource types outrank generic resources. Use this before fetch_support and fetch every resource you rely on. Search results are read-only first-party AutoID support records and manufacturer resources; do not infer a firmware version or procedure from a title alone.

輸入參數query必填

fetch_support

Fetch AutoID support model or resource

Fetch the full verified text and metadata for one result returned by search_support. IDs have the form model:<id> or resource:<id>. Use the returned verified text, warnings, model scope, official URL, version/OS metadata and source provenance as the grounding source for technical answers. Never substitute a nearby model or invent missing versions.

輸入參數id必填

autoid_support_health

Check AutoID Support MCP health

Checks the read-only AutoID Support Center MCP source used for manuals, firmware, drivers, software, videos and troubleshooting resources.

無需輸入參數。

autoid_api_health

Check AutoID canonical API health

Checks whether the first-party AutoID canonical API is reachable and reports its declared authoritative commercial fields and relation capabilities.

無需輸入參數。

版本歷史

1
  1. v0.3.0最新Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。