EDT MCP plugin
EDT_MCP
A 1C:EDT plugin that runs an MCP server inside the IDE: projects, modules, metadata, forms, DCS, debugging and infobase deploy
- 17 ★ on the repository
- Last commit
Broad access
Why this level
- Can change configuration metadata and code and update the infobase
- Reads infobase data including the event log
Install
- Works in
- Services
Manual install
claude mcp add edt-mcp \
--transport sse \
--url http://127.0.0.1:3001/mcp/sse \
--header "Authorization: Bearer <token>"The port may differ if 3001 is taken.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can change configuration metadata and code and update the infobase
- Reads infobase data including the event log
This is third-party code. Review the repository files before installing.
What it does
The plugin installs into 1C:EDT from an update site and starts a local HTTP+SSE server protected by a Bearer token. Through it an agent opens projects and BSL modules, edits metadata and forms, builds data composition schemas, runs quality checks, reads the event log, launches the 1C client and debug sessions, updates the infobase and creates xUnitFor1C tests. A personal data masking layer runs before infobase data is sent to the client. The server is controlled from the Window menu and the EDT status bar.
Who it is for. For 1C developers working in EDT who want to give an agent project access through the IDE itself.
Good fit when
- You want the agent to understand configuration metadata, not just module text
- You need the agent to update the infobase and start the client or debugger
- You want the agent to build a DCS report or xUnitFor1C tests
Not a fit when
- Development happens in Designer without EDT
- The agent must not write to a production infobase
Example request
Which projects are open in EDT? Find the ПриходнаяНакладная document in the configuration and list its attributesLimitations
Requires 1C:EDT; the main tested branch is 2026.x, and 2023.x to 2025.x are expected to work but the author has not verified them live. The server listens on a local port and needs a token generated in plugin settings. The client must support SSE transport.
How to disable. Stop the server via Window, EDT MCP, Stop, or uninstall the plugin in Help, About, Installation Details. Remove the edt-mcp entry from your client.
FAQ
Do I need to build from source?
No, it installs from a ready update site or a ZIP from releases. JDK and Maven are only for development.
Can several EDT instances run at once?
Yes, each takes the first free port in the configured range, 3001 to 3006 by default.
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
A 1C:EDT plugin that gives agents the live project model over MCP: reading, refactoring, builds, infobase operations and debugging
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
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
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 Russian README walks from installing EDT to the first tool call: a supported versions matrix, installing from the update site, port and token setup, and checks with curl and MCP Inspector. It gives the Claude Code command and a Claude Desktop config. The full tool catalog is in docs/tools.md, recipes and known bugs in the edt-mcp skill, and report patterns in the edt-skd skill. The plugin is Apache 2.0.