Skip to content

Usage

After you create a connection, the page shows the token and ready configurations with your endpoint and token filled in:

  • Claude Code: claude mcp add --transport http cs-cart "<endpoint>" --header "Authorization: Bearer <token>"
  • Cursor (.cursor/mcp.json) and VS Code (.vscode/mcp.json): URL plus an Authorization header.
  • Claude Desktop (claude_desktop_config.json): through npx mcp-remote with the header (needs Node.js).
  • Other MCP clients (n8n MCP Client, agent frameworks): URL, transport Streamable HTTP, header Authorization: Bearer <token> (or X-Api-Key: <token>).
  • Clients without custom headers (custom connectors of claude.ai and ChatGPT): enable Connector URL with key on the connection and paste the connector URL. Anyone with this URL can use the connection: keep it private.

Then ask in plain language, for example:

  • “Compare this week’s sales with last week and list the best sellers.”
  • “Which orders from the last 3 days are still Open?”
  • “Which active products have 3 or fewer in stock?”
  • “Show customer [email protected] and her last orders.”
  • “Rewrite the meta description of product 12 around ‘waterproof hiking boots’ and send it for approval.”
  • “Mark order 1045 as Complete without e-mailing the customer.”

Write tools never change the store directly. Each call creates a change request; the agent is told that it waits for approval.

Website > AI Agent Connector > Change requests lists pending requests with the product or order, the connection, the agent’s reason and the old and new value. Approve or reject each request, or tick several and use Approve selected / Reject selected.

On approval the add-on checks that the stored value still equals the old value. If someone changed it in the meantime, the request becomes Stale and nothing is written. Order status changes run the normal CS-Cart status change (stock, payment and notification rules); the customer gets the status e-mail only when the agent asked for it.

The agent can check the result with the list_change_requests tool.

Every call is logged with time, connection, tool, arguments, result and duration, including refused tokens and rate-limit hits. The cards on top show active connections, pending requests and the calls and errors of the last 24 hours.

Tool Scope
get_store_info any
get_sales_summary, get_top_products reports.read
search_orders, get_order orders.read
search_products, get_product, get_low_stock, list_categories catalog.read
search_customers, get_customer customers.read
update_product_price, update_product_stock, update_product_status, update_product_content catalog.write
update_order_status orders.write
list_change_requests catalog.write or orders.write

Revenue counts orders in the statuses marked “payment received” in Administration > Order statuses.