Skip to main content

Connect an AI assistant (MCP)

Zimam runs an MCP (Model Context Protocol) server for your store. Any AI assistant that supports MCP, Claude included, can connect to it and answer questions such as "show me today's pending orders" or "which products are low on stock?". With write access, the assistant can also update orders and products and send orders to a carrier.

The server address is:

https://api.getzimam.com/mcp

Your customers' data​

Once connected, the assistant reads your customers' names, phone numbers and delivery addresses. That data goes to the AI provider configured in your own MCP client, outside Zimam, and Zimam does not control what that provider does with it. Before you can connect, you must confirm: "I understand that customer names, phone numbers and delivery addresses will be sent to the AI provider configured in my own MCP client, outside Zimam."

Connect with sign-in (OAuth)​

Use this when your MCP client can add a remote server by URL and sign you in.

  1. In your MCP client, add a remote MCP server or connector with the address above.
  2. When the client opens Zimam, sign in with your Zimam account.
  3. On Connect an AI assistant, choose the Store.
  4. Under Requested access, keep or clear each permission the client asked for.
  5. Check the customer-data notice.
  6. Click Allow access, or Deny to refuse.

Connect with a token​

Use this when your MCP client accepts a custom HTTP header.

  1. Open Store settings, then the MCP tab, where you find MCP access tokens.
  2. Click Create a token and give it a Name.
  3. Under Access, choose the permissions. Write permissions are under Write access.
  4. Check the customer-data notice and create the token.
  5. Click Copy token. It is shown only once.
  6. In your MCP client, send it as the header Authorization: Bearer followed by the token.

Permissions​

PermissionPlan
Read orders, Read products, Read analytics, Read delivery statusEvery plan
Create and update orders, Create and update products, Assign delivery for ordersGrowth, Pro and Enterprise

On other plans the write permissions show "Not included in your current plan. Upgrade to allow this." If your store later moves to a plan without write access, the assistant's write actions are refused and its read access keeps working.

A token or app never has more access than the Zimam user who created it. If that user loses access to the store, the token stops working.

What the assistant can do​

  • Read: list and search orders, open an order, list and open products, read store and region stats, read delivery status.
  • Orders: add a note, confirm a pending order, change an order's status, edit the customer's name, phone, address and notes.
  • Products: create a product (always created unpublished), edit a product, update stock, publish or unpublish a product.
  • Delivery: send an order to a delivery company.

Actions that need your confirmation​

Changing an order's status, editing an order, editing a product, publishing or unpublishing a product, and sending an order to a carrier happen in two steps. The assistant first gets a preview of the change and shows it to you. It carries out the change only when it comes back with that exact change within 5 minutes. If anything differs from the preview, the change is refused.

Adding a note, confirming a pending order, updating stock and creating an unpublished product happen directly.

Limits​

  • 30 requests every 10 seconds per store. Past that, the assistant is told to wait and retry.
  • 10 carrier dispatches per minute per store.

Revoke access​

In MCP access tokens:

  • Click Revoke next to a token to stop it immediately.
  • Under Connected apps, click Revoke next to an app. This signs the app out everywhere and cancels every token it received. Other apps are not affected.

If the assistant reports that its token is invalid or expired, connect it again.