EDT-MCP is a plugin for 1C:EDT (the Eclipse-based development environment for the 1C:Enterprise platform) that runs a Model Context Protocol server inside the IDE, so an AI assistant can read and change a 1C configuration through the workspace that EDT already has open. It speaks MCP 2025-11-25 over Streamable HTTP with SSE, and connects to VS Code with GitHub Copilot, Cursor, Claude Code, Claude Desktop (through a stdio bridge), Cline, and Antigravity. One build supports EDT 2026.1 and 2026.2.
The server exposes 97 tools in 11 groups. Read tools list projects, metadata objects and subsystems, errors and markers, module structure, call hierarchies, references, content assist, and platform documentation. Write tools read and write BSL module source, create, modify, rename, and delete metadata objects and their members with cascading updates across code, forms, and metadata, author XDTO packages and data composition schemas, edit command interfaces, and run translation. Application tools update the database, launch and terminate 1C clients, inspect infobase sessions, run and debug YAxUnit tests, set breakpoints, step, evaluate expressions, and profile. Form tools return PNG screenshots and YAML layout snapshots from the form editor, and a three-way configuration comparison against two git revisions is read node by node.
Tool exposure is configurable. Groups and individual tools can be enabled or disabled from the preferences, presets switch between All Tools, Analysis Only, Code Review, and Development, and an optional progressive-disclosure mode exposes only a core toolset and reveals the rest on demand. Every tool carries standard MCP annotations (read-only, idempotent, destructive, open-world), returns Markdown by default with JSON reserved for round-trip identifiers and machine-structured positions, and reports failures through one structured error contract. Destructive operations preview first and act only with explicit confirmation, and writes to objects locked by vendor support are refused.
A status bar shows the running tool and elapsed time and lets you interrupt a call with a signal to the agent (cancel, retry, continue in background, ask expert, or a custom message). When 1C:Workmate runs in the same JVM, an in-process bridge works both ways: an ask_workmate tool starts Workmate's conversation loop as a pollable background job, and an OSGi service lets Workmate's JShell list and call EDT-MCP tools. A separate proxy routes a single endpoint to several running EDT instances by project name. The server binds to loopback by default, requires a bearer token for remote access, validates MCP sessions, refuses non-loopback browser origins, and caps request bodies.
The repository also ships a Claude Code project skill, edt-mcp-autopilot, that takes an issue end to end through a multi-agent spec-driven pipeline of researchers, critics, an architect, parallel developers, and a reviewer loop, at a reported cost of several million tokens per task.
Features
- MCP 2025-11-25 server in EDT: Streamable HTTP transport with SSE, running inside the IDE against the open workspace
- 97 tools in 11 groups: project, errors, code intelligence, tags, applications and testing, debugging, BSL code, refactoring, translation, comparison, and git
- BSL code analysis: browse modules, inspect structure, read and write methods, search code, follow call hierarchies and references, and get content assist and platform documentation at any position
- Metadata refactoring: create, modify, rename, delete, and adopt metadata objects and their members with cascading updates across BSL code, forms, and metadata
- Debugging and profiling: breakpoints, stepping, variables, expression evaluation, YAxUnit test runs and debugging, and profiling results
- Form inspection: PNG screenshots and YAML layout snapshots from the form editor
- Application management: update the database, launch in debug mode, terminate EDT-launched clients, and inspect or terminate infobase sessions before an update
- Three-way comparison: compare a configuration against two git revisions and read the result node by node, with merging left to a human in EDT
- Tool management: enable or disable groups and tools, presets (All Tools, Analysis Only, Code Review, Development), per-tool parameter defaults, and optional progressive disclosure
- Interruptible operations: a status bar sends cancel, retry, continue-in-background, ask-expert, or custom signals to the agent mid-call
- Workmate bridge: an ask_workmate tool runs 1C:Workmate as a pollable background job, and an OSGi service lets Workmate call EDT-MCP tools in-process
- Local trust model: loopback bind by default, bearer token required for remote access, session validation, loopback-only browser origins, bounded request bodies, and consent for destructive operations
