SkillFoxx

1C:EDT MCP worktree bootstrap

onec-worktree-mcp

A Node.js script that starts EDT-MCP and the BSL Language Server for every new git worktree and writes readiness markers

  • 0 ★ on the repository
  • Last commit
  • MIT
Workflow

Extended access

Why this level

  • A Node script imports the project into the EDT workspace via 1cedtcli and starts EDT and BSL Language Server
  • Writes port and readiness marker files and calls no external services
All reasons and checks
Russian stack

pravets/onec-worktree-mcpAuthor:pravets

Install

Manual install

node tools/init-mcp.mjs init --import

The command is registered as a worktree setup command in OpenChamber: Settings, Project, Worktree setup commands.

Access and checks

How we review

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

  • A Node script imports the project into the EDT workspace via 1cedtcli and starts EDT and BSL Language Server
  • Writes port and readiness marker files and calls no external services

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

What it does

The package moves EDT-MCP and BSL Language Server initialization into other repositories. When a new git worktree is created, tools/init-mcp.mjs picks free ports, imports the project into the EDT workspace via 1cedtcli in the background, starts EDT in GUI mode and the BSL Language Server in MCP mode, then writes readiness marker files. The MCP config reads ports from build/*-mcp-port files through {file:...} placeholders, and the command is wired up as an OpenChamber worktree setup command.

Who it is for. For 1C developers who work in OpenChamber with several git worktrees and want EDT-MCP and BSL-MCP to start without manual steps.

Good fit when

  • You work in OpenChamber with parallel worktrees and want the same MCP setup in each
  • You are tired of starting EDT-MCP and the BSL Language Server by hand for every new worktree
  • You want to carry an already tuned MCP bootstrap into another 1C repository

Not a fit when

  • You do not use OpenChamber or git worktrees
  • You have no 1C:EDT install or bsl-language-server in PATH

Example request

Set up EDT-MCP and BSL-MCP to start automatically for new worktrees in this 1C project

Limitations

It needs Node.js 22 or newer (uses fs.globSync), a 1C:EDT install with the path set in edt.home config, and bsl-language-server available on PATH. The script is built specifically for the OpenChamber workflow and is not an MCP server itself, only a bootstrap for two existing ones. The project is very small, has one author, no stars and no releases.

How to disable. Remove tools/init-mcp.mjs from the repository and the related entry from opencode.json, and delete the command from Worktree setup commands in OpenChamber settings.

FAQ

Do I have to wait for the servers to start?

No, if Wait for setup commands is off: the command returns in seconds while EDT and the BSL Language Server start in the background.

Where do the ports come from?

The script picks free ports itself and writes them to build/*-mcp-port files, which are then substituted into opencode.json via the {file:...} placeholder.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
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 for 1C:EDT with its own bridge plugin: 65 tools for metadata, BSL, debugging, forms, extensions and safe database operations

MCP serverExtended access2

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

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

1C AI development environment

1C AI Development Environment

Russian stack

1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C

MCP serverBroad access18

README in short

The README describes moving EDT and BSL MCP initialization into other repositories by copying the tools folder and two config files. It lists requirements (Node.js 22+, 1C:EDT, bsl-language-server on PATH), a four-step install, and setup as an OpenChamber worktree setup command with the --import flag for the first import run through 1cedtcli.

README badge

Report a problem