---
title: "Comment by Cai on \"How AI Agents Connect to Retail ERP: APIs, MCP, and Controlled Workflows\" | Hashnode"
description: "MCP is the right choice for normalizing retail ERP integrations. One gap that becomes obvious once an agent has write access: the spec doesn't define agent-leve"
url: "https://hashnode.com/posts/how-ai-agents-connect-retail-erp-apis-mcp-controlled-workflows/6ad912a5d6efd7eaf6d3dd23/comment/6ad9c36df90b53477e3b06de"
---

[Discussion](https://hashnode.com/posts/how-ai-agents-connect-retail-erp-apis-mcp-controlled-workflows/6ad912a5d6efd7eaf6d3dd23)

Comment [How AI Agents Connect to Retail ERP: APIs, MCP, and Controlled Workflows](https://hashnode.com/posts/how-ai-agents-connect-retail-erp-apis-mcp-controlled-workflows/6ad912a5d6efd7eaf6d3dd23)

[Cai](https://hashnode.com/@cailab)

[Oct 22](https://hashnode.com/posts/how-ai-agents-connect-retail-erp-apis-mcp-controlled-workflows/6ad912a5d6efd7eaf6d3dd23/comment/6ad9c36df90b53477e3b06de)

MCP is the right choice for normalizing retail ERP integrations. One gap that becomes obvious once an agent has write access: the spec doesn't define agent-level identity, so implementations end up threading principal IDs through tool arguments to keep audit trails meaningful. CAI's agent wallet protocol with signed intents was designed for exactly this pattern.