MCP endpoint
The three channels
MCP server
Connect Claude, ChatGPT, Copilot, Cursor or Mistral.
REST API
Read shipments, invoices, documents and tracking from your own code.
Ask Zach
The assistant already inside Hermès, for the people using it.
Permissions
Every channel resolves permissions server-side, against the identity its credential carries, and an agent cannot reach anything that identity cannot already reach. This is enforced by the credential rather than by the agent. Which identity that is differs by channel. The MCP server and Ask Zach both act as the signed-in person, so they see exactly what that colleague sees in Hermès and no more. A REST token is issued for the account by an owner or admin, so it is not scoped to one person — treat it as an account credential and store it accordingly.What an agent may change
Agent actions lists every action an agent can perform, generated from the API schema, and marks which are exposed as MCP tools. Reading never requires confirmation. Changing does, and how depends on the channel:- REST API — no approval step. A call with a valid token performs the write immediately, and your code is the control.
- MCP server — every tool carries the standard MCP annotations (
readOnlyHint,destructiveHint,idempotentHint). Interactive assistants normally use them to decide when to ask the user first; an unattended client has no such prompt. Read Before you automate before relying on them. - Ask Zach — the assistant states what it is about to change and waits for the person to agree, on a card for the most common actions and in the conversation for the rest.