saby-mcp-ro: a read-only MCP server for Saby (SBIS)
saby-mcp-ro
Read-only access to the Saby API: incoming documents, tasks, counterparties and certificates, with no write commands in the code
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- A Saby session opens reading of documents, contracts and counterparty data
- The incoming summary prints document titles and amounts into the agent chat
Install
- Works in
- Services
Manual install
pip install -e .From a repository clone; then `saby-mcp login`, and a `saby` server with the `saby-mcp` command goes into the client configuration.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- A Saby session opens reading of documents, contracts and counterparty data
- The incoming summary prints document titles and amounts into the agent chat
This is third-party code. Review the repository files before installing.
What it does
The MCP server lets an agent read Saby (SBIS) data: documents, tasks, counterparties, organizations and certificates. The code has no write or delete commands, so neither an agent mistake nor prompt injection can change anything in the account. The agent searches for a command by words (`saby_search`), reads its parameters (`saby_describe`) and calls it (`saby_call`); `saby_doc_types` turns "invoice" into the `СчетИсх` type. The `saby_digest` tool builds a summary of incoming items in one call: what arrived, which tasks wait on you, what changed since last time. The `saby-mcp digest` terminal command prints the same summary. The server pages through long lists itself, respecting each command page ceiling.
Who it is for. Accountants and managers whose document flow runs through Saby, and anyone who wants to ask an agent about incoming items without worrying about changing anything.
Good fit when
- In the morning you want a summary of incoming items and your tasks without opening the account
- You must find the month invoices and reconcile amounts for a counterparty
- An assistant sorts documents, but you do not want to trust it with writing to Saby
- The Saby command is unknown and easier to find by a search in Russian
Not a fit when
- You need to create, sign or send a document: the server cannot write
- You work with another EDI operator: the server knows only the Saby API
- You need sign-in by certificate or application token: the server signs in with login and password
Example request
Show the incoming items for October and tell me which tasks have been waiting on me for over a monthMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
SBIS_SESSION_IDsecret- A ready Saby session id instead of login sign-in
SABY_MCP_HOME- Server data directory, `~/.saby-mcp` by default
Limitations
The server signs in with login and password, the password is never stored, and the issued session id sits in `~/.saby-mcp/session.json` and lives 21 days; a ready session can be passed in `SBIS_SESSION_ID`. Installation runs from a repository clone with `pip install -e .`, and the README mentions no PyPI package. Each Saby command has its own paging method and ceiling, and some commands, such as the invitation changes list, page incompletely. The registry window follows the event date, and the document date plays no part.
How to disable. Remove the `saby` block from the client configuration and delete the session from `~/.saby-mcp/session.json`.
FAQ
Can the agent change anything in Saby?
No: the server code has no write or delete commands, only the catalog of read commands is available.
How do I sign in to Saby?
Run `saby-mcp login` and enter login and password; then `saby-mcp doctor --live` shows who you are signed in as.
How do I get the incoming summary without an agent?
With `saby-mcp digest`; the `--days 7` and `--since 01.10.2026 --until 12.10.2026` flags set the window, `--save` remembers its end as a cursor.
How does the assistant find the right Saby command?
It searches by words with `saby_search`, in Russian or English, reads parameters in `saby_describe` and calls `saby_call`.
What to do when the session expires?
Run `saby-mcp login` again or put a new id into `SBIS_SESSION_ID`; `saby-mcp doctor --live` checks the sign-in.
Discussion
No questions or reviews yet.
Related
All Saby (SBIS) toolsUnofficial MCP server for Saby (SBIS) EDI: the agent reads documents, events, counterparties and attachments without signing anything
SBIS (Saby) API MCP server
sbis-mcp-ru
An MCP server for SBIS (Saby): documents and workflow stages, signing, certificates, powers of attorney, employees and counterparties
A local document base for your agent: hybrid semantic and keyword search plus a web UI for browsing and uploads
MCP PDF for large documents: the agent searches by meaning and keyword across one file or a folder and reads only the pages, tables and scans it needs
An MCP server with full-text search over local 1C:Element documentation, including your own markdown and PDF files
An MCP server for the 1C platform API docs read straight from shcntx_ru.hbk help files, with keyword, semantic and hybrid search
README in short
The README goes from installation and sign-in to client setup, describes the tools and the incoming summary, and ends by explaining why writing is impossible in this server. It includes paging measurements from October 15 and 16, 2026.