SkillFoxx

BSL Graph MCP

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

  • 50 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

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
All reasons and checks
Russian stack

alkoleft/bsl-graphAuthor:alkoleft

Install

Manual install

./gradlew build

Build the server with Gradle's Kotlin DSL.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • 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

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 it

MCP

Transport
stdio, http
Authentication
not required

Limitations

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.

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.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

Loads a 1C configuration XML export into Neo4j and gives read-only MCP access to metadata, BSL routines and rights via text and full-text search

MCP serverExtended access1

1C configuration graph MCP server

1C Configuration MCP Server

Russian stack

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

MCP serverExtended access4
Russian stack

A local knowledge graph of a 1C configuration for an agent: Memgraph and ONNX embeddings with no cloud, for bases with hundreds of thousands of routines

MCP serverExtended access12
Russian stack

A local stdio MCP server on Node.js: builds an in-memory call graph over a 1C BSL source export and finds definitions, callers, callees and the impact radius

MCP serverExtended access
Russian stack

Five independent Docker-based MCP servers: a Neo4j metadata and call graph, static BSL analysis, platform syntax help, a query builder and 1C coding standards

MCP serverExtended access
Russian stack

A single-binary Go MCP server: the agent sees 1C metadata, searches code, runs read-only queries and writes accurate BSL

MCP serverBroad access255

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.

README badge

Report a problem