SkillFoxx

EDT Bridge: Unica-style tools on top of EDT-MCP

edt-bridge

An MCP server with 18 tools that ports Unica-style functionality to 1C:EDT-format projects as a layer over EDT-MCP, with atomic change application

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • The mutation-applying tools change project forms, templates and extensions
  • Deleting objects is guarded by a separate confirmation token, but the operation is irreversible without a backup
All reasons and checks
Russian stack

banibaushev/edt-bridgeAuthor:BaniBaushev

Install

Manual install

Text for your agent

Install and configure EDT-MCP by DitriXNew, then install edt-bridge from source via pyproject.toml, connect it as a stdio MCP server, and call edtb_plan_mutations before edtb_apply_mutations for any batch of changes.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The mutation-applying tools change project forms, templates and extensions
  • Deleting objects is guarded by a separate confirmation token, but the operation is irreversible without a backup

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

What it does

The project implements for the 1C:EDT format what Unica does for the configurator's XML format: compiling and parsing forms, MXL templates, roles, subsystem command interfaces and configuration panels, scaffolding external processings and reports against the standard subsystems library, and borrowing methods into extensions. The key edtb_plan_mutations tool builds a dry-run plan for a batch of changes with a planHash and a confirmation token for deletions, and edtb_apply_mutations atomically applies the batch: backing up, applying, rolling back on error, and resyncing the result back into EDT. It is not a Unica fork: the codebase is new, and Unica's license and runtime are not used.

Who it is for. For 1C developers working in EDT-format projects who want the same form, template and extension operations that Unica provides for the configurator.

Good fit when

  • The project is already in 1C:EDT format and needs Unica-level operations
  • You need to apply a batch of changes atomically with rollback on error
  • You need to scaffold a standard-subsystems-based external processing or report without hand-typing the template

Not a fit when

  • The project is in DESIGNER configurator format, not EDT: use Unica itself
  • EDT-MCP, which the bridge sits on top of, is not installed and configured

Example request

Use edt-bridge to plan changing a list form to the dialog preset and show the planHash before applying

MCP

Transport
stdio
Authentication
not required

Limitations

The bridge works only on top of an already configured EDT-MCP from another author and is useless on its own. Some tools, such as edtb_designer_check, wrap external utilities like ring and 1cedtcli that need to be present on the system separately. The project is small, has no license listed in the repository metadata, no stars and no releases.

How to disable. Remove the edt-bridge entry from your MCP client config.

FAQ

Is this a Unica fork?

No, the README says explicitly the codebase is new and Unica's license and runtime are not used, only similar functionality for the EDT format is implemented.

What happens if applying a batch fails?

edtb_apply_mutations backs up before changes and rolls back on failure, then resyncs the state back into EDT.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

An MCP server for 1C:EDT with its own bridge plugin: 65 tools for metadata, BSL, debugging, forms, extensions and safe database operations

MCP serverExtended access2
Russian stack

A 1C:EDT plugin that gives agents the live project model over MCP: reading, refactoring, builds, infobase operations and debugging

MCP serverBroad access30

EDT MCP

EDT_MCP

Russian stack

A 1C:EDT plugin that runs an MCP server inside the IDE: projects, modules, metadata, forms, DCS, debugging and infobase deploy

PluginBroad access19
Russian stack

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

MCP serverBroad access9
Russian stack

A 1C:EDT plugin that gives agents projects, errors, BSL analysis, form screenshots, metadata refactoring and infobase launch over MCP

MCP serverBroad access333
Russian stack

An MCP server inside 1C:EDT: the agent works with code and metadata through the IDE's semantic model, validators and debugger

PluginBroad access29

README in short

The README gives a table of 18 tools with their Unica equivalents: planning and applying mutations, compiling and parsing forms, decompiling and compiling MXL templates, scaffolding EPF against the standard subsystems library, adding help, borrowing methods into extensions, editing the command interface and configuration panels, and wrapping designer check. It stresses this is not a fork but a new implementation on top of EDT-MCP with careful file operations and resync back into EDT.

README badge

Report a problem