AI-EDT plugin
An MCP server inside 1C:EDT: the agent works with code and metadata through the IDE's semantic model, validators and debugger
- 23 ★ on the repository
- Last commit
- AGPL-3.0
Broad access
Why this level
- Changes configuration metadata and code and updates the connected infobase
- Controls the debugger and reads infobase data
Install
- Works in
- Services
Manual install
Установи мне плагин AI-EDT в 1C:EDT. Рецепт: https://github.com/Desko77/ai-edt/blob/main/docs/agent-install.md Прочитай его целиком и следуй ему. Ставь с update site https://desko77.github.io/ai-edt/ через Equinox p2 director (1cedtc.exe из каталога установки EDT). Мастер "Установить новое ПО" не используй. Это первая установка, поэтому -uninstallIU не передавай.
Shortened prompt from the README; the full one is in the install section. Needs a shell-enabled agent on the EDT machine.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Changes configuration metadata and code and updates the connected infobase
- Controls the debugger and reads infobase data
This is third-party code. Review the repository files before installing.
What it does
The plugin runs inside a live 1C:EDT and gives the agent the IDE's own services instead of a folder of XML and BSL files. The agent searches code, resolves references and builds call hierarchies, creates and changes metadata objects and managed forms, validates queries against the actual configuration and immediately runs results through EDT validators. It also offers debugging with breakpoints and expression evaluation, work with DCS, extensions and the infobase, YAxUnit tests and Vanessa Automation scenarios. A binary .cf can become a project in one call. The repository includes an ai-edt skill with the tool catalog.
Who it is for. For 1C developers on EDT who want an agent that understands the configuration model and verifies its own changes.
Good fit when
- You need to see which forms, roles and subsystems depend on an object
- You want the agent to create metadata without hand-editing XML
- You need to inspect a paused debug session
Not a fit when
- Your EDT version is older than 2026.1
- Sources are for 1C 7.7
Example request
Which forms and roles use the Номенклатура catalog? Check whether my query compiles against this configurationLimitations
The current version runs only on 1C:EDT 2026.1 and 2026.2 and needs JDK 17 or 25 respectively. Build scripts and install commands in the README target Windows and PowerShell. Some features need YAxUnit, Vanessa Automation or the Attach configuration. AGPL-3.0 licensed.
How to disable. Uninstall the plugin from EDT via p2 director or Installation Details and remove the server from your MCP client config.
FAQ
How is this different from an agent reading exported files?
The agent relies on EDT indexes and validators, so it sees references, types and errors as the IDE does and verifies changes before loading them into the infobase.
Can it be installed without manual steps?
The author provides a prompt for a shell-enabled agent: it closes EDT, installs the plugin via p2 director and restarts the IDE.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA 1C:EDT plugin that gives agents the live project model over MCP: reading, refactoring, builds, infobase operations and debugging
A 1C:EDT plugin that gives agents projects, errors, BSL analysis, form screenshots, metadata refactoring and infobase launch over MCP
EDT MCP
EDT_MCP
A 1C:EDT plugin that runs an MCP server inside the IDE: projects, modules, metadata, forms, DCS, debugging and infobase deploy
1C:EDT companion MCP with 46 tools
edt-companion-mcp
An OSGi plugin runs an HTTP MCP inside 1C:EDT, giving an agent the live model: metadata, BSL with unsaved edits, debugging and headless infobase updates
CodePilot1C for 1C:EDT
CodePilot1C (EDT plugin)
A 1C:EDT plugin with a built-in MCP Host: an agent gets typing, metadata and the EDT model directly, not by parsing XML files
An MCP server for 1C:EDT with its own bridge plugin: 65 tools for metadata, BSL, debugging, forms, extensions and safe database operations
README in short
The Russian and English README explains which questions a text-only agent cannot answer without the IDE model and lists scenarios: code exploration, metadata, debugging, diagnostics, DCS and tests. The quick start covers EDT and JDK requirements, a Maven build and installation from the update site, including a ready prompt for an agent. Extra integrations and architecture are described separately. AGPL-3.0 licensed.
README badge
Original SKILL.md
--- name: ai-edt description: "1C:Enterprise development through the AI-EDT MCP server - BSL analysis and editing, metadata and managed forms, query validation, project diagnostics, debugging, infobase updates and unit tests. Use when the project is a 1C:EDT workspace: BSL modules, .mdo metadata, 1C queries, managed forms. Also use when all you have is a delivered .cf or .cfe with no project yet - it becomes one. Not for 1C 7.7 sources." --- # AI-EDT AI-EDT exposes a running 1C:EDT instance over MCP. Search, navigation and analysis run against EDT's semantic model, not against file text, so references, definitions and call hierarchies are resolved the way the IDE resolves them. Plain text and regular-expression search over the module catalogue is available too, as one operation among others. The tool catalogue lives in `references/`. Read the file you need for the task at hand rather than all of them. ## When to use it - Reading and editing BSL: modules, methods, references, call graphs, refactoring. - Metadata: inspect, create, change, delete, rename with cascade. - Managed forms: structure, a screenshot of the WYSIWYG editor, editing without hand-written XML. - 1C queries: syntax and semantic validation before anything runs. - Project problems, infobase updates, YAxUnit tests, debugging and profiling.