Skip to main content
Glama

sbis-mcp-ru

API СБИС (Saby) для ИИ-ассистентов: документы и этапы документооборота, подписание вложений, сертификаты и МЧД, сотрудники, контрагенты, подразделения.

PyPI CI License: MIT Методов Сайт Звёзды

Install in VS Code Install in Cursor

Каталог собран из первоисточника (справка saby.ru/help/integration/api) и лежит в репозитории как sbis_mcp/endpoints.yaml: 45 методов, из них 19 на чтение, 21 на запись и 5 необратимых. Сервер исполняет ровно этот файл, поэтому таблица ниже не может разойтись с кодом.

Установка

Два пути, выбирайте по тому, есть ли у вас терминал.

Без терминала: файл .mcpb

Скачайте sbis-mcp-ru-vX.Y.Z.mcpb со страницы релизов и откройте двойным щелчком. Claude Desktop поставит сервер сам и спросит ключи в отдельном окне, в конфиг лезть не придётся. Нужен Python 3.10 или новее: зависимости сервер доставит себе при первом запуске.

В терминале

uvx sbis-mcp-ru

Claude Desktop, claude_desktop_config.json:

{
  "mcpServers": {
    "sbis-mcp": {
      "command": "uvx",
      "args": ["sbis-mcp-ru"],
      "env": { "SBIS_SESSION_ID": "..." }
    }
  }
}

Related MCP server: chestny-znak-mcp-ru

Ключи

Команда СБИС.Аутентифицировать по логину и паролю сотрудника с правами на API возвращает идентификатор сессии. Сессия живёт ограниченное время и обновляется той же командой, пароль в сервере не хранится.

переменная

секрет

что это

SBIS_SESSION_ID

да

Идентификатор сессии Saby (СБИС) от команды СБИС.Аутентифицировать.

Ключи можно не держать в окружении: сервер умеет кабинеты и кладёт их в ~/.ru-mcp/cabinets.json с правами 600, вне репозитория.

Карта методов

раздел

методов

чтение

запись

необратимое

Документы и этапы

19

7

8

4

Аутентификация

9

3

6

0

Электронная подпись

4

2

2

0

МЧД

4

2

1

1

Наши организации

3

2

1

0

Сервисные команды

3

2

1

0

Сотрудники

2

0

2

0

Контрагенты

1

1

0

0

всего

45

19

21

5

Как это выглядит в чате

Вы: список документов

sbis_search_methods("список документов")
  sbis_spisok_dokumentov               POST /service/  чтение
  sbis_spisok_dokumentov_po_sobytiyam  POST /service/  чтение
  sbis_spisok_izmeneniy                POST /service/  чтение

sbis_describe_method("sbis_spisok_dokumentov")
  Возвращает список документов указанного типа
  POST online.sbis.ru/service/
  параметры: {"jsonrpc":"2.0","method":"СБИС.СписокДокументов","params":{},"id":0}
  класс доступа: чтение

sbis_call_method("sbis_spisok_dokumentov", {})

Три инструмента вместо 45 функций: агент ищет метод словами, читает его карточку и вызывает. Запись и необратимое спрашивают подтверждение.

Что обычно просят:

  • Выгрузить список документов нужного типа за период.

  • Посмотреть, на каком этапе застряли исходящие документы.

  • Проверить статус сертификатов подписи до того, как они истекут.

  • Найти контрагента и его идентификатор участника ЭДО.

Безопасность

Сервер работает на машине пользователя, ключи наружу не уходят. У методов три класса доступа: чтение идёт сразу, запись и необратимые действия требуют подтверждения. Заголовок авторизации не покидает домены сервиса даже при вызове произвольного пути.

Проверить установку

uvx sbis-mcp-ru doctor

Печатает, сколько методов загрузилось, найдены ли ключи и откуда. Секреты не показывает. С --live делает один дешёвый реальный вызов на чтение.

Родня

Ядро вынесено в schema-mcp-core. Соседние серверы: vk-mcp-ru, diadoc-mcp-ru, chestny-znak-mcp-ru. Маркетплейсы живут отдельно: marketplaces-mcp-ru.

MIT. Автор Илья Утов.

Все проекты одним списком, разобранные по назначению: ilyautov.github.io.

Privacy Policy

sbis-mcp-ru не собирает и не передаёт ваши данные: ключи лежат локально в ~/.ru-mcp/cabinets.json, запросы идут только в API СБИС (Saby), телеметрии нет. Полный текст: PRIVACY_POLICY.md.

