1creader: read a 1C file infobase
1creader
A read-only MCP and CLI that read a 1C file infobase directly from 1Cv8.1CD and build a configuration map for an AI agent and Obsidian
- 9 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Runs a Python server that parses the 1Cv8.1CD file without the platform
- Gives the agent catalog and register data, which usually holds customers, employees and counterparties
- Writing to the database is not supported
Install
- Works in
- Services
Manual install
git clone https://github.com/vengeoff/1creader.git
cd 1creader
python3 -m venv .venv && .venv/bin/pip install -e .Install from source.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Runs a Python server that parses the 1Cv8.1CD file without the platform
- Gives the agent catalog and register data, which usually holds customers, employees and counterparties
- Writing to the database is not supported
This is third-party code. Review the repository files before installing.
What it does
The tool reads the 1Cv8.1CD file of a file-based 1C infobase without the platform and without an XML export, parsing metadata, BSL module text, forms, and catalog and register data. From that it builds a compact MAP.md for an agent, an Obsidian vault with relation and subsystem maps under vault/, full schemas under developer/, and RAG chunks in ai/retrieval.json. The same MCP server connects to Cursor, Claude Code and Codex, with tools for the index, object schemas, modules, catalog data and Obsidian notes. A parallel onecreader CLI offers info, ls, obj, module, search, form and catalog-data commands.
Who it is for. For anyone handed an unfamiliar or legacy 1C file infobase with no documentation who wants to understand its structure quickly, without the platform and without an XML export.
Good fit when
- You need to understand an unfamiliar or legacy 1C configuration from a 1Cv8.1CD file
- You need a configuration map for an agent in Cursor, Claude Code or Codex without an EDT or XML export
- You want a navigable Obsidian base with subsystem and object relation maps
Not a fit when
- You need to write changes back to the database: the tool only reads
- The file infobase is in a 1CD format newer than 8.3.8, which the project does not yet support
- The database is held open by the Configurator and the file is locked for reading
Example request
Show the module of the Nomenclature catalog and explain how it relates to order documentsMCP
- Transport
- stdio
- Authentication
- not required
Limitations
Only the 1CD 8.3.8 format and platform 8.3.8+ are supported; newer file formats are not claimed. The tool only reads the database, write access is not supported in any mode. The file infobase must be accessible as a file on disk, and the Configurator can hold a lock that blocks reading. Python 3.10 or newer is required.
How to disable. Remove the 1creader entry from .mcp.json, .cursor/mcp.json or .codex/config.toml, and delete the .onecreader artifact folders if you no longer need them.
FAQ
Does it need the 1C platform installed?
No, the tool reads the 1Cv8.1CD file directly and does not require the platform to be installed.
Can catalog data be read, not just the structure?
Yes, the config_catalog_data tool and the catalog-data command read data from the database tables, not just the object schema.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA local read-only MCP server suite for 1C: a Rust code indexer, metadata skills, a prompt gallery and platform help search, with evidence-backed answers
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
A stdio MCP server that indexes a 1C structure XML export and code into SQLite and gives an agent search over objects and procedures
An MCP server for Claude Code: full-text search over multiple 1C XML+BSL configuration exports in a local SQLite FTS5 database
1C Agent Platform: three MCP servers for 1C
1C Agent Platform
A platform of three MCP servers for reading, writing and intelligence operations on 1C:Enterprise configurations and infobases
A strictly read-only MCP server on a 1C HTTP service: 39 tools for metadata, queries, accounting and reports on any configuration
README in short
The README explains why reading the file infobase directly is useful, gives a quick start with the onecreader init command, describes the artifact layout (MAP.md, vault, developer, ai) and the Obsidian vault structure, shows MCP connection snippets for Cursor, Claude Code and Codex, a table of seven MCP tools, and a list of CLI commands. It ends with what gets read (catalogs, documents, registers, modules, database data, DBSCHEMA) and honest limitations on format support and the read-only mode.