The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the AutoID Product Catalog & Support listing page.
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.
search_productsget_product_grouplist_product_variantsget_productget_product_offerget_related_productsget_related_products_summarysearch_supportfetch_supportautoid_support_healthautoid_api_healthThe 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:
pret_listapret_autoid_eurogrp_pret_lista_micgrp_pret_autoid_micstock_autoidstock_distributieFor 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.
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:
inc_vatex_vat may also be shownpret_lista / pret_autoid_euro remain the commercial authorityget_related_products reads:
/wp-json/autoid-ai/v1/relations/{sku-or-model}
Supported relation types:
accessory - stock-managedconsumable - stock-managedsoftware - not stock-managedservice_contract - not stock-managedallCompatibility 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-imprimantarole-de-eticheteintretinere-imprimanteget_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.
MC9300 full relation graph at validation time:
ZT610 full relation graph at validation time:
ZT610 consumables at validation time:
These numbers are validation snapshots, not hard-coded production data. MCP always reads the live canonical API.
mcp.autoid.rowww.autoid.roNo WordPress DB access, WooCommerce API key or WordPress administrator credentials are required.
Environment variables:
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
Assuming the live application directory is /opt/autoid-mcp:
Then verify:
The included Dockerfile intentionally uses npm install because this release archive does not include a generated lock file.
The container binds only to 127.0.0.1:3000; expose it through the supplied Nginx reverse-proxy configuration.
After deployment, validate these tool calls in an MCP client:
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.
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.
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.
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.