BSL CallGraph MCP Server

Install

Manual install

git clone https://github.com/ShustovM/bsl-callgraph.git
cd bsl-callgraph
npm ci
npm test

This is third-party code. Review the repository files before installing.

What it does

The server indexes .bsl files in memory and gives an MCP client seven tools: find_symbol and search_symbols to find definitions by exact name or substring, get_callers and get_callees to find calling and called procedures, get_impact to transitively walk a change's impact radius, reindex to rebuild the index after files change, and stats plus server_info for server state and capabilities. Each call is classified as resolved (one known target), ambiguous (several candidates) or dynamic (needs a runtime type), and exact mode returns only resolved edges while exploratory mode shows ambiguous candidates with a confidence note. A stateful lexer recognizes Russian and English Процедура/Procedure and Функция/Function declarations, Асинх/Async and Экспорт/Export, including multiline signatures, and does not turn query text inside strings into graph edges. The analysis is static and deliberately lightweight: not a BSL compiler or full type inference, and results should be treated as navigation evidence, not proof.

Who it is for. For 1C developers who need to quickly estimate a change's impact radius in a large configuration without manually walking through files.

Example request

Find everyone who calls the РассчитатьСумму function and estimate the impact radius of changing it to depth 3

Limitations

Dynamic dispatch and values stored in variables do not always resolve to a single target, identical symbol or module names can be ambiguous, and preprocessor behavior, type inference and runtime metadata are not evaluated. The BSL root is set once at startup by the client and cannot be replaced by a tool call. Results carry no guarantee of fixed latency or an exact token-saving ratio.

How to disable. Remove the server registration from the MCP client, for example codex mcp remove bsl-callgraph, and stop the server process; it creates no disk cache to clean up.

MCP

Transport

stdio

Authentication

not required

Security check

• The tools are strictly read-only, and the server executes no BSL code and needs no network
• Responses include symbol names, module names and relative file paths, visible to the connected client

README in short

The README details the seven tools with their parameters, the resolved/ambiguous/dynamic edge classification, the accuracy limits of static analysis, and a privacy section: parsing happens locally, the server does not execute BSL and needs no network, but MCP responses are seen by the connected client and possibly a remote agent per its policy. It gives source-install commands, configuration for Codex CLI, Claude Code and a generic stdio client with POSIX and Windows examples, and a troubleshooting and uninstall section. Baseline and benchmark scripts measure performance on your own machine. MIT license.

Related