SkillFoxx

EDT Debug Tracer MCP

An Eclipse plugin for 1C:EDT that records a step-by-step debug trace of BSL code and exposes it to an agent over an MCP-compatible JSON-RPC endpoint

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • Controls a live debug session: can step, resume and suspend execution threads
  • The plugin's HTTP server listens on a local port with no authorization by default
All reasons and checks
Russian stack

lytkinam/edt-debug-tracerAuthor:lytkinam

Install

Manual install

git clone https://github.com/lytkinam/edt-debug-tracer
cd edt-debug-tracer
javac --release 17 -d plugin/bin -cp "$CP" plugin/src/plugin17/test/*.java
jar cfm plugin17-test_1.0.0.jar plugin/META-INF/MANIFEST.MF -C plugin/bin .

Building needs the jar path from an installed Eclipse ($CP from the README); the result is copied into the Eclipse or EDT plugins folder.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Controls a live debug session: can step, resume and suspend execution threads
  • The plugin's HTTP server listens on a local port with no authorization by default

This is third-party code. Review the repository files before installing.

What it does

The plugin intercepts Eclipse Debug API events during a 1C:EDT debug session and, at every step, records the procedure, line, module, thread, call stack and variables into SQLite and JSON. The same HTTP port serves a JSON-RPC 2.0 endpoint at /mcp with eight tools: debug status, step, resume, suspend, wait for break, stack frame variables, and the full call stack. It also manages breakpoints, which can be placed automatically from an already recorded trace. There is a ready integration pattern for Vanessa: the trace records around each BDD step, and the result can be attached to an Allure report.

Who it is for. For 1C developers and testers who debug configurations in EDT and want to give an agent programmatic access to the debug session and execution trace.

Good fit when

  • You want an agent to drive step-by-step BSL debugging: step, resume, suspend
  • You need an execution trace with variables and call stack to analyze a bug
  • You want to tie the debug trace to Vanessa BDD tests and attach it to an Allure report

Not a fit when

  • No EDT debug session is running: without an active debug target the tracer gets no events
  • You need a ready installer rather than building from source for a specific Eclipse version

Example request

Start debugging, wait for the first breakpoint and show me the call stack and variables of the current frame

MCP

Transport
http
Authentication
not required

Limitations

The plugin only works while EDT is attached to a debug session as the debug target; without one the trace buffer stays empty. It is built from source manually for a specific Eclipse or EDT build, with no ready installer. It is a single-author project, and part of the documentation reads as a development log with an AI agent rather than a reference for an outside user.

How to disable. Remove the plugin jar from the Eclipse or EDT plugins folder, delete its registration line from bundles.info and restart Eclipse.

FAQ

Is this an official 1C tool?

No, it is a third-party Eclipse plugin for 1C:EDT by a single author, unrelated to the 1C vendor.

Can I get a trace without an active debug session?

No, the plugin intercepts Eclipse debugger SUSPEND events, so without a running debug target the trace buffer stays empty.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

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

MCP serverBroad access9

EDT MCP

EDT_MCP

Russian stack

A 1C:EDT plugin that runs an MCP server inside the IDE: projects, modules, metadata, forms, DCS, debugging and infobase deploy

PluginBroad access17
Russian stack

A 1C:EDT plugin that gives agents the live project model over MCP: reading, refactoring, builds, infobase operations and debugging

MCP serverBroad access30
Russian stack

A 1C:EDT plugin that gives agents projects, errors, BSL analysis, form screenshots, metadata refactoring and infobase launch over MCP

MCP serverBroad access333
Russian stack

An MCP server inside 1C:EDT: the agent works with code and metadata through the IDE's semantic model, validators and debugger

PluginBroad access29

CodePilot1C for 1C:EDT

CodePilot1C (EDT plugin)

Editors’ pick

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

PluginBroad access159

README in short

The README lists the plugin's features: intercepting debug events, 12 fields per trace step, dual SQLite and JSON storage, 17 HTTP endpoints, automatic breakpoint placement from the trace, around 130 config parameters, and trace post-processing with a Python script. It gives Eclipse build commands, a sample tracer.properties config, a grouped endpoint table, the step record format, a target usage scenario, an architecture diagram and a version history from v1.0 to v9.2. MIT license.

README badge

Report a problem