1C platform context exporter
platform-context-exporter
A Java console app that exports the 1C:Enterprise platform reference into JSON, XML, Markdown or an LLM-ready context format
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- It only reads the local reference file and exports it to text formats
- The MCP mode, when connected to a live base, only searches and reads the reference, it does not write data
Install
Manual install
./gradlew buildBuild the JAR from Gradle sources.
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.
Security check
- It only reads the local reference file and exports it to text formats
- The MCP mode, when connected to a live base, only searches and reads the reference, it does not write data
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.
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.
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