EDT-MCP工具

Required JVM flag for form screenshots

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):

1. Close EDT.
2. 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).
3. After the -vmargs line, add:

   -DnativeFormBufferedLayoutRender=true
   

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.

Prerequisites

• JDK 17 (e.g. Temurin / Oracle JDK)
• Apache Maven 3.9+ (no mvnw wrapper is committed — install Maven manually or via a package manager: winget, Homebrew, apt, SDKMAN, etc.)
• bash (Git Bash on Windows works) and either zip or the jar binary that ships with the JDK
• Network access to https://edt.1c.ru/, https://download.eclipse.org/ and Maven Central — Tycho downloads the EDT p2 repository and Eclipse SDK on the first run (hundreds of MB, cached afterwards under ~/.m2/)

Requirements

• 1C:EDT 2025.2 (Ruby) or later
• Java 17+

Installation

From Windows command line</strong> - "one shot" very fast install

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

Installation Result

<details> Once the installation has been completed successfully, we will see the following:

</details>

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

Getting Started

Assigning Tags to Objects:

1. Right-click on any metadata object in the Navigator
2. Select Tags from the context menu
3. Check the tags you want to assign, or select Manage Tags... to create new ones

Managing Tags:

In the Manage Tags dialog you can: - Create new tags with custom names, colors, and descriptions - Edit existing tags (name, color, description) - Delete tags - See all available tags for the project

Getting Started

Creating a Group:

1. Right-click on any metadata folder (e.g., Catalogs, Common modules) in the Navigator
2. Select New Group... from the context menu
3. Enter the group name and optional description
4. Click OK to create the group

Create Group Dialog:

Adding Objects to a Group:

1. Right-click on any metadata object in the Navigator
2. Select Add to Group...
3. Choose the target group from the list

Removing Objects from a Group:

1. Right-click on an object inside a group
2. Select Remove from Group

Building from source

The plugin is a Maven/Tycho project under mcp/. CI builds it via .github/workflows/build.yml; the same flow can be run locally with source/compile.sh.

Quick start

```bash

Examples

```bash

Configuration

Go to Window → Preferences → MCP Server. The settings page has two tabs:

General Tab

• Server Port: HTTP port (default: 8765)
• Check descriptions folder: Path to check description markdown files
• Auto-start: Start server on EDT launch
• Plain text mode (Cursor compatibility): Returns results as plain text instead of embedded resources (for AI clients that don't support MCP resources)
• Show tags in Navigator: Display tags as decorations in the Navigator tree
• Tag decoration style: How tags are displayed — all tags as suffix, first tag only, or tag count
• Server control: Start, stop, and restart the MCP server directly from preferences

Tools Tab

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.

Script options

source/compile.sh accepts every path as a flag (with matching environment-variable fallback) so it can be driven from CI or run against an out-of-tree checkout:

Self-contained invocation, no env tweaks required

bash source/compile.sh \ --java-home "/c/Program Files/Java/jdk-17" \ --maven-home /d/Soft/maven \ --skip-tests \ --version 1.27.1

Same, configured via environment

JAVA_HOME="/c/Program Files/Java/jdk-17" \ MAVEN_HOME=/d/Soft/maven \ EDT_MCP_OUTPUT_DIR=/tmp/edt-mcp-builds \ bash source/compile.sh ```

API Endpoints

Cline - extension for VSCode.

{
  "mcpServers": {
    "EDTMCPServer": {
      "type": "streamableHttp",
      "url": "http://localhost:8765/mcp"
    }
  }
}

VS Code / GitHub Copilot

Create .vscode/mcp.json:

{
  "servers": {
    "EDT MCP Server": {
      "type": "sse",
      "url": "http://localhost:8765/mcp"
    }
  }
}

<details> <summary><strong>Other AI Assistants</strong> - Cursor, Claude Code, Claude Desktop</summary>