# Add to your Claude Code skills
git clone https://github.com/DitriXNew/EDT-MCPGuides for using mcp servers skills like EDT-MCP.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
MCP (Model Context Protocol) server plugin for 1C:EDT, enabling AI assistants (Claude, GitHub Copilot, Cursor, etc.) to interact with EDT workspace.
[!IMPORTANT] EDT version compatibility: EDT 2025.2+ is supported
https://ditrixnew.github.io/EDT-MCP/Close your EDT (!) and run:
rem Here "%VER_EDT% = 2025.2.3+30" just for example - please, set YOUR actual version !
set VER_EDT=2025.2.3+30
"\your\path\to\EDT\components\1c-edt-%VER_EDT%-x86_64\1cedt.exe" -nosplash ^
-application org.eclipse.equinox.p2.director ^
-repository https://ditrixnew.github.io/EDT-MCP/ ^
-installIU com.ditrix.edt.mcp.server.feature.feature.group ^
-profileProperties org.eclipse.update.reconcile=true

After that, EDT will automatically monitor the update site and install available updates when detected.
As well, we can also manually check via Help → About → Installation Details → Select MCP → Update
The get_form_screenshot and get_form_layout_snapshot tools need EDT to be launched with the following JVM flag:
-DnativeFormBufferedLayoutRender=true
Without it, both tools return blank output (gray PNG / empty elements list).
Why: EDT's NativeRenderService reads nativeFormBufferedLayoutRender once at class-load time. If it was unset at JVM startup, the singleton HippoLayoutService is constructed without its offscreen buffer handler, the C++ form renderer never writes captureable pixels back to Java, and the screenshot helper falls through to an SWT Control.print() of the native window — which on Windows produces a gray rectangle. Setting the flag at runtime via reflection does not help because the singleton has already been built.
How to add it (persistent, recommended):
Close EDT.
Open 1cedt.ini (next to 1cedt.exe, e.g. C:\Program Files\1C\1CE\components\1c-edt-2025.2.6+4-x86_64\1cedt.ini).
After the -vmargs line, add:
-DnativeFormBufferedLayoutRender=true
Start EDT.
How to add it (one-shot, no install changes):
"<path-to-EDT>\1cedt.exe" -data "<workspace>" -vmargs -DnativeFormBufferedLayoutRender=true
The same flag is also recommended for production EDT use — it enables the buffered native renderer that EDT itself benefits from.
If your screenshots still come back blank after adding the flag, verify with -vmargs actually appears before it in 1cedt.ini (Eclipse stops parsing -vmargs block once it hits a non--D line) and that EDT was fully restarted.
Go to Window → Preferences → MCP Server. The settings page has two tabs:
Manage which tools are available to AI assistants. Tools are organized into groups that can be enabled or disabled together. See Tool Management for details.

The MCP server status bar shows real-time execution status with interactive controls.
Status Indicator:

During Tool Execution:
MCP: update_database)When a tool is executing, you can send signals to the AI agent to interrupt the MCP call:
| Button | Description | When to Use | |--------|-------------|-------------| | Cancel Operation | Stops the MCP call and notifies agent | When you want to cancel a long-running operation | | Retry | Tells agent to retry the operation | When an EDT error occurred and you want to try again | | Continue in Background | Notifies agent the operation is long-running | When you want agent to check status periodically | | Ask Expert | Stops and asks agent to consult with you | When you need to provide guidance | | Send Custom Message... | Send a custom message to agent | For any custom instruction |
How it works:
USER SIGNAL: Your message here
Signal Type: CANCEL
Tool: update_database
Elapsed: 20s
Note: The EDT operation may still be running in background.
Use cases:
Control which MCP tools are exposed to AI assistants. This lets you reduce context window usage and restrict AI to read-only operations when needed.
All 56 tools are organized into 9 semantic groups:
| Group | Description | Tools |
|-------|-------------|-------|
| Core / Project | EDT version, project listing, configuration, validation, XML export/import | get_edt_version, list_projects, get_configuration_properties, clean_project, revalidate_objects, get_check_description, export_configuration_to_xml, import_configuration_from_xml |
| Errors & Problems | Error reporting, bookmarks, tasks | get_problem_summary, get_project_errors, get_bookmarks, get_tasks |
| Code Intelligence | Content assist, documentation, metadata browsing | get_content_assist, get_platform_documentation, get_metadata_objects, get_metadata_details, list_subsystems, get_subsystem_content, find_references |
| Tags | Tag management | get_tags, get_objects_by_tags |
| Applications & Testing | App management, database updates, testing | get_applications, list_configurations, update_database, debug_launch, run_yaxunit_tests |
| Debugging | Breakpoints, stepping, variable inspection | set_breakpoint, remove_breakpoint, list_breakpoints, wait_for_break, get_variables, step, resume, evaluate_expression, debug_yaxunit_tests, debug_status, start_profiling, get_profiling_results |
| BSL Code | Module browsing, code reading/writing, search, form inspection | read_module_source, write_module_source, get_module_structure, list_modules, search_in_code, read_method_source, get_method_call_hierarchy, go_to_definition, get_symbol_info, get_form_layout_snapshot, get_form_screenshot, validate_query |
| Refactoring | Metadata rename, delete, add attributes | rename_metadata_object, delete_metadata_object, add_metadata_attribute |
| Translation (LanguageTool) | Translation strings gene