1C:EDT MCP Toolkit
An MCP server for 1C:EDT with its own bridge plugin: 65 tools for metadata, BSL, debugging, forms, extensions and safe database operations
- 2 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Metadata and extension change operations need a plan and confirmation, but are still executed by the agent
- Optional Designer access uses the database admin password from environment variables
Install
- Works in
- Services
Manual install
Set-Location .\mcp-wrapper
.\build.ps1Builds the MCP wrapper after installing edt-bridge and selecting a project in EDT.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Metadata and extension change operations need a plan and confirmation, but are still executed by the agent
- Optional Designer access uses the database admin password from environment variables
This is third-party code. Review the repository files before installing.
What it does
The project has two parts: mcp-wrapper, a Go STDIO MCP server that exposes protected tools and locks access to one database or a family of EDT projects, and edt-bridge, a Java loopback plugin for EDT that serves metadata, BSL, applications, debugging, forms, MXL and extensions data. Version 0.12 fully replaced the third-party DitriX EDT-MCP integration with its own bridge covering all 65 verified tools, with no AGPL code in the repo. It offers root project selection from the EDT menu, extension work (creating, borrowing metadata, editing forms and MXL through prepared MCP plans), diagnostics, Vanessa Automation and technology log integration, code review via the BSL Language Server, and safe metadata editing through a facade requiring a prepared and confirmed plan.
Who it is for. For 1C developers on EDT who use Codex or another MCP client and want safe, scoped agent access to the project and database rather than unrestricted access to the whole infobase.
Good fit when
- You need agent integration with EDT: metadata, BSL, forms, extensions, debugging in one MCP server
- You need to restrict the agent to one base configuration and its extensions, not an arbitrary path
- You need safe metadata-change operations with a prepared plan and confirmation
Not a fit when
- You develop in the classic Configurator rather than 1C:EDT
- You cannot build edt-bridge for your EDT version: only 2025.2 and 2026.1 are verified
Example request
Show the structure of the Counterparties catalog and prepare a plan to change its item formMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
ONEC_DB_USER- The 1C infobase user for operations via Designer.
ONEC_DB_PASSWORDsecret- The infobase user's password.
Limitations
Requires building your own edt-bridge for a specific EDT version (2025.2 and 2026.1 verified, platform 8.3.27, Go 1.25, Java 17); there is no ready binary. The setup targets the Codex client, and configuration for other MCP clients is not explicitly documented. Metadata changes need a separately prepared and confirmed plan rather than a direct one-command edit.
How to disable. Remove the onec_edt entry from Codex's MCP server configuration and stop edt-bridge in EDT.
FAQ
Do I need DitriX EDT-MCP?
No, starting with version 0.12 the built-in edt-bridge covers all 65 compatibility tools, so installing DitriX EDT-MCP is not required.
Can the model pick an arbitrary database itself?
No, the root project is chosen only by the user from the EDT menu, and an explicit projectName is only accepted for that configuration or its extension.
How is the 1C:EDT MCP Toolkit different from other 1C:EDT MCP servers?
A two-part project: mcp-wrapper, a Go STDIO MCP server with protected tools that pins access to one database or a family of EDT projects, and edt-bridge, a loopback plugin. It gives 65 tools for metadata, BSL, debugging, forms, extensions and safe database operations.
Do I need DitriX EDT-MCP and can the model pick an arbitrary database?
See the README for compatibility with DitriX EDT-MCP. The model cannot pick an arbitrary database: access is pinned to one database or family of EDT projects set in the configuration. Build with .\build.ps1 in the mcp-wrapper folder. It works with Codex. Risk is medium.
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
A local Codex plugin that installs EDT-MCP into 1C:EDT on Windows and sets up a ready MCP connection on localhost
An MCP server inside 1C:EDT: the agent works with code and metadata through the IDE's semantic model, validators and debugger
README in short
The README is structured as a version history from 0.6 to 0.12, listing features added at each step: from a basic development and export layer to Vanessa Automation, safe edit_metadata, a debugger, code review, and finally a full replacement of DitriX. It describes the architecture: a STDIO client talks to mcp-wrapper, which talks to a local bridge using a token from bridge.json, which talks to the EDT project model and optionally the Designer. It lists security measures: project selection only by the user, a loopback interface, a one-time token, passwords only from environment variables, and confirmation for metadata-change plans. Licenses differ by part: MIT for the wrapper, EPL-2.0 for the bridge.