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
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Runs local EDT and BSL Language Server processes on the developer's machine
- Does not call external services or write to production infobases
Install
Manual install
node tools/init-mcp.mjs init --importThe command is registered as a worktree setup command in OpenChamber: Settings, Project, Worktree setup commands.
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 projectLimitations
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.
Security check
- Runs local EDT and BSL Language Server processes on the developer's machine
- Does not call external services or write to production infobases
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.
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.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
Agent Skills for Google products
Agent Skills for Google products and technologies
Official Google skill collection for working with Google Cloud, BigQuery, GKE, ads and analytics from an agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring