BSL Graph
bsl-graph
A draft Kotlin server that builds a 1C configuration's knowledge graph in NebulaGraph and exposes it to an agent through MCP and REST
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- The server reads and stores the configuration's full structure and code in an external graph database
- The project's draft stage raises the risk of data-interpretation bugs
Install
Manual install
./gradlew buildBuild the server with Gradle's Kotlin DSL.
This is third-party code. Review the repository files before installing.
What it does
The server reads a 1C configuration export in the standard format or in EDT format through the bsl-mdclasses library and builds a graph in the NebulaGraph graph database, where nodes are configuration objects (catalogs, documents, constants) and edges are their relations and dependencies. It ships a Sigma.js web UI for interactive graph visualization, a REST API and MCP protocol support for an agent's programmatic access to the graph data. The author explicitly marks the project a draft: metadata reading and graph export work, while code and query analysis are only on the roadmap.
Who it is for. For 1C developers and architects who need a visual map of configuration object relations and agent access to it.
Good fit when
- You need to visually explore relations between catalogs, documents and other objects of a large configuration
- You need a configuration knowledge graph reachable by an agent through MCP or REST
- You are ready to run NebulaGraph to store the graph
Not a fit when
- You need query-code or configuration-quality analysis: per the README this is only planned
- You need a stable production tool rather than an actively evolving draft
Example request
Build the relation graph for the Counterparties catalog and show which documents reference itLimitations
The author explicitly warns the project is a draft stage and may contain bugs or incomplete functionality. It needs Kotlin/JVM 17, Gradle, NebulaGraph as a separate database and, for visualization, a separate Vite frontend build. Per the author, extensive testing on real large configurations is still ahead.
How to disable. Stop the server and the NebulaGraph container, and remove the server from your MCP client configuration.
MCP
- Transport
- stdio, http
- Authentication
- not required
Security check
- The server reads and stores the configuration's full structure and code in an external graph database
- The project's draft stage raises the risk of data-interpretation bugs
README in short
The README openly marks the project a draft under active development. It describes the stack: Kotlin, Spring Boot, NebulaGraph, Clean Architecture, the 1c-syntax libraries for BSL and metadata parsing, and a TypeScript and Sigma.js frontend. It separately lists what is implemented versus planned, and a detailed five-stage roadmap: code analysis, query analysis, intelligent search, advanced analytics and scaling.
FAQ
What state is the project in now?
Metadata reading, graph export, web visualization, a REST API and MCP support are implemented. Code and query analysis and extensive testing on large configurations are only on the roadmap.
Which configuration export formats are supported?
The standard configurator export (files) and 1C:EDT format.
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