Connect an assistant with MCP EN

Choose the right interface, authenticate to the right store and verify permissions before allowing writes.

An MCP connection lets an assistant use Kaduno tools. Its available actions depend on the interface, authenticated person, selected store, permissions, modules and policy. Do not assume that every admin button has an equivalent tool, or that an assistant's confirmation prompt replaces server-side authorisation.

Select an interface

InterfaceIntended audience and work
/mcp/commerceStaff working with reports, orders, products, customers and content
/mcp/salesB2B sales work such as accounts, opportunities, quotes and follow-up
/mcp/adminBroader staff administration within the caller's permissions
/mcp/storefrontAuthenticated customers, their shopping and portal context
/mcp/publicPublic visitor tools
/mcp/kaiConversations with Kai from another client

Use the connection address shown in the store's Settings → AI agents page. Do not guess a URL on the storefront domain or assume it forwards MCP requests. For a narrower staff workflow, choose the interface that exposes the needed work rather than automatically connecting every interface.

Connect and prove the context

  1. A store administrator checks AI plugins staff may connect. External staff OAuth and agent-key connections are off by default; the choices allow Commerce only or Commerce, Sales and Admin. This is separate from Kai inside admin.
  2. Review the business description the assistant will receive. Keep it factual; do not put credentials or unnecessary customer data there.
  3. Each person signs in with their own Kaduno account through the supported OAuth connection. If multiple stores are available, select the intended store.
  4. For supported developer clients, a staff agent key is an alternative. Create it in API-key settings with appropriate expiry; it is bound to its store and owner's role. A REST integration key is not interchangeable with this key.
  5. Read store context and inspect the actual tool list. Perform a permitted read first and verify the returned store before authorising any write.

An OAuth connection can switch among stores it is allowed to access. A staff agent key remains bound to its configured store. Recheck context after any switch; credentials alone are not proof that a particular operation is allowed. Use connected-app settings to revoke an unwanted OAuth authorisation.

Policy and confirmation are separate controls

The store's agent policy can restrict tool groups. Kai's own risk policy and external MCP-client confirmation behaviour are different layers. Check the client's confirmation support and an agent key's MCP confirmation configuration before allowing consequential actions.

Do not assume that every write displays the same card or requires typed confirmation. Requirements vary by tool, risk, connection and supported workflow. Read AI permission and approval boundaries for source-verified exceptions and limits. A dry run exists only where the tool supports it; it is not a universal safe mode.

Customer-facing agent access and checkout controls are configured separately. Staff access does not grant a customer or anonymous visitor staff authority.

Data and credentials

Data returned to an external assistant is shared with that assistant's provider. Review the store's customer-data privacy settings and the applicable provider arrangement before enabling sensitive use. Do not assume every returned field is masked simply because one privacy setting is enabled.

Never paste passwords, API keys or tokens into a conversation or support note. Where a credential handoff is offered, enter the secret in that dedicated flow; otherwise use the integration's authorised settings. Check the destination before entering anything. Logging and attribution vary by operation; do not rely on a universal full-content audit or automatic undo.

Troubleshooting without expanding access

  • No tools or denied call: check interface, plugin setting, store, role, module and agent policy. Do not grant administrator access just to remove the error.
  • Wrong store: inspect context and switch only to the intended authorised store.
  • Confirmation unavailable: check client support and key configuration. Do not bypass a required confirmation by choosing another transport.
  • Timeout after a write: inspect the actual result in Kaduno and any destination before retrying. A disconnected client does not prove the operation failed.

Continue with integration administration and launch and support. This is source-reviewed guidance, not a completed connection test for your store.