onec-cfg2md
A Go CLI that converts a 1C configuration metadata dump in CFG or EDT format into readable Markdown
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads local dump files and writes Markdown and CSV, does not connect to a database
- Does not execute 1C code and does not modify the source configuration
Install
Manual install
go build -o bin/onec-cfg2md .Build from source after git clone and go mod tidy.
This is third-party code. Review the repository files before installing.
What it does
The tool automatically detects the dump format: CFG (Configurator XML files with Configuration.xml at the root) or EDT (MDO files with .project and src/ at the root), and generates one Markdown file per metadata object with its header attributes and tabular sections, plus a shared objects.csv catalog summarizing every object. It supports documents, catalogs, enums, characteristic type charts, accumulation and information registers, constants and filter criteria, and the type set can be narrowed with the --types flag. The output is meant to be fed to an MCP server or another agent tool that needs textual context about the configuration structure without parsing raw XML or MDO files.
Who it is for. For 1C developers who need a compact textual context of configuration metadata for an agent or another MCP tool.
Good fit when
- You need to feed an agent a description of metadata objects without parsing raw XML or MDO
- You have a CFG or EDT dump and want one readable representation
- You need a CSV catalog of all configuration objects for a quick overview
Not a fit when
- You need full MCP access to a live database with queries, not just a text overview
- You need to convert BSL modules, not just metadata objects: the tool does not process those
Example request
Convert my EDT configuration dump into Markdown and show me the structure of the Order documentLimitations
The tool is not an MCP server itself, but a file generator meant for later use in MCP or another tool. The README does not describe pre-built binaries for different OSes, only go build from source. Not all 1C metadata types are supported, only the eight listed in the README table.
How to disable. Simply stop running the onec-cfg2md binary and delete the generated Markdown and CSV files if they are no longer needed.
Security check
- Only reads local dump files and writes Markdown and CSV, does not connect to a database
- Does not execute 1C code and does not modify the source configuration
README in short
The README lists supported formats (CFG, EDT) and eight metadata types with their CLI keys, gives installation commands via go build, run examples with the --format, --types and --verbose flags, the output Markdown file naming and content template, the objects.csv format, the Go project structure (cmd, pkg/detector, pkg/generator, pkg/parser) and make commands for building and testing.
FAQ
Do you need to specify the format manually?
No, the tool auto-detects it, but you can force it with --format=cfg or --format=edt.
Can you process only documents?
Yes, the --types=documents flag limits the set of metadata types processed.
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