What it does

For store owners and teams who already work with an AI assistant. The add-on turns your store into a Model Context Protocol server: Claude, ChatGPT, Cursor, VS Code, n8n and other MCP clients can read sales, orders, products, stock and customers through 17 tools and propose changes. Each connection has its own token, scopes and expiry. No AI model or subscription is included: you use your own.

How it works

Open Website, AI Agent Connector, create a connection with the scopes you want and copy its token into your AI client with the ready configuration shown. The client calls the store's endpoint over Streamable HTTP. Reads are answered at once. Writes become change requests that you approve or reject, one by one or in bulk; auto-approve is optional per connection. Every call is logged. Nothing runs on the storefront.

Features

MCP server over Streamable HTTP, protocol versions 2025-06-18, 2025-03-26 and 2024-11-05
17 tools: store info, sales summary with previous period, best sellers, orders, products, low stock, categories, customers
Price, stock, status, product text and order status changes only through change requests
Approve or reject in bulk, old and new value side by side, stale guard and expiry
Access tokens with scopes, expiry, revoke, stored as hashes
Customer contact data only with its own scope, masked otherwise
Multi-Vendor connections limited to one vendor, optional vendor self-service
Connections limited to one storefront on CS-Cart Ultimate
Activity log and rate limit per connection
Ready configurations for Claude Code, Cursor, VS Code and Claude Desktop
Secret connector URL for clients without custom headers
Admin only, no storefront impact

What you get

Package	kv_mcp_connector-1.0.0.zip, installed through Add-ons → Manage add-ons
Updates & support	12 months included. Download new versions from your account and install them in Add-ons → Manage add-ons or the Upgrade Center.
License	1 production installation. Staging, dev and localhost are free and unlimited. The add-on keeps working after the update period ends. How licensing works

Compatibility

We list only the builds we install and test on. “Tested” means the full test plan was run on that build; “Supported” means the build is inside the supported range and uses the same hooks.

CS-Cart version and edition compatibility
CS-Cart version	CS-Cart	CS-Cart Ultimate	Multi-Vendor	Multi-Vendor Ultimate
4.22 and later	Testing next	Testing next	Testing next	Testing next
4.21.2	Supported	Supported	Supported	Supported
4.20.x	Supported	Supported	Supported	Supported
4.19.x	Supported	Supported	Supported	Supported
4.18.x	Supported	Supported	Supported	Supported
4.17.2	Supported	Supported	Supported	Supported
Before 4.17.2	Not supported	Not supported	Not supported	Not supported

Requirements

Requirement	HTTPS on the storefront for hosted clients (claude.ai, ChatGPT). Local clients (Claude Code, Cursor, VS Code) also work with HTTP on a test store
PHP	The web server must pass the `Authorization` header to PHP. Apache with CGI/FastCGI sometimes drops it; the add-on also reads `REDIRECT_HTTP_AUTHORIZATION`, and clients can send the token as `X-Api-Key` instead
Requirement	A firewall or "bot protection" in front of the store must let POST requests to the endpoint through
Core changes	None. Hooks and template overrides only

1.0.0

Nov 4, 2026

Latest

Added 7

MCP server on the storefront endpoint kv_mcp_connector.mcp: Streamable HTTP transport, JSON-RPC 2.0 with batches, protocol versions 2025-06-18, 2025-03-26 and 2024-11-05.
17 tools: store information, sales summary with the previous period and a daily series, best sellers, order search and details, product search and details, low stock, categories, customer search and details, price, stock, status, text and order status change requests, change request list.
Change requests with old and new value, stale guard, expiry, approve or reject one by one or in bulk, optional auto-approve per connection.
Connections with hashed access tokens, scopes, expiry, revoke and activate; Bearer, X-Api-Key and optional secret connector URL.
Customer contact data only with the customers.read scope and the setting; masked otherwise.
Multi-Vendor connections limited to one vendor and optional vendor self-service (Seller tools menu); CS-Cart Ultimate connections limited to one storefront.
Activity log with retention, rate limit per connection, copy-ready configurations for Claude Code, Cursor, VS Code, Claude Desktop and other clients.

Does the add-on include an AI model?

No. It lets the AI client you already use work with your store. Your AI provider bills its usage.

Can the AI change my store without me?

Not unless you allow it. Without write scopes the agent can only read. With write scopes it creates change requests that you approve. Only a connection with Auto-approve changes writes at once, and even then only price, stock, product status, product texts and order status. It cannot delete anything, create products, refund payments or change settings.

What customer data does the agent see?

With the customers.read scope and Share customer contact data on: names, e-mails, phones and shipping addresses of the customers and orders it reads. Otherwise first names and masked e-mails. Think about your privacy policy and your AI provider's data terms before you share personal data.

Which MCP version does it speak?

Streamable HTTP transport, protocol versions 2025-06-18, 2025-03-26 and 2024-11-05, JSON responses, tools capability. OAuth sign-in is not part of version 1.0: clients authenticate with the access token (header) or the secret connector URL.

My client gets 401.

Check that the token is copied fully, the connection is active and not expired, and that your server passes the Authorization header to PHP (try X-Api-Key instead). For the connector URL, both the setting and the connection option must be on.

My client gets 503.

The endpoint is disabled in the settings or the license is not active.

Does it slow down the storefront?

No. The endpoint answers only POST requests from AI clients; it adds no templates, scripts or styles to the storefront and is never cached.

Is the log or the change list affected by Multi-Vendor vendors?

Vendors see only their own connections, requests and log rows, and only when the administrator enables vendor connections.