SkillFoxx

dsh-rlm-tools-bsl plugin

A DeepSeek Harness plugin-runner: starts and stops the rlm-tools-bsl MCP server for 1C code analysis alongside DSH and registers it in the MCP manager itself

  • 3 ★ on the repository
  • Last commit
Plugin

Extended access

Why this level

  • Auto-install downloads and runs the uv installer and the rlm-tools-bsl server itself without explicit version confirmation
  • The plugin can kill a process taken over on its port even if it was not started by the plugin itself
All reasons and checks
Russian stack

mempemp/dsh-runner-rlm-tools-bslAuthor:Mempemp

Install

Manual install

dsh plugin --profile web add https://github.com/Mempemp/DSH-runner-rlm-tools-bsl/releases/download/v0.1.3/dsh-rlm-tools-bsl-0.1.3.tgz

Installs from the release without manual download; DSH needs a restart afterward.

Access and checks

How we review

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

  • Auto-install downloads and runs the uv installer and the rlm-tools-bsl server itself without explicit version confirmation
  • The plugin can kill a process taken over on its port even if it was not started by the plugin itself

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

What it does

The plugin manages the lifecycle of a third-party MCP server, rlm-tools-bsl (token-efficient 1C codebase analysis, a separate Dach-Coin project), inside the DeepSeek Harness environment: on DSH startup it launches the server on local port 9330 and waits for readiness via the MCP handshake, and on DSH shutdown it kills the whole process tree. A settings tab shows status, version, pid, a restart button and a ready-made JSON snippet for the MCP manager. If rlm-tools-bsl is not installed, the plugin installs it itself via uv, and if a server is already answering on the port from a previous session, it takes over that one instead of starting a second. The plugin registers the server in DSH's MCP manager storage itself, updates it when the port changes, and leaves unrelated entries alone. The /rlm/state, /rlm/log, /rlm/start, /rlm/stop, /rlm/restart HTTP routes give other DSH plugins and agents control access.

Who it is for. For DeepSeek Harness (DSH) users who want a 1C code analysis MCP server without manually starting and stopping the process every session.

Good fit when

  • You work in DeepSeek Harness and want the rlm-tools-bsl MCP server for 1C code analysis without manual administration
  • You want the server to automatically stop when DSH closes and not hold the port between sessions
  • You want automatic installation of rlm-tools-bsl and its uv dependency without separate steps

Not a fit when

  • You use an agent other than DeepSeek Harness: the plugin only works within its profile composition
  • You need the actual 1C code analysis, not process management: the tools themselves come from the separate rlm-tools-bsl project

Example request

Start the rlm tools and index the current 1C project for code analysis

Limitations

Only works inside DeepSeek Harness version 0.1.2-rc.1 or newer and requires Node.js 20+. The plugin itself does not analyze code; it only manages the process of the separate rlm-tools-bsl MCP server, which must be installed separately (or left to auto-install). The server's data (config, log, cache) is written outside the working folder into the user profile by default, which can conflict with DSH's file sandbox.

How to disable. Remove the plugin from the DSH profile composition and, if needed, delete the rlm entry from the MCP manager storage by hand; the plugin does not remove it itself.

FAQ

Do I need to install rlm-tools-bsl separately?

No, if it is missing, the plugin installs it itself along with uv; auto-install can be turned off with autoInstall: false.

Is the server reachable from outside the machine?

No, rlm-tools-bsl only listens on 127.0.0.1, and the plugin's host routes are locally accessible without a session token, so DSH should not be exposed to the network without its own token.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

An MCP server that hands bulk file work to a local DeepSeek Harness agent so file contents never enter Claude's context

MCP serverBroad access2
Russian stack

An MCP server for analyzing large 1C codebases with less context: the agent runs scripts server-side and gets only a compact result

MCP serverExtended access232
Russian stack

A Docker gateway with 40-plus MCP tools for 1C, one address, a settings dashboard and a set of 1C skills for Claude Code

MCP serverBroad access
Russian stack

MCP bridge to BSL Language Server: navigation, diagnostics and refactoring of 1C and OneScript code for agents

MCP serverExtended access71
Russian stack

A Dockerized MCP server that keeps BSL Language Server running and gives the agent code navigation, diagnostics and refactoring for 1C instead of grep search

MCP serverExtended access1
Russian stack

An MCP server that exposes the cloud 1C:Napparnik (1C.ai) assistant and a local BSL Language Server to agents in Cursor and other IDEs

MCP serverExtended access22

README in short

The README details the features (shared lifecycle with DSH, a settings tab, auto-install, taking over an already-running server, auto-registration in the MCP manager, /rlm/* routes), three ways to connect the server in DSH, and three ways to install the plugin itself. Separate sections cover data locations and the file sandbox, advanced parameters via the plugin config line, common issues in a symptom-fix table, and the security model: the server is localhost-only, and the plugin never kills unrelated processes. The plugin has no external dependencies, only node and React from the DSH runtime.

README badge

Report a problem