kd31-rules

Automate Exchange Data conversion rule creation and management via the MCP-toolkit HTTP API.

43|9|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Desko77/cursor-1c-skills --skill kd31-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kd31-rules
Source: https://github.com/Desko77/cursor-1c-skills/tree/main/skills/kd31-rules
Command: npx skills add https://github.com/Desko77/cursor-1c-skills --skill kd31-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp-toolkit, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of working with Exchange Data conversion rules in 1C:Enterprise, making it easier to research, create, and modify rules, as well as manage the format and obtain artifacts for expanding the EnterpriseData format.

Core Features & Use Cases

  • Rule Management: Research and modify conversion rules for Exchange Data using the MCP-toolkit HTTP API.
  • Format Management: Configure the format of the EnterpriseData module manager and XDTO package expansion.
  • Artifact Retrieval: Obtain artifacts required for expansion of the EnterpriseData format.
  • Use Case: Imagine you need to create a new conversion rule for a specific data exchange in 1C:Enterprise. This Skill allows you to design and implement the rule efficiently.

Quick Start

Use the kd31-rules skill to create a new conversion rule for the 'Demo_ExpansionEnterpriseData' conversion.

Frequently Asked Questions about kd31-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the creation of Exchange Data conversion rules in 1C:Enterprise?

You can automate conversion rules by using the MCP-toolkit HTTP API to perform operations directly on the live information base, enabling efficient creation, inspection, and modification of rules in 1C:Enterprise 8.5.1.1302.

What is the process for expanding the EnterpriseData format in 1C:Enterprise?

Expanding the EnterpriseData format involves configuring the format of the module manager and XDTO package expansion, then retrieving the required artifacts to successfully implement the format expansion in your 1C:Enterprise environment.

Do I need MCP-toolkit to manage 1C:Enterprise conversion rules?

Yes, MCP-toolkit is a required dependency. You also need 1C:Enterprise 8.3 installed to ensure full functionality when automating and managing Exchange Data conversion rules through the HTTP API.

How do I inspect and edit existing Exchange Data conversion rules on a live information base?

You can inspect structures and edit existing conversion rules on a live information base by executing operations through the MCP-toolkit HTTP API, streamlining the management of data exchange formats in 1C:Enterprise.

Can I retrieve artifacts for EnterpriseData format expansion using this approach?

Yes, obtaining artifacts required for the expansion of the EnterpriseData format is a core feature. This allows you to gather the necessary components to extend data exchange capabilities within 1C:Enterprise.

What are the limitations of automating 1C:Enterprise conversion rules via the MCP-toolkit?

Automation is specifically targeted at 1C:Enterprise 8.5.1.1302 and requires both MCP-toolkit and 1C:Enterprise 8.3 for full functionality, meaning compatibility with other versions or lacking these dependencies may limit operations.