Yzel

Install

pip install yzel
yzel config add-1c

This is third-party code. Review the repository files before installing.

What it does

Yzel bundles connectors to CIS business systems into one Python package with a shared CLI and an encrypted local credential store. Each connector runs as a separate MCP server, so you add only what you need. The 1C connector reads the infobase schema from $metadata at startup, keeps Cyrillic object names and tells 1C:Fresh from on-premise publishing on its own. The other connectors use each service's public API and handle its rate limits and auth quirks.

Who it is for. Small businesses, marketplace sellers and 1C specialists who want to ask an agent about data from several systems at once.

Example request

Show the last 10 sales documents from 1C this week grouped by counterparty

Limitations

The project is alpha. 1C needs objects published via OData; writes cover only creating and updating documents, posting is not supported yet. The 1C connector is tested on mocks and on live 1C:Fresh transport, with full real-infobase testing awaiting community help. For amoCRM you enter ready tokens via the CLI; there is no browser login yet. iiko has no catalog service slug, but a connector exists.

How to disable. Remove the yzel-* blocks from the MCP config. Saved credentials live in ~/.yzel/store.db.

MCP

Transport

stdio

Authentication

not required

Security check

• Creates and updates 1C documents and CRM and marketplace data
• Stores credentials for several production systems on one machine
• The project is alpha and mostly tested against mocks

README in short

The Russian and English README explains why the connectors are bundled and details 1C specifics: streaming $metadata parsing, Cyrillic names, 1C:Fresh and Basic auth. It has a service table with auth methods, CLI commands to add connections and a Claude Desktop config via uvx. It lists limitations and plans honestly: WhatsApp, Kazakhstan public procurement, meeting platforms. MIT license.

Related