Kash — POS, Invoicing, CRM & Webshop

Kash: касса, счета, CRM и интернет-магазин для малого бизнеса через AI-ассистента

От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноМожет изменять данные

Что умеет

  • Регистрировать продажи и заказы с привязкой к столам или клиентам
  • Управлять каталогом товаров, отделами и ставками НДС
  • Вести базу клиентов с контактами и историей покупок
  • Получать отчёты по продажам, кассам и ожидающим заказам
  • Создавать учётную запись Kash и входить по одноразовому коду

Какие данные видит

Ассистент получает доступ к данным конкретного магазина Kash после аутентификации владельца через OTP или OAuth.

Нужен ли аккаунт

Не нужен: сервер работает без входа

Kash — бесплатная облачная платформа для управления бизнесом с 2011 года: касса, счета и накладные, CRM, интернет-магазин, склад и доставка. Официальный MCP-сервер даёт ассистенту 35 инструментов для регистрации продаж, ведения каталога, работы с клиентами и получения отчётов через обычный диалог. Подключение защищено OAuth 2.0 с PKCE.

Как подключить

Как подключить Kash — POS, Invoicing, CRM & Webshop к Claude

Адрес сервера, который нужно вставить в настройках Claude:

https://kash.run.tools

  1. Откройте Claude (сайт claude.ai или приложение для компьютера).
  2. Перейдите в Настройки → Коннекторы (в английском интерфейсе: Settings → Connectors).
  3. Нажмите Добавить пользовательский коннектор (Add custom connector).
  4. Вставьте адрес сервера, скопированный ниже, в поле URL удалённого MCP-сервера и нажмите Добавить.
  5. В чате нажмите + → Коннекторы и включите новый коннектор.

Пользовательские коннекторы доступны на тарифах Free, Pro, Max, Team и Enterprise. На Free можно добавить только один. В Team и Enterprise коннектор сначала добавляет владелец организации в Настройки организации → Коннекторы.

Авторизация

После нажатия Добавить откроется окно входа в сервис. Войдите под своим аккаунтом и подтвердите доступ. Пароль Claude не видит.

Как подключить Kash — POS, Invoicing, CRM & Webshop к ChatGPT

Адрес сервера, который нужно вставить в настройках ChatGPT:

https://kash.run.tools

  1. Откройте ChatGPT в браузере (chatgpt.com). Нужен тариф Plus, Pro, Business, Enterprise или Edu.
  2. Один раз включите режим разработчика: Настройки → Приложения → Дополнительные настройки → Режим разработчика (Settings → Apps → Advanced settings → Developer mode).
  3. Откройте Настройки → Коннекторы и нажмите Создать (Create).
  4. Заполните форму: Название (любое), Описание (одна фраза, что делает сервис), URL MCP-сервера (скопируйте ниже).
  5. В поле Аутентификация выберите OAuth, если сервис требует вход, иначе Нет. Нажмите Создать.
  6. В новом чате откройте + → Приложения/Коннекторы и включите коннектор.

Название раздела у OpenAI менялось (Connectors → Apps/Plugins). Если пункт называется иначе, ищите «режим разработчика» в настройках. В рабочих пространствах Business/Enterprise администратор должен разрешить пользовательские коннекторы.

Авторизация

При первом использовании ChatGPT откроет окно входа в сервис. Войдите и подтвердите доступ.

Как подключить Kash — POS, Invoicing, CRM & Webshop к Cursor

Адрес сервера, который нужно вставить в настройках Cursor:

https://kash.run.tools

Быстрый способ: нажмите кнопку Открыть в Cursor ниже, Cursor сам предложит добавить сервер.

Вручную:

  1. В Cursor откройте Settings → Cursor Settings → MCP и нажмите Add new global MCP server.
  2. Вставьте JSON, скопированный ниже, в открывшийся файл ~/.cursor/mcp.json (для одного проекта: .cursor/mcp.json в корне проекта).
  3. Сохраните файл. Сервер появится в списке MCP; при необходимости пройдите авторизацию по кнопке рядом с ним.

Авторизация

Если сервис требует вход, рядом с сервером в списке MCP появится кнопка авторизации.

Список инструментов сервера (39)

Технические названия из tools/list. Нужны только разработчикам.

