1C platform context exporter CLI
platform-context-exporter
A Java console app that exports the 1C:Enterprise platform reference into JSON, XML, Markdown or an LLM-ready context format
- 50 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- A Java app parses the shcntx_ru.hbk help file from the 1C platform install
- The mcp-server command starts a local MCP server that searches the platform API
Install
- Works in
- Services
Manual install
./gradlew buildBuild the JAR from Gradle sources.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- A Java app parses the shcntx_ru.hbk help file from the 1C platform install
- The mcp-server command starts a local MCP server that searches the platform API
This is third-party code. Review the repository files before installing.
What it does
The app reads the shcntx_ru.hbk reference file from a 1C platform installation directory and extracts structured info about global properties, methods and types into one of four formats, including a context format meant for feeding into an LLM's context. There is also a separate mcp-server command that starts an MCP server with fuzzy search over the platform API and detailed element info for Claude Desktop and similar clients, but the README warns that this functionality is moving to a separate project, mcp-bsl-context, so the MCP part should be treated as being phased out here.
Who it is for. For 1C developers who need an offline export of the platform reference into text for feeding to an LLM, IDE autocompletion or their own tooling.
Good fit when
- You need to export the 1C platform reference into JSON, XML, Markdown or context format with one command
- You need an offline source of platform global method and type data without a live MCP server
- You need a ready platform context file for an agent's prompt
Not a fit when
- You specifically need a live platform-reference MCP server: the README points to the separate mcp-bsl-context project for that
- You do not have access to the shcntx_ru.hbk reference file from a 1C installation
Example request
Export the 1C platform reference from /opt/1cv8 into context format in ./contextLimitations
Needs Java 17 and the shcntx_ru.hbk reference file from a 1C platform installation version 8.3.20 or newer for MCP mode. The built-in MCP functionality is marked as moving to mcp-bsl-context, so relying on mcp-server in this specific repository long term is not advisable.
How to disable. Delete the built JAR, and if MCP mode was used, remove the server from your MCP client configuration.
FAQ
Where did the MCP functionality go?
The README says it moved to a separate project, mcp-bsl-context, and remains here only as a temporary feature.
Which export formats are supported?
json (default), xml, markdown and context for LLMs.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsAn MCP server for the 1C platform API docs read straight from shcntx_ru.hbk help files, with keyword, semantic and hybrid search
1C platform reference over MCP
mcp-bsl-platform-context
An MCP server with the 1C syntax assistant reference: search functions, types, methods, properties and constructors from the installed platform
MCP server with the 1C platform reference and validation of BSL code against the real API of a chosen platform version
An MCP server that unpacks 1C's .hbk help, indexes it in Qdrant and gives the agent search over API, snippets and standards
1C built-in language help: a local MCP server
itcoolmcplang1c
A Rust MCP server that gives an agent the 1C built-in language reference from your own platform install, with a knowledge base built and kept entirely local
1C Platform Help MCP Server
Onec Platform Help MCP Server
An MCP and REST server with hybrid search (BM25 plus semantic) over the official 1C:Enterprise platform help
README in short
The README describes two modes: platform context export via the platform command in four formats, and an MCP server via the mcp-server command with fuzzy API search. It lists system requirements, the Gradle build, dependencies (Spring Boot, Spring AI, Picocli, 1c-syntax libraries) and a warning that the MCP part is moving to mcp-bsl-context. MIT license.