Available Tools

18 tools
sbis_add_cabinetA
Idempotent

Add or update a cabinet (a named set of API credentials), from chat.

⚠️ This puts the key into the chat transcript — requires i_understand_key_goes_to_chat=true. The terminal-free safe alternative is the installer (install.py / double-click), where the key never enters chat.

Args: credentials: dict with the required fields for this service ({fields}). For Ozon: {{"client_id": "...", "api_key": "..."}}; for WB: {{"token": "..."}}. name: optional label. If omitted, the cabinet is named after the real shop name fetched from the marketplace (falls back to "main"). i_understand_key_goes_to_chat: must be true to proceed. Saved to ~/.marketplace-mcp/cabinets.json (local, chmod 600), never echoed.

Inputs: credentials (required), name, i_understand_key_goes_to_chat. Returns: result

sbis_call_methodA
Read-only

Execute one READ endpoint from the catalog by operation_id.

Target API: https://saby.ru/help/integration/api.

Reads only: nothing here changes data, so it runs without confirmation. To change data use sbis_write_method, to delete use sbis_delete_method.

Args: operation_id: id from the catalog (see sbis_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body (a few read endpoints take one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Inputs: operation_id (required), body, query, path_values. Returns: result

sbis_check_authA
Read-only

Check whether the required credentials are present in the environment.

Does NOT reveal secret values — only reports which variables are set. Returns JSON: {"ready": bool, "missing": [str], "required": [str]}.

Inputs: no named parameters. Returns: result

sbis_delete_methodA
Destructive

Execute one DESTRUCTIVE endpoint: deletes or irreversibly changes data.

Target API: https://saby.ru/help/integration/api.

Both confirm_write=true and i_understand_this_modifies_data=true are required; nothing is sent without both.

Args: operation_id: id from the catalog (see sbis_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body. confirm_write: must be true. i_understand_this_modifies_data: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Inputs: operation_id (required), body, query, path_values, +2 more. Returns: result

sbis_delete_rawA
Destructive

Delete data at ANY path, including paths not in the catalog.

Target API: https://saby.ru/help/integration/api.

DELETE only. Both confirm_write=true and i_understand_this_modifies_data=true are required.

Args: path: full path beginning with '/'. method: DELETE. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body. confirm_write: must be true. i_understand_this_modifies_data: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Inputs: path (required), body, host, query, +3 more. Returns: result

sbis_describe_methodB
Read-only

Return the full catalog record for one endpoint: method, host, path, scope, safety level, pagination style, rate limit, params and doc URL.

Inputs: operation_id (required). Returns: result

sbis_fetch_allA
Read-only

Auto-paginate a read endpoint and return every row in one response.

Handles offset, last_id, cursor (Ozon v4/v5), page and WB lastChangeDate styles. The array path is taken from the catalog automatically.

Args: operation_id: a read endpoint from the catalog. query / body / path_values: base parameters (cursor fields are managed). items_path: override the array path (default: the endpoint's own). limit: page size to request. max_items: hard cap to protect context (default 10000). Returns JSON: {"ok", "items", "total_fetched", "pages_fetched", "truncated"}.

Inputs: operation_id (required), body, limit, query, +3 more. Returns: result

sbis_get_rawA
Read-only

Read ANY endpoint by path, including ones missing from the catalog.

Target API: https://saby.ru/help/integration/api.

Safe verbs only (GET, HEAD, OPTIONS). To change data use sbis_write_raw, to delete use sbis_delete_raw.

Args: path: full path beginning with '/', e.g. "/". method: safe verb, GET by default. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body (rare on reads; some APIs want one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Inputs: path (required), body, host, query, +1 more. Returns: result

sbis_get_sectionA
Read-only

List all endpoints in one section.

Args: section: section name (see sbis_list_sections), e.g. "statistics". Returns JSON list of {operation_id, method, path, safety, summary}.

Inputs: section (required). Returns: result

sbis_list_cabinetsA
Read-only

List configured cabinets for this marketplace and which one is active.

Returns JSON: {"active": str|null, "cabinets": [names], "fields_needed": [...]}. Secret values are never returned.

Inputs: no named parameters. Returns: result

sbis_list_sectionsA
Read-only

List API sections and how many catalog endpoints each contains.

Inputs: no named parameters. Returns: result

sbis_mapA
Read-only

The big picture: business entities this API covers and the go-to methods for each. Call with no args to see the whole map ("you are here"); pass entity="reviews" (or stocks/prices/orders/…) to list every method of one entity. Use this before guessing — it orients you fast.

Inputs: entity. Returns: result

sbis_remove_cabinetB
Destructive

Delete a stored cabinet. If it was active, another becomes active.

Args: name: the cabinet to remove.

Inputs: name (required). Returns: result

sbis_search_methodsA
Read-only

Search the endpoint catalog by keyword (works in Russian and English).

Args: query: free text, e.g. "остатки", "stocks", "update price". limit: max results (1-50). Returns JSON list of matching endpoints (best first).

Inputs: query (required), limit. Returns: result

sbis_set_keyA
Idempotent

Change / rotate the API key from chat (e.g. the old one expired or leaked).

⚠️ The key goes into the chat transcript — requires i_understand_key_goes_to_chat=true. The safe, terminal-free alternative is the installer, where the key never enters chat. Use a scoped key and rotate it in the seller cabinet if it was exposed.

Args: credentials: dict with the required fields ({fields}). cabinet: which cabinet to update. Default: the active one (so "my key expired" just works). If there is none, the cabinet is named from the marketplace's shop name, else "main". i_understand_key_goes_to_chat: must be true to proceed. On success the key is validated against the marketplace and the shop name is reported. Saved locally (chmod 600), never echoed back.

Inputs: credentials (required), cabinet, i_understand_key_goes_to_chat. Returns: result

sbis_use_cabinetA
Idempotent

Switch the active cabinet. Subsequent API calls use its credentials.

Args: name: the cabinet to activate (see sbis_list_cabinets).

Inputs: name (required). Returns: result

sbis_write_methodA

Execute one WRITE endpoint from the catalog: create or update data.

Target API: https://saby.ru/help/integration/api.

Requires confirm_write=true; nothing is sent without it. Irreversible operations live in sbis_delete_method, reads in sbis_call_method.

Args: operation_id: id from the catalog (see sbis_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body. confirm_write: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Inputs: operation_id (required), body, query, path_values, +1 more. Returns: result

sbis_write_rawA

Create or update data at ANY path, including paths not in the catalog.

Target API: https://saby.ru/help/integration/api.

POST, PUT and PATCH only; requires confirm_write=true.

Args: method: POST, PUT or PATCH. path: full path beginning with '/'. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body. confirm_write: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Inputs: path (required), method (required), body, host, +2 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    The tools are mostly distinct: catalog exploration tools (sbis_list_sections, sbis_get_section, sbis_search_methods, sbis_map, sbis_describe_method) are clearly separated from execution tools (sbis_call_method, sbis_write_method, sbis_delete_method) and raw variants (sbis_get_raw, sbis_write_raw, sbis_delete_raw). The main ambiguity is between sbis_get_section and sbis_list_sections, which both sound like listing sections, though their descriptions clarify one lists all sections and the other lists endpoints in one section.

    Naming Consistency4/5

    All tools follow the sbis_ prefix and use lower_snake_case verbs (check, get, search, map, call, write, delete, fetch, list, add, set, use, remove, describe). The naming is mostly consistent, with minor deviations: sbis_map as a noun-like verb is less descriptive than the others, and sbis_set_key overlaps conceptually with sbis_add_cabinet for credential updates. Overall the pattern is predictable.

    Tool Count4/5

    18 tools is slightly on the higher side but appropriate for a server that covers both catalog discovery, curated execution, raw execution, and credential/cabinet management. The count is justified by the breadth of the domain and the need for both catalog-driven and raw HTTP access variants.

    Completeness5/5

    The server provides complete coverage: discovery (sections, search, map, describe), safe execution (call), write execution (write), destructive execution (delete), raw access for uncataloged endpoints (get/write/delete_raw), pagination handling (fetch_all), and all credential lifecycle operations (list, add, set, use, remove). No significant gaps for the stated purpose of integrating with Saby/marketplace APIs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to authenticate users, manage calendar events, create meetings, and maintain persistent API sessions for seamless integration with Russian business platforms. Provides comprehensive business productivity capabilities including session management, password operations, and cross-user calendar coordination.
      -
    • A
      license
      A
      quality
      B
      maintenance
      VK API for AI assistants: wall posts, communities, messages, market items, ads and stats. 373 methods in one catalog, each with a read/write/destructive safety class; the agent searches methods in plain language instead of receiving 373 tools.
      18
      78 PyPI
      3
      MIT