onec-cfg2md CLI
A Go CLI that converts a 1C configuration metadata dump in CFG or EDT format into readable Markdown
- 38 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The built tool reads a local 1C configuration export
- Writes Markdown per metadata object and objects.csv to an output folder, never connects to a database
Install
- Services
Manual install
go build -o bin/onec-cfg2md .Build from source after git clone and go mod tidy.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The built tool reads a local 1C configuration export
- Writes Markdown per metadata object and objects.csv to an output folder, never connects to a database
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.
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.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsAn MCP server and portable admin tool for analyzing an exported 1C XML configuration: object listing, metadata structure, code search
An MCP server for Claude Code: full-text search over multiple 1C XML+BSL configuration exports in a local SQLite FTS5 database
1C AI development environment
1C AI Development Environment
1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C
1c-enterprise-skill: developing 1C configurations from XML and BSL
1c-enterprise-skill
A skill with a linter and templates: an agent creates and edits 1C 8.3 configurations in XML and BSL sources without manual entry in the Configurator
conf-doc: semantic search over a 1C configuration
Документация из конфигурации 1С (conf-doc)
An MCP server for Cursor with a web UI: indexes a 1C configuration's export once on the server and gives an agent semantic search over the documentation
1C configuration graph MCP server
1C Configuration MCP Server
An MCP server builds a metadata and call graph from a 1C configuration's XML and BSL export, with optional semantic search via an external embedder and Qdrant
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.