EDT-Bridge MCP
A 1C:EDT plugin that gives agents the live project model over MCP: reading, refactoring, builds, infobase operations and debugging
- 29 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Changes project metadata and code through the EDT engine
- Updates infobase configurations and terminates cluster sessions
- The debugger can run arbitrary BSL against a live base
Install
- Works in
- Services
Manual install
pipx install edt-bridge-mcp
claude mcp add edt-bridge -- edt-bridge-mcp --workspace "D:\\path\\to\\edt-workspace"The wrapper starts a headless EDT and puts the plugin jar into dropins. The write token is set via EDT_BRIDGE_TOKEN.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Changes project metadata and code through the EDT engine
- Updates infobase configurations and terminates cluster sessions
- The debugger can run arbitrary BSL against a live base
This is third-party code. Review the repository files before installing.
What it does
The plugin runs inside 1C:EDT and asks the IDE what a text parser cannot see: EDT validation problems, metadata structure and types, cross-references, query validation against the project's real metadata and the platform Syntax Helper. Write tools create and delete objects, attributes, methods, forms and HTTP service routes, rename with reference updates and build .cfe, .epf and .erf files. A separate group works with infobases through EDT synchronization, ibcmd, the designer agent and rac: configuration updates, sessions, maintenance windows and .dt dumps. It can also attach a debugger and evaluate expressions in a suspended frame.
Who it is for. For 1C developers who work in 1C:EDT and want the agent to go through the IDE model instead of editing XML by hand.
Good fit when
- You need to check generated BSL and queries against EDT validation before loading into a base
- You need to create a metadata object, form or HTTP service route without hand-editing .mdo
- You want to build an extension and update a test infobase from the agent
Not a fit when
- The project lives in the Designer without EDT
- You need to touch a production base: update and debug tools are meant for test stands
Example request
Show EDT problems in the Document.ЗаказКлиента module and validate the queries in it against project metadataMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
EDT_BRIDGE_WORKSPACE- EDT workspace for the headless start, same as --workspace
EDT_BRIDGE_TOKENsecret- Token for write tools, writes are refused without it
EDT_BRIDGE_EDT_DIR- EDT install directory, the newest one is used by default
EDT_BRIDGE_PORT- Bridge port, 8770 by default
Limitations
It needs a running 1C:EDT with the project open, GUI or headless, and for .epf builds and infobase updates a local 1C:Enterprise platform of the matching version. Write tools require a token and return only a plan by default. Arbitrary BSL evaluation stays off until explicitly allowed. The server listens on localhost only.
How to disable. Run claude mcp remove edt-bridge and pipx uninstall edt-bridge-mcp. Remove the plugin jar from EDT's dropins folder and restart EDT.
FAQ
Does EDT have to be open?
The edt-bridge-mcp wrapper starts a headless EDT when no window is open and delivers the plugin jar into dropins.
Can I skip the Python wrapper?
Yes, after installing the jar manually a client can connect over HTTP to http://127.0.0.1:8770/mcp.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA 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
An MCP server for 1C:EDT with its own bridge plugin: 65 tools for metadata, BSL, debugging, forms, extensions and safe database operations
An MCP server inside 1C:EDT: the agent works with code and metadata through the IDE's semantic model, validators and debugger
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
README in short
The README explains the difference between static file parsing and the live EDT model and describes installation via pipx with Claude Code registration. Tools are split into tables: read, write, infobases with the transport used, debugging and a wrapper-only tool. It covers the EDT preference page, manual jar install, headless runs and a Maven-free build from source. Russian and English docs live on docs.keyfire.ru. Apache-2.0 license.