BSL Analyzer MCP
A Rust-based Language Server for BSL with code diagnostics, incremental analysis and a built-in MCP server for AI agents
- 117 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Live MCP tools execute code and queries against a live 1C infobase through --onec-url
- The workspace profile reads the source code of the whole project
Install
- Works in
- Services
Manual install
curl -fsSL https://raw.githubusercontent.com/itrous/bsl-analyzer/develop/scripts/install.sh | bashBinary install on Linux and macOS.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Live MCP tools execute code and queries against a live 1C infobase through --onec-url
- The workspace profile reads the source code of the whole project
This is third-party code. Review the repository files before installing.
What it does
BSL Analyzer applies the rust-analyzer architecture to the 1C:Enterprise language: incremental computation through Salsa, parsing into a full-fidelity CST and a layered HIR with type inference. That gives semantic hover and completion aware of an expression's real type, symbol-based find references and rename instead of text search, and flow-sensitive diagnostics such as unreachable code. Besides an LSP for editors, the binary can analyze a project from the console with SARIF or JSONL output for CI, and it starts an MCP server that gives AI agents search over 1C code, platform reference, SDBL queries and debugging. Platform method and type data comes from the built-in 8.3.27 help.
Who it is for. For 1C developers who want modern BSL diagnostics and completion in their editor, and for those connecting an AI agent to platform code and reference through MCP.
Good fit when
- You need BSL code-quality diagnostics and SARIF reports for CI
- You want a modern LSP with semantic hover and completion for VS Code, Cursor or Zed
- You need an MCP server so an agent can search project code, platform reference and SDBL queries
Not a fit when
- The project uses a 1C platform older than 8.3.27: method and type facts come only from that version of the reference
- You need a stable production tool: the project is explicitly described as experimental
Example request
Check the project for unreachable branches and lost Return statements, show the report in SARIF formatMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
NAPARNIK_TOKENsecret- 1C:Naparnik token for extended reference in the reference profile.
EMBEDDING_URL- Embeddings service address for semantic search over the reference.
Limitations
The author explicitly calls the project an experimental Language Server. Analysis and diagnostics target the full 8.3.27 API, and earlier compatibility modes are not checked. Live MCP tools need the infobase URL and credentials, and the reference profile optionally needs an EMBEDDING_URL and a 1C:Naparnik token.
How to disable. Remove the server with claude mcp remove or the equivalent for your client, uninstall the bsl-analyzer-lsp editor extension and delete the installed binary from PATH.
FAQ
What is the difference between the reference and workspace profiles?
reference gives platform and ITS reference without tying to a specific repository, workspace searches project code, metadata and a live 1C base through --onec-url.
Which platform versions are supported?
The project is developed and tested only against 1C:Enterprise 8.3.27, and API facts come from that version's reference.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsMCP wrapper for BSL Language Server
BSL MCP Server
A small MCP server that runs BSL Language Server as a JAR file and gives an agent BSL code analysis and formatting as JSON
onec-hbk-bsl: BSL linter and MCP
1C HBK BSL (onec-hbk-bsl)
A BSL CLI linter and formatter with 180 diagnostics, an LSP server for VS Code and Cursor, and MCP tools for local AI assistants
An MCP server for BSL syntax checks on BSL Language Server in Docker: send code, get back JSON errors and warnings with no Java install needed
MCP server with the 1C platform reference and validation of BSL code against the real API of a chosen platform version
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
An MCP server for analyzing large 1C codebases with less context: the agent runs scripts server-side and gets only a compact result
Alternatives
Tools by other authors for the same tasks.
- BSL MCP Analyzer4 Repository stars
README in short
The README explains the idea: apply the rust-analyzer architecture to BSL to get incremental analysis, semantic hover and flow-sensitive diagnostics. It covers installation via script for Linux/macOS/Windows and a separate editor extension, the lsp, analyze and mcp serve run modes, MCP auto-install through mcp install with reference and workspace profiles, and links to detailed architecture and configuration docs.