Skip to content
Back to search

EDT-MCP

MCP for 1C:EDT

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/DitriXNew/EDT-MCP with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/DitriXNew/EDT-MCP'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ditrixnew--edt-mcp/badge.svg)](/listings/ditrixnew--edt-mcp)

HTML

<a href="/listings/ditrixnew--edt-mcp"><img src="/api/listings/ditrixnew--edt-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

From Update Site

1. In EDT: **Help → Install New Software...** 2. Add update site URL: `https://ditrixnew.github.io/EDT-MCP/` 3. Select **EDT MCP Server Feature** 4. Restart EDT

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**

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

4. 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.

Configuration

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

> [!NOTE] > **Display language.** The settings page and the tag dialogs are bilingual (Russian / English) and follow the Eclipse/EDT display language — the same `-nl` launch argument (or OS locale) that localizes the rest of EDT. Launch EDT with `-nl ru` for Russian or `-nl en` for English; any other locale falls back to English. The MCP tool surface itself (tool names, descriptions and errors) stays English regardless, as it is the AI wire contract.

General Tab

- **Server Port**: HTTP port (default: 8765) - **Check descriptions folder**: Optional override for the check descriptions that ship with the plugin. Leave it empty to use the bundled ones; point it at a folder to replace or translate individual checks (a file found there wins, per check) - **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) - **Enhance Navigator**: Controls this plugin’s contributions to the Navigator tree (groups and their filter). Turn it off to resolve conflicts with another plugin that patches the same panel

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 187 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. [![GitHub all releases](https://img.shields.io/github/downloads/DitriXNew/EDT-MCP/total)](https://github.com/DitriXNew/EDT-MCP/releases)
  2. [![Build & Unit Tests](https://github.com/DitriXNew/EDT-MCP/actions/workflows/build.yml/badge.svg)](https://github.com/DitriXNew/EDT-MCP/actions/workflows/build.yml)
  3. [![Proxy](https://github.com/DitriXNew/EDT-MCP/actions/workflows/proxy.yml/badge.svg)](https://github.com/DitriXNew/EDT-MCP/actions/workflows/proxy.yml)
  4. [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=DitriXNew_EDT-MCP&metric=alert_status)](https://sonarcloud.io/summary/new_code?id=DitriXNew_EDT-MCP)
  5. [![Bugs](https://sonarcloud.io/api/project_badges/measure?project=DitriXNew_EDT-MCP&metric=bugs)](https://sonarcloud.io/summary/new_code?id=DitriXNew_EDT-MCP)
  6. [![Code Smells](https://sonarcloud.io/api/project_badges/measure?project=DitriXNew_EDT-MCP&metric=code_smells)](https://sonarcloud.io/summary/new_code?id=DitriXNew_EDT-MCP)
  7. [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=DitriXNew_EDT-MCP&metric=coverage)](https://sonarcloud.io/summary/new_code?id=DitriXNew_EDT-MCP)
  8. [![E2E 2026.2](https://github.com/DitriXNew/EDT-MCP/actions/workflows/e2e-2026.2.yml/badge.svg)](https://github.com/DitriXNew/EDT-MCP/actions/workflows/e2e-2026.2.yml)
  9. [![Conformance 2026.2](https://github.com/DitriXNew/EDT-MCP/actions/workflows/conformance-2026.2.yml/badge.svg)](https://github.com/DitriXNew/EDT-MCP/actions/workflows/conformance-2026.2.yml)
  10. # EDT MCP Server
  11. MCP (Model Context Protocol) server plugin for 1C:EDT, enabling AI assistants (Claude, GitHub Copilot, Cursor, etc.) to interact with EDT workspace.
  12. It connects an assistant to the projects, diagnostics, code and metadata already available in your EDT workspace.
  13. Use it to inspect a configuration, make edits, validate changes and work with running applications through MCP tools.
  14. The plugin ships both local stdio and HTTP transports; choose the setup your client supports.
  15. - Browse projects, configuration properties, metadata and BSL modules.
  16. - Read diagnostics, validate queries and revalidate objects.
  17. - Search code, inspect types, follow references and call hierarchies.
  18. - Edit BSL, metadata, forms, text templates and XDTO packages.
  19. - Inspect form layouts and capture screenshots.
  20. - Launch clients normally, minimized, on another screen or isolated (Windows/Linux; hidden on macOS); update databases and manage infobase sessions.
  21. - Debug, profile and run YAXUnit tests.
  22. - Compare configurations against git revisions.
  23. - Organize the Navigator with metadata tags and groups.
  24. - Choose tool presets and reveal toolsets on demand.
  25. ## Requirements
  26. - 1C:EDT 2026.2.2 (Ruby); compatibility with earlier versions is not guaranteed
  27. - Runs on the JRE bundled with EDT (the plugin runtime floor is Java 17); no separate Java installation is needed
  28. See [compatibility details](docs/features.md) and [CI details](docs/building.md) for the supported platform and build baseline.
  29. ## Installation
  30. In EDT, choose **Help → Install New Software...**, add `https://ditrixnew.github.io/EDT-MCP/`,
  31. select **EDT MCP Server Feature**, and restart EDT.
  32. For a one-shot Windows install, close EDT and run this with your actual executable path:
  33. ```cmd
  34. "<path-to-EDT>\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
  35. ```
  36. **Form screenshots:** before enabling `get_form_screenshot`, read the [JVM flag requirements and form-designer effects](docs/installation.md#required-jvm-flag-for-form-screenshots).
  37. See [installation and preferences](docs/installation.md) for screenshots, updates and preferences, and [status-bar controls](docs/status-bar.md).
  38. ## Connecting a client
  39. Use `/mcp/plaintext` on the same HTTP port for clients that need full results in `content[0].text`.
  40. For stdio, add `"-resultMode", "plaintext"` to the launcher arguments (`"structured"` gives JSON results a short text digest).
  41. Without an override, `/mcp` and stdio use EDT's **Plain text mode** preference. Clients can share one EDT with different modes.
  42. For local stdio, use **Window > Preferences > MCP Server > General**: clear **Enable MCP over HTTP**,
  43. then click **Copy stdio .mcp.json** and merge the entry into your client's configuration.
  44. Apply to stop HTTP as well. The bundled bootstrap uses EDT's Java and explicit install/workspace paths.
  45. On Linux, stdio only attaches to an already running EDT; on Windows it starts EDT if needed.
  46. For HTTP clients, click **Start** in the EDT status bar before connecting, or enable **Auto-start** in
  47. **Window > Preferences > MCP Server > General** (off by default); see [HTTP startup](docs/installation.md#starting-http).
  48. For HTTP, the default endpoint is `http://localhost:8765/mcp`. The minimal configurations differ as follows:
  49. | Client | Configuration | Setup |
  50. |---|---|---|
  51. | stdio (including Claude Desktop) | Paste the generated entry; no Node.js needed | [Transport and startup limits](docs/stdio.md) |
  52. | VS Code / GitHub Copilot | `.vscode/mcp.json`, top-level `servers` | [VS Code](docs/clients.md#vs-code--github-copilot) |
  53. | Cursor | `.cursor/mcp.json`, top-level `mcpServers`; use `/mcp/plaintext` | [Cursor](docs/clients.md#cursor-ide) |
  54. | Claude Code | `.claude.json`, top-level `mcpServers`, `type: "http"` | [Claude Code](docs/clients.md#claude-code) |
  55. | Claude Desktop over HTTP | Use the `mcp-remote` stdio bridge (requires Node.js) | [Claude Desktop](docs/clients.md#claude-desktop) |
  56. | Cline | Top-level `mcpServers`, `type: "streamableHttp"` | [Cline](docs/clients.md#cline---extension-for-vscode) |
  57. | Antigravity | Top-level `mcpServers`, `serverUrl` instead of `url` | [Antigravity](docs/clients.md#antigravity) |
  58. VS Code / Copilot:
  59. ```json
  60. {"servers": {"EDT MCP Server": {"type": "sse", "url": "http://localhost:8765/mcp"}}}
  61. ```
  62. Cursor:
  63. ```json
  64. {"mcpServers": {"EDT MCP Server": {"url": "http://localhost:8765/mcp"}}}
  65. ```
  66. Claude Code:
  67. ```json
  68. {"mcpServers": {"EDT MCP Server": {"type": "http", "url": "http://localhost:8765/mcp"}}}
  69. ```
  70. Cline:
  71. ```json
  72. {"mcpServers": {"EDTMCPServer": {"type": "streamableHttp", "url": "http://localhost:8765/mcp"}}}
  73. ```
  74. Antigravity uses:
  75. ```json
  76. {"mcpServers": {"EDTMCPServer": {"serverUrl": "http://localhost:8765/mcp"}}}
  77. ```
  78. The [client setup guide](docs/clients.md) includes full snippets, `mcp-remote` and the
  79. [Multi-EDT proxy](docs/clients.md#multi-edt-proxy) for routing between workspaces.
  80. ## Tools
  81. The generated [full tool reference](docs/tools/README.md) lists every tool, parameter and guide, grouped by toolset.
  82. For enablement, presets and progressive disclosure,
  83. see [tool management](docs/tool-management.md). Toolsets control visibility; preferences control which tools are enabled.
  84. **Progressive disclosure** (the checkbox on the **Tools** tab, off by default) lists only the core toolset
  85. until the client reveals more with `list_toolsets` and `enable_toolset`. Turn it on only for a client that
  86. re-reads `tools/list` on `notifications/tools/list_changed` and does not load tools on demand itself.
  87. Codex and Claude Code already load MCP tools on demand, so it saves them nothing.
  88. | Toolset | Purpose | Reference |
  89. |---|---|---|
  90. | `core` | Project/module navigation, source reads and tool discovery | [Core](docs/tools/README.md#core) |
  91. | `metadata` | Discover, create, edit and refactor metadata and DCS. Check extension properties with `get_metadata_details(controlledMismatches: true)`. | [Metadata](docs/tools/README.md#metadata) |
  92. | `code` | Read/write methods, navigate symbols and inspect calls | [Code](docs/tools/README.md#code) |
  93. | `debug` | Breakpoints, stepping, variables and expressions | [Debug](docs/tools/README.md#debug) |
  94. | `testing` | Run and debug YAXUnit tests | [Testing](docs/tools/README.md#testing) |
  95. | `profiling` | Capture, compare and exchange performance profiles; capture and analyze technological logs | [Profiling](docs/tools/README.md#profiling) |
  96. | `forms` | Inspect form layouts, screenshots and templates | [Forms](docs/tools/README.md#forms) |
  97. | `tags` | Read and filter metadata tags | [Tags](docs/tools/README.md#tags) |
  98. | `translation` | Generate and synchronize translation strings | [Translation](docs/tools/README.md#translation) |
  99. | `project` | Diagnostics, applications, infobases and database updates | [Project](docs/tools/README.md#project) |
  100. | `comparison` | Three-way configuration comparison and merge rules | [Comparison](docs/tools/README.md#comparison) |
  101. | `git` | Git commands and branch/infobase bindings | [Git](docs/tools/README.md#git) |
  102. ## Security in brief
  103. HTTP binds to `127.0.0.1` unless remote access is configured; remote access requires an auth token.
  104. Treat connected clients as trusted: tools can edit files, update databases and execute debug expressions.
  105. Windowed EDT asks for human consent before gated destructive operations by default.
  106. **Explicit stdio `-headless` allows everything:** per-tool disabling, read-only presets and the consent window do not apply.
  107. Preview/confirm steps and tool preconditions still apply. See the [security and trust model](docs/security.md).
  108. ## Documentation
  109. | Article | Contents |
  110. |---|---|
  111. | [Features](docs/features.md) | Full feature list, compatibility and business-project guidance |
  112. | [Installation](docs/installation.md) | Update site, Windows command, JVM flag, HTTP startup and preferences |
  113. | [Status bar](docs/status-bar.md) | Server status, execution controls and user signals |
  114. | [Clients](docs/clients.md) | Every client's full setup, HTTP bridge and Multi-EDT proxy |
  115. | [stdio](docs/stdio.md) | Bundled bootstrap, local transport, startup modes and limits |
  116. | [Tool management](docs/tool-management.md) | Preference groups, presets, defaults and progressive disclosure |
  117. | [Tool reference](docs/tools/README.md) | Generated index linking to every per-tool page |
  118. | [Tool overviews](docs/tool-overviews.md) | Detailed usage summaries grouped by toolset |
  119. | [Output formats and API](docs/output-formats.md) | Markdown/JSON policies, contracts and HTTP endpoints |
  120. | [Security](docs/security.md) | Trust model, destructive consent, vendor support and infobase authentication |
  121. | [Infobase sessions](docs/features/infobase-sessions.md) | Inspect and clear database-update blockers |
  122. | [Three-way comparison](docs/features/comparison.md) | Compare revisions, inspect nodes and author merge rules |
  123. | [Text templates](docs/features/text-templates.md) | Read and safely update TextDocument template contents |
  124. | [XDTO packages](docs/features/xdto-packages.md) | Author package members and inspect validation results |
  125. | [Metadata tags](docs/features/metadata-tags.md) | Assign, display, filter and store tags |
  126. | [Metadata groups](docs/features/metadata-groups.md) | Organize Navigator collections into folders |
  127. | [Technological log](docs/features/tech-log.md) | Capture 1C technological logs and investigate them problems-first |
  128. | [Guided workflows](docs/guided-workflows.md) | Optional MCP prompts, resources and argument completion |
  129. | [Workmate bridge](docs/workmate-bridge.md) | Integrate with the Workmate assistant |
  130. | [E2E test cases](docs/e2e/mcp-test-cases.md) | Manual and automated tool verification scenarios |
  131. | [Building](docs/building.md) | Maven/Tycho prerequisites, scripts, options and examples |
  132. | [Autopilot](docs/autopilot.md) | Whole-task development skill, workflow and token costs |
  133. For business projects, start with the [agent skills pack](agent/README.md) and [rules pack](rules/README.md).
  134. Contributors should read [CLAUDE.md](CLAUDE.md).
  135. ## Building from source
  136. See [docs/building.md](docs/building.md) for prerequisites, script options and examples.
  137. Build from the repository root with `bash source/compile.sh` (JDK 25 and Maven 3.9+).
  138. The output is a p2 update-site archive for installation through EDT.
  139. ## License
  140. Copyright (C) 2026 DitriX
  141. Licensed under GNU AGPL v3.0

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.