Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Read-only AutoID Romania MCP for product search, live stock/prices, specs, and technical support.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.autoid.ro/mcpRun this in your terminal
claude mcp add --transport http autoid-support https://mcp.autoid.ro/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"autoid-support": {
"url": "https://mcp.autoid.ro/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"autoid-support": {
"type": "http",
"url": "https://mcp.autoid.ro/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.autoid.ro/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain autoid.ro (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
unzip autoid-mcp-v0.3.1.zip
cd autoid-mcp-v0.3.1 npm install cp .env.example .env npm run build npm run smoke:api npm start
Environment variables:
AUTOID_API_BASE=https://www.autoid.ro/wp-json/autoid-ai/v1
MCP_PUBLIC_HOST=mcp.autoid.ro PORT=3000 AUTOID_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
Assuming the live application directory is /opt/autoid-mcp:
sudo systemctl stop autoid-mcp
sudo cp -a /opt/autoid-mcp /opt/autoid-mcp-backup-v0.1.0 sudo rm -rf /opt/autoid-mcp sudo mkdir -p /opt/autoid-mcp sudo cp -a ./autoid-mcp-v0.3.1/. /opt/autoid-mcp/ sudo cp /opt/autoid-mcp-backup-v0.1.0/.env /opt/autoid-mcp/.env cd /opt/autoid-mcp sudo npm install sudo npm run smoke:api sudo npm run build sudo chown -R www-data:www-data /opt/autoid-mcp sudo cp deploy/autoid-mcp.service /etc/systemd/system/autoid-mcp.service sudo systemctl daemon-reload sudo systemctl enable autoid-mcp sudo systemctl restart autoid-mcp sudo systemctl status autoid-mcp
Then verify:
curl -s https://mcp.autoid.ro/health
curl -s https://mcp.autoid.ro/ready
The included Dockerfile intentionally uses npm install because this release archive does not include a generated lock file.
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.
After deployment, validate these tool calls in an MCP client:
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" })
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: or resource: 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.