edt-bridge-mcp 0.4.1

stdio MCP front-end for the edt-bridge 1C:EDT plugin: proxies to a running EDT, or auto-starts a headless one

edt-bridge-mcp

English · Русский

stdio MCP front-end for the edt-bridge 1C:EDT plugin.

The Java plugin serves MCP as plain JSON-RPC over HTTP on 127.0.0.1:8770 – which means an MCP client configured with that URL loses the server whenever EDT is not running. This wrapper is what the client talks to instead:

• EDT open (GUI or headless) → every request is forwarded to the live bridge;
• EDT closed → it auto-starts a headless EDT (1cedtcli with a keepalive pipe, the same recipe as scripts/run-headless.ps1) and forwards once the model is ready;
• plugin jar missing → it delivers the jar itself from the latest GitHub release (checksum-verified) into EDT's dropins/ before starting – a bare pipx install edt-bridge-mcp is enough to get a working bridge;
• a client session never hangs on startup: while the backend is starting, tools/list returns an empty list and a notifications/tools/list_changed follows when ready.

Install

pipx install edt-bridge-mcp        # or: pipx install ./python  from a checkout

Register in an MCP client

claude mcp add edt-bridge -- edt-bridge-mcp --workspace "D:\\path\\to\\edt-workspace"

Self-update

edt-bridge-mcp self-update             # refresh the plugin jar (GitHub Releases) + the wrapper (PyPI)
edt-bridge-mcp self-update --jar-only  # only the jar
edt-bridge-mcp self-update --pip-only  # only the wrapper

A running EDT (GUI or headless) keeps the old jar loaded until it restarts; the wrapper restarts its own headless instance on the next auto-start.

Configuration

CLI flags override the environment.

Env	Flag	Meaning
EDT_BRIDGE_PORT	--port	bridge port (default 8770)
EDT_BRIDGE_TOKEN	–	write-tools token, forwarded as Authorization: Bearer and injected into the headless JVM
EDT_BRIDGE_WORKSPACE	--workspace	EDT workspace path – required for the headless auto-start
EDT_BRIDGE_EDT_DIR	--edt-dir	EDT install dir (.../1cedt); newest install auto-detected when omitted
EDT_BRIDGE_START_TIMEOUT	--start-timeout	seconds to wait for a starting backend (default 360)
EDT_BRIDGE_AUTOSTART	--no-autostart	set 0/pass the flag for proxy-only mode

Safety

• If a GUI EDT is running but the bridge port is dead (plugin missing there), the wrapper refuses to start a headless instance – the GUI holds the workspace lock. It still delivers the jar into dropins/ when missing, so restarting that EDT activates the bridge.
• If a headless 1cedtcli is already starting, the wrapper waits for it instead of spawning a second one.