account_listList all Kash / free-cash-register.net accounts linked to an email address. Use this before account_create to check if the user already has an account. Returns an array of accounts, each with accountTitle, accountID, and a getOTPForAccount URL that can be used to request a one-time password (OTP) to retrieve the APIKEY. This endpoint is public and requires no authentication.
account_createCreate a new Kash / free-cash-register.net account. Requires an email address and a shop name (accountTitle). Optional: configType to pre-load a dataset matching your business type (e.g. 'Restaurant', 'Bakery', 'Bar', 'Retail'...), plus address and legal info. On success, returns APIKEY and SHOPID and automatically initializes the session so all other tools can be used immediately. IMPORTANT: the user must validate their email via the link sent automatically, otherwise the account may be deleted after a period of inactivity.
auth_request_otpStep 1 of 2 for in-conversation authentication. Sends a one-time password (OTP) to the user's email address. If the user has multiple accounts, provide accountID (obtained from account_list) to target the right one. On success, an OTP code is sent by email — then call auth_login_with_otp with that code.
auth_login_with_otpStep 2 of 2 for in-conversation authentication. Exchange the OTP received by email for an APIKEY and SHOPID, and automatically initialize the session so all other tools work immediately. Call auth_request_otp first to receive the OTP by email.
account_editModify the settings of the authenticated shop account. All fields are optional. Covers: basic info (name, address, legal numbers), receipt display options, order requirements, feature flags (stock, barcodes, variations, webshop, coupons...), delivery method toggles, and third-party integrations (PayPal, Prestashop, Yavin, Viva.com).
account_show_infosRetrieve all current settings of the authenticated shop account as a JSON object. Returns the full shop configuration: name, address, legal numbers, receipt options, order requirements, enabled features, delivery methods, webshop colours, and third-party integration settings. Use this to verify invoice prerequisites before creating orders: shopName, adressline1, and companyRegistrationNum must all be set for legally valid invoices. If any are missing, prompt the user to fill them in via account_edit.
auth_logoutClear the current authentication session (APIKEY and SHOPID). After this, all tools requiring authentication will fail until a new login is performed.
report_getDownload a synthetic HTML sales report for a given period. Period logic: omit all date fields to get yesterday's report; provide y only for a full-year report; y + m for a full-month report; y + m + d for a specific day. Returns an HTML summary including total revenue, number of orders, breakdown by department, VAT summary, and payment methods.
order_createRecord a new order in the connected shop. Input includes paymentMode, and items[]. Each item can be of type 'catalog' (with productId), 'department' (with price and deptId) or 'free' (with title and price). Check if the client already exists using data_list_clients and if the client exists, only specify idClient. If provided, paymentMode should correspond to a payment ID from data_list_payments_modes tool. Returns a sale confirmation JSON including: a link to the PDF invoice, and a link to a private order page showing full order details which can also be used by the client to pay online. IMPORTANT: before creating a validated invoice (payment ≠ -2), call account_show_infos to verify that shopName, adressline1, and companyRegistrationNum are all set. If any of these fields are empty, warn the user and suggest using account_edit to fill them in before issuing invoices.
order_editModify an existing order by its ID. Use the payment field to control the order state: -2 = keep as unvalidated quote (not paid); -1 = validate as invoice without payment; a payment method ID (from data_list_payments_modes) = record an actual payment and validate the order. Use paymentAmount to specify a partial payment amount (omit for full payment). Items can only be added or changed on unvalidated orders. Once validated, only payments can be recorded. Returns the orderID, a payment link, and a PDF invoice or quote URL.
data_list_productsRetrieve the list of articles (products) configured in the shop. Returns an array of products with fields like id, title, price, and departmentId. Optional parameter 'format' allows output as json, csv, or html.
data_list_departmentsGet all departments (product categories) defined in the shop, including their names and default tax rates. Supports format=json|csv|html.
data_list_department_groupsReturn the list of department groups, used to organize product categories. Each group may include multiple department IDs.
data_list_clientsGet the list of clients registered in the shop, including contact info, loyalty points.
data_list_variationsRetrieve product variations (declinaisons) such as size or color. Returns an array of variant definitions with value and optional price delta.
data_list_delivery_menList all delivery methods available for the shop, such as in-store pickup, home delivery, or courier services.
data_list_payments_modestools.data.list.payments.description
data_list_cashboxesList the registered cashboxes (physical or virtual) linked to the shop, including their current status and identifiers.
data_list_delivery_zonesReturn all configured delivery zones, including area names, postal codes, and applicable delivery fees or restrictions.
data_list_relay_pointsList all relay points where customers can pick up their orders, including address, city, and postal code.
data_list_discountsReturn all available discounts or promotions, including their names, types (percentage or fixed), values, and conditions.
data_list_usersList all users (cashiers, managers, etc.) associated with the shop, including their roles and identifiers.
data_list_tablesRetrieve the list of tables configured in the app, used for restaurant mode or table management.
data_list_vatsRetrieve the list of VAT rates configured in the shop, including their title, rate percentage, and optional accounting chapter.
data_list_pending_ordersRetrieve the list of unvalidated orders (that can still be modified)
data_list_ordersList either: unvalidated orders (called quotes) with creation date between from_date_ISO8601 and to_date_ISO8601 OR validated orders (called orders, invoices) with date of value between from_date_ISO8601 and to_date_ISO8601. You can also filter delivery methods (using filterDeliveryMethod).
order_detailRetrieve full order information by its unique ID, including items, client data, payment mode, and total amount.
vat_addAdd a new VAT rate to the shop configuration. Requires a title and a rate (e.g. 20 for 20%). Optional fields: accountingChapter, legal mention.
vat_editModify an existing VAT rate by its ID. All fields are optional except the ID.
vat_deletePermanently remove a VAT rate from the shop configuration by its ID.
plu_addAdd a new item/article to the shop catalog. Requires a title. Optional fields include price, department (deptID), VAT rate (vatID), barcode, stock, variations, and many more.
plu_editEdit an existing item/article in the catalog by its ID. All fields are optional except the ID. Use data_list_products to find the article ID first.
plu_deletePermanently remove an item/article from the catalog by its ID.
dept_addAdd a new department (product category) to the catalog. Requires a title. Optional fields include VAT rate (vatID), price, discount, position, department group, and variations.
dept_editEdit an existing department/category by its ID. All fields are optional except the ID. Use data_list_departments to find the department ID first.
dept_deletePermanently remove a department/category from the catalog by its ID.
client_addAdd a new customer to the shop's customer file. All fields are optional: name, surname, email, phone, address, company registration number, VAT number, barcode, private/public comment, blacklist status, birth date, etc. Use data_list_clients to check if the customer already exists first.
client_editEdit an existing customer by their ID. All fields are optional except the ID. Use data_list_clients to find the customer ID first.
client_deletePermanently remove a customer from the shop's customer file by their ID.