MCP:1C-DevTools
78 MCP tools for 1C development over local XML exports: metadata, code audit, queries, EPF, configuration diffing, and a verified API reference
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- The apply-and-build-cf batch automation applies configuration changes to a real infobase through the designer
- Changing operations require confirmed=true, but once passed they run without further questions
Install
Manual install
docker build -t onec-devtools . && docker run --rm -it -v $(pwd)/config-dump:/data/config:ro -v $(pwd)/src/cf:/data/src:ro onec-devtoolsThe main way to run it with the XML export mounted in.
This is third-party code. Review the repository files before installing.
What it does
The server works over a local XML configuration export and does not need a running 1C base. Tools are grouped by topic: metadata (tree, structure, search, dependencies, objects orphaned outside subsystems), audit (15 checks from query and code antipatterns to personal-data patterns and RLS rights), queries (validation, optimization, generation), EPF artifacts (validation, building, comparison), forms and DCS, integrations (exchange plans, XDTO), tests and quality, BSL helpers (reference lookup, generation, modal-call conversion) and configuration work (diffing, a pre-commit checklist). A separate verified_api.json is a registry of API names, each verified by actually running it on a live 8.3 platform through an EPF oracle rather than the author's memory: the verdict is exists, absent or unknown, with an explanation of why unknown must not be treated as absent. Batch automation on top of 1cv8.exe DESIGNER and ibcmd can apply and build a cf with backup and rollback, but requires explicit confirmed=true on any changing operation.
Who it is for. For 1C development teams that need a wide set of deterministic code and configuration checks with no running base, and no invented API names.
Good fit when
- You need query and code audits against specific antipatterns without manual reading
- You need to know for sure whether a platform method exists, instead of guessing from the model's memory
- You need a batch cf build with backup before any changing operation
Not a fit when
- You need real-time work with a live base: the tool targets static XML exports
- You do not need designer batch automation: that layer needs 1cv8.exe paths and explicit confirmation
Example request
Run the query antipattern audit over the configuration and check whether the ЭтоЧисло method exists on the Число objectLimitations
The verified API registry is still limited: 83 global functions, 10 catalog manager methods, 18 synonym pairs and 49 refuted names; unverified names are honestly marked unknown. Batch automation needs Windows, a path to 1cv8.exe, and explicit confirmed=true on changing steps. BSL Language Server, by the author's own note, does not replace this registry: its unknown-method diagnostic is off by default and heuristic without a metadata index.
How to disable. Stop the container with docker-compose down, or remove the onec-devtools entry from your MCP client configuration.
MCP
- Transport
- stdio
- Authentication
- not required
| Environment variables | |
|---|---|
| ONEC_DEVTOOLS_CONFIG_PATH required | Path to the 1C configuration XML export. |
| ONEC_DEVTOOLS_1C_PATH | Path to 1cv8.exe for batch automation. |
Security check
- The apply-and-build-cf batch automation applies configuration changes to a real infobase through the designer
- Changing operations require confirmed=true, but once passed they run without further questions
README in short
The README lists all 78 tools across eight lettered groups with a description of each, explains the verified API registry's three verdicts (exists/absent/unknown) and the evidence behind them, describes a client-server-configuration architecture with no running base, and covers designer and ibcmd batch automation with backup, rollback and argument passing without shell=True to preserve Cyrillic paths.
FAQ
What does an unknown verdict from bsl.syntax.help mean?
The name simply was not checked by the oracle and must not be treated as absent; it needs a separate check against ITS or a live run.
Can BSL Language Server be trusted as the source of truth for API existence?
No, its UnknownMember diagnostic is off by default and heuristic without a metadata index; the project's own verified registry exists for that reason.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything