Skip to main content
Glama
sbis-mcp

sbis-mcp

by pyrfor

sbis-mcp

License: MIT

Read-only MCP server for Saby (СБИС) EDI — list/read documents and counterparties via the official JSON-RPC API, so agents can see legally significant paperwork without copy-paste.

⚠️ Unofficial. Not affiliated with Tensor LLC / Saby. Needs your own Saby account with API access.
v0.1 is read-only. Digital signatures (КЭП) and write paths are out of scope until v0.2.

⚠️ Неофициальный. Не аффилирован с ООО «Тензор» / Saby. Нужен свой аккаунт.
v0.1 — только чтение. КЭП и запись — не в этом релизе.

Proof — seven tools (v0.1)

Tool

SBIS method

sbis_config

—

sbis_current_user

СБИС.ИнформацияОТекущемПользователе

sbis_list_documents

СБИС.СписокДокументов

sbis_list_documents_by_event

СБИС.СписокДокументовПоСобытиям

sbis_read_document

СБИС.ПрочитатьДокумент

sbis_list_counterparties

СБИС.СписокКонтрагентов

sbis_get_attachment

GET by temporary link

Writes (ЗаписатьДокумент, ПодготовитьДействие, …) stay off until v0.2 (writable, default false).

Related MCP server: procurement-knowledge-mcp

First use

Env (recommended):

export SBIS_LOGIN="<LOGIN>"
export SBIS_PASSWORD="<PASSWORD>"
# optional:
export SBIS_BASE_URL="https://online.sbis.ru"   # test: https://fix-online.sbis.ru
export SBIS_ACCOUNT="<ACCOUNT>"

Or ~/.sbis-mcp/config.json:

{
  "login": "<LOGIN>",
  "password": "<PASSWORD>",
  "baseUrl": "https://online.sbis.ru",
  "writable": false
}

Build & run (Node.js ≥ 18):

npm install
npm run build
npm start

Claude Desktop example: examples/claude_desktop_config.json.

Limits (from Saby docs)

  • Auth: ≤300 calls/min per IP

  • Session sid: ~21 days (X-SBISSessionID)

  • Attachment: ≤73 MB, up to 10 per document

  • Temporary file links: ~1 month

Source: saby.ru tech requirements

API docs: JSON-RPC format · auth · documents · counterparties

Live smoke & tests

Live smoke is manual (real account + tariff «Обмен с контрагентами»):

npm run build
SBIS_LOGIN="…" SBIS_PASSWORD="…" node scripts/live-smoke.mjs

Unit tests mock RPC — no live account:

npm test

License

MIT — see LICENSE.

Available Tools

7 tools
sbis_configA

Check Saby/SBIS configuration status and setup instructions (read-only v0.1)

Inputs: no named parameters.

sbis_current_userC

Current authenticated user (СБИС.ИнформацияОТекущемПользователе). КЭП auth not supported in v0.1.

Inputs: extraFields.

sbis_get_attachmentA

Download attachment by temporary URL from read_document (GET, no sid). Pass includeContent:true for base64.

Inputs: url (required), includeContent.

sbis_list_counterpartiesC

Search counterparties by INN/KPP/name (СБИС.СписокКонтрагентов)

Inputs: inn, kpp, name, page, +2 more.

sbis_list_documentsC

List documents by type and period (СБИС.СписокДокументов). docType required: Реализация, Корреспонденция, etc.

Inputs: docType (required), mask, page, limit, +7 more.

sbis_list_documents_by_eventC

Registry lists: Входящие / Исходящие / Ответы от контрагентов (СБИС.СписокДокументовПоСобытиям)

Inputs: registryType (required), page, limit, state, +4 more.

sbis_read_documentC

Full document card with attachments metadata (СБИС.ПрочитатьДокумент)

Inputs: documentId (required), editionId, extraFields.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: user info, document listing by type, document listing by events, reading a document, counterparty search, attachment download, and config check. The two document listing tools are differentiated by their filter criteria.

    Naming Consistency4/5

    All tools follow the 'sbis_<action>_<noun>' pattern except 'sbis_current_user' (noun phrase) and 'sbis_config' (noun), which are minor deviations. The majority use 'list', 'read', or 'get' as verbs, maintaining overall consistency.

    Tool Count5/5

    Seven tools is an appropriate scope for a document management server, covering core retrieval operations without being overly numerous or sparse.

    Completeness2/5

    The server lacks any CRUD operations beyond reading and listing; there are no tools for creating, updating, or deleting documents or counterparties, which are essential for typical document workflows.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      MCP server for 1C:Enterprise ERP with 35 tools: metadata inspection, document CRUD, register queries, and BSP integration. First MCP server for Russian ERP systems (300,000+ organizations). JSON-RPC 2.0 compliant BSL implementation.
      51
      48
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for RAG-based search over 1C Enterprise configuration documentation, enabling natural language queries to find objects like справочники, документы, and отчеты.
      MIT