1c-ninja-kit workflow
A toolkit for 1C development with an agent: skills, rules, roles, an MCP server for the NinjaLive extension and an OpenCode installer for Windows
- 1 ★ on the repository
- Last commit
Broad access
Why this level
- The installer installs dependencies and copies agents, commands and scripts into the global OpenCode config
- Live mode runs code and queries in a live infobase and reads the event log under an infobase user's password
Install
- Works in
- Services
Manual install
powershell -NoProfile -ExecutionPolicy Bypass -File .\install\kit.ps1 depsAfter cloning the repository. Then `kit.ps1 doctor` and `kit.ps1 apply`. The 1C platform is installed separately.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The installer installs dependencies and copies agents, commands and scripts into the global OpenCode config
- Live mode runs code and queries in a live infobase and reads the event log under an infobase user's password
This is third-party code. Review the repository files before installing.
What it does
The repository assembles a working environment for an agent that writes code on the 1C platform. Inside are twenty-two skills under `profile/skills`: code analysis through `bsl-analyzer`, environment setup, publishing and stopping the web client, 1C:Fresh adaptation checks, query composition, versioning and task handoff. Alongside sit rules, seven named agent roles and a global task scaffold with the `/Задача`, `/Продолжить` and `/Статус` commands. The `1c-ninja-mcp` component runs on OneScript and is built on `autumn-mcp`. It works in two modes: static searches a configuration export, and live calls the `NinjaLive` extension inside the infobase over HTTP at `/hs/ninja-live`. The `live_extensions_list` tool lists the infobase's extensions without launching the 1C client. The `install/kit.ps1` installer supports `doctor`, `verify`, `apply`, `lock` and `deps`. `deps` installs OneScript, `vanessa-runner`, `bsl-analyzer`, `ripgrep`, Node and Playwright, Apache and a toolkit. You bring the 1C platform from your own distribution. Skills and rules are wired in through paths in the global `~/.config/opencode/opencode.jsonc`.
Who it is for. 1C developers on Windows who work through OpenCode and want a ready set of skills, rules and MCP instead of assembling the environment by hand.
Good fit when
- A fresh machine without tools: you install the 1C platform yourself and `kit.ps1 deps` sets up the rest
- The agent must check syntax and read the event log of a live infobase through the extension
- A configuration extension for 1C:Fresh must be checked against requirements before publishing
- Work on a task spans several sessions and its state must live in the project's `Задачи/` folder
- A configuration must be published to a web server for tests and unpublished on command
Not a fit when
- You work in Claude Code or Cursor: the kit targets a single harness, OpenCode
- The 1C platform is not installed and cannot be obtained: live mode and publishing do not work without it
- You need a narrow tool such as one MCP for syntax-helper lookups: the kit pulls many dependencies
- The working machine runs macOS or Linux: the installer is a Windows PowerShell script
Example request
Check a module's syntax in the live infobase through the NinjaLive extension and show the latest errors from the event log.Limitations
The 1C platform is installed separately from your own distribution. Platform 8.3 uses Apache on port 8083, and 8.5 on port 8085. 1C MCP secrets must not go into a global user config that is committed to git.
The installer targets Windows and PowerShell. There is one harness, OpenCode V2. Third-party tools such as OneScript, `vanessa-runner`, `bsl-analyzer`, Apache and the platform stay under their own licenses and are not vendored as binaries.
The static part of `1c-ninja-mcp` derives from lekot/mcp-1c under GPL-3.0, and its scaffold comes from `autumn-mcp`, also GPL-3.0. The repository page shows no license of its own for the kit; details are in `NOTICE.md`.
How to disable. Remove the skill and rule paths from `~/.config/opencode/opencode.jsonc` and delete the copied agents, commands and `taskctl.ps1` from `~/.config/opencode`. Unpublish Apache publications with the web-client stop skill.
FAQ
What is in 1c-ninja-kit?
Skills and rules under `profile/`, agent roles, the `1c-ninja-mcp` MCP server with the `NinjaLive` configuration extension, the `kit.ps1` installer and docs about the OpenCode harness. The kit version is in the `VERSION` file.
How do I install the kit on a clean computer?
Clone the repository and run three `kit.ps1` commands: `deps`, `doctor`, `apply`. Install the 1C platform from your own distribution beforehand. What `deps` installs and what stays manual is described in `docs/MACHINE-BOOTSTRAP.md`.
What modes does 1c-ninja-mcp have?
Static searches a configuration export and live works over HTTP with the `NinjaLive` extension at an address like `http://localhost:8083/<app>/hs/ninja-live`. For live, set `NINJA_URL`, `NINJA_USER` and `NINJA_PASSWORD` in the environment.
Does the kit work with Claude Code?
The README names one harness, OpenCode V2: skills and rules are wired through paths in its global config. Connecting to Claude Code is not documented, so you would have to set it up yourself.
Where do I put the infobase password?
In the project's `opencode.jsonc`, not in the user config. A rule explicitly forbids 1C MCP secrets in a global config that may end up in git.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA shared skill and tooling infrastructure for 1C development, wired in as a git submodule and laid out across several agents at once
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
Universal Agent Skills for safely working with 1C extensions: an isolated session, selective export and validation before applying changes
A kit of skills, agents and rules for 1C development in Claude Code and Cursor: metadata, forms, DCS, extensions, infobases and web client
A skill for 1C platform batch operations: build and unpack data processors, load and dump configurations and extensions, launch the base
1C AI Development Kit: 1C skill collection
1C AI Development Kit
A set of 52 Claude Code skills and agents, plus Cursor rules, for the full 1C:Enterprise 8.3 development cycle, assembled from several community projects
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| 1c-ninja-kit (this card) | no | 1 | |
| 1c-agent-kit | no | 0 | another 1C kit without its own live extension NinjaLive |
| 1C AI Development Kit | no | 170 | a kit for a different harness and toolset |
README in short
The README covers a three-command quick start, the directory layout, the global task scaffold and hard rules such as Apache ports and listing extensions. Kit version 0.11.0. Links to detailed docs lead to `docs/opencode.md`, `docs/NAMING.md` and `docs/MACHINE-BOOTSTRAP.md`.