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 分

    请在仓库或注册中心条目中声明许可证。