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
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
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
Install
Manual install
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.
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 applyingLimitations
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.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- 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
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.
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.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything