edt-bridge

Adoption verdict: edt-bridge is worth testing as a technical candidate for connecting 1C:EDT to MCP, but the available evidence is not sufficient to treat it as a mature, production-ready development platform. The only evidence is a GitHub repository search listing showing 26 stars, 2 forks, and 2 comments. Those figures demonstrate some attention, not usability, reliability, or production adoption.

In practical terms, the repository summary describes an Eclipse/OSGi plugin that exposes a local 1C:EDT semantic model through MCP and supports reading, writing, refactoring, and debugging. A more accurate analogy is a local bridge between 1C:EDT and AI agents or developer tools. It should not be confused with a standalone AI coding assistant, a foundation model, a generic hosted MCP service, or a complete 1C development environment.

The likely entry barrier is having a working 1C:EDT and Eclipse/OSGi plugin setup, plus an agent or developer tool that can connect through MCP. The available listing does not document versions, installation steps, permissions, or the limits of debugging support. No official pricing or API fee information is provided.