Skip to content
ITEMRA
Documentation menu

Developers

MCP & connectors

The Itemra MCP server for AI agents, and the Zapier and Make connector sources.

The MCP server

Itemra ships an MCP server so AI agents can work with your inventory through the Customer API: search items, answer stock and availability questions, create controlled adjustments and moves, draft purchase orders, and query stock reports. It's a local stdio adapter (Node 22+, no third-party runtime dependencies) — it adds no public endpoint and bypasses nothing: the API's tenant isolation, scopes, and permissions remain the enforcement boundary.

Security model in brief:

  • The API key comes from the subprocess environment, never a tool argument, and is redacted from every payload the server emits.
  • HTTPS only (loopback excepted for local testing); redirects rejected.
  • Use a dedicated least-privilege key per the tool set: reads need items:read / stock:read / reports:read; the write tools map to stock:write, movements:write, purchasing:write.
  • Write tools require explicit idempotency keys, and a good MCP client should ask a human before any write fires — the read tools are annotated read-only.

Point it at a dev-environment key and the sandbox dataset while building.

Zapier and Make

Itemra maintains connector sources for Zapier (instant webhook triggers with full signature verification) and Make (checkpointed polling of the events feed) — triggers for stock.changed, low-stock, item.created, and po.received, plus actions to create items, adjust stock, and create purchase orders. Both use one dedicated API key per platform and require a stable idempotency key per action. Ask Itemra support for current availability and setup guidance on your platform of choice.