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
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
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
Manual install
Set-Location .\mcp-wrapper
.\build.ps1Builds the MCP wrapper after installing edt-bridge and selecting a project in EDT.
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 formLimitations
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.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| ONEC_DB_USER | The 1C infobase user for operations via Designer. |
| ONEC_DB_PASSWORD secret | The infobase user's password. |
Security check
- 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
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.
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.
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