Rules MCP: 1C exchange rules parser
rules-mcp
An MCP server that parses 1C exchange rules in Data Conversion 2.0 format and answers questions about them in chat, with no LLM involved in the parsing itself
- 5 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The server parses local Data Conversion 2.0 exchange rule XML into an in-memory index
- Does not connect to production, rule reload is password protected
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/rules-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The server parses local Data Conversion 2.0 exchange rule XML into an in-memory index
- Does not connect to production, rule reload is password protected
This is third-party code. Review the repository files before installing.
What it does
The server parses multi-megabyte exchange rule XML files (ExchangeRules.xml and RegistrationRules.xml in Data Conversion 2.0 format) once into an in-memory index with a plain program, no model involved, so tokens are spent only on answers. Eight tools answer questions: an overview of exchange directions, tracing a document from registration to the receiver, a full conversion rule card, searching by code or text, the full text of a rule or attribute handler page by page with line numbers, breaking a handler's queries into individual queries and temp tables, and what the rules expect from receiver attributes for reconciliation. The tools also understand shared algorithms that rules call via Выполнить(Алгоритмы.Имя), and individual attribute handlers.
Who it is for. For 1C developers who work with or debug Data Conversion 2.0 exchanges and want to ask questions about the rules directly in chat.
Good fit when
- You need to quickly understand what a specific conversion rule does without opening the XML by hand
- You need to trace where and how a document is processed during exchange
- You need to reconcile what the rules expect from the receiver configuration with the real attributes
Not a fit when
- The exchange is built on Data Conversion 3 (EnterpriseData): the server supports only Data Conversion 2.0
- You need a ready MCP server that reads the 1C configuration itself: rules-mcp only works with exchange rule files
Example request
Show what happens to the sales document during the UPP to ERP exchange, and where each rule call sitsMCP
- Transport
- stdio, http
- Authentication
- not required
Environment variables
RULES_REFRESH_PASSWORDsecret- Password for the refresh_rules tool, which rereads the rules from the repository.
Limitations
Only Data Conversion 2.0 is supported; EnterpriseData (Data Conversion 3) is not read. The rules must sit locally in a specific folder structure by exchange direction. The CorrespondentExchangeRules.xml file is not read. The index lives in memory with no database, and the refresh_rules tool for rereading is password protected.
How to disable. Stop the server container or process and remove the rules-mcp entry from your Open WebUI MCP client settings.
FAQ
Does an LLM take part in parsing the rules?
No, the XML parsing is a plain program; model tokens are spent only on what the tool returns in chat.
Can the rules be checked against the real configuration?
Yes, if a server reading 1C configurations is connected alongside it, such as rlm-tools-bsl, the model compares data from rules-mcp against real attributes.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsAn MCP server for 1C exchange rules: an agent reads, builds, edits and validates Data Conversion 2 and 3 rules
Rules, subagents, skills and MCP integrations for 1C:Enterprise 8 development with Cursor, Claude Code, Codex and other agents
An MCP server and portable admin tool for analyzing an exported 1C XML configuration: object listing, metadata structure, code search
1C managed forms MCP server
1c-formsserver
An MCP with 18 tools for generating, validating and converting 1C managed forms between the Configurator, Managed and EDT formats
A native component that runs a full MCP server inside 1C: tools, resources and prompts are written in BSL, while a DLL handles the protocol
A stdio MCP server that indexes a 1C structure XML export and code into SQLite and gives an agent search over objects and procedures
README in short
The README lays out the problem: exchange rules are tens of megabytes of XML with embedded code, impossible to read blindly or in full. The server parses them once into an index and answers precisely. It lists eight tools with their purpose, the folder layout for storing rules by exchange direction, and the idea of pairing it with a separate server reading 1C configurations for automatic reconciliation.