SkillFoxx

BSL Code Search MCP

A local read-only MCP server for 1C code search on the Zoekt engine: fast lexical and regex search over your own configuration dumps

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

Extended access

Why this level

  • Runs a binary that indexes the 1C export with Zoekt and searches it
  • The tools are read-only, the index keeps source text on disk
All reasons and checks
Russian stack

iiityraeliii/bsl-code-search-mcpAuthor:IIITYRAELIII

Install

Manual install

.\bsl-code-search-mcp.exe index --name "my-configuration" --source "C:\path\to\configuration\sources" --default

Indexes a configuration dump and makes it the default for queries without an explicit corpus.

Access and checks

How we review

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

  • Runs a binary that indexes the 1C export with Zoekt and searches it
  • The tools are read-only, the index keeps source text on disk

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

What it does

The tool indexes a 1C configuration exported to files (from the Configurator or EDT) using the Zoekt engine and gives an agent two strictly read-only tools: search_code for lexical, exact or regex search over code with line context, and list_corpora to list attached corpora and their stats. You can index several configurations under different names, set one as the default for unqualified queries, and search across all of them at once with the allCorpora flag. Indexing only reads the explicitly given source directory and only writes the local index; the server itself makes no network calls and never stores or returns source paths in tool responses.

Who it is for. For 1C developers who need fast search over large configuration exports directly from an agent, without sending code anywhere off their machine.

Good fit when

  • You need fast search for usage examples of a method or pattern across a whole configuration dump
  • You work with several configurations at once and need to search one or all of them
  • You need the configuration code to never leave the machine or go over the network

Not a fit when

  • You need semantic navigation, not just text search: definitions, callers, a call graph, which needs a different tool
  • Your platform is not Windows x64: other OSes are not officially tested

Example request

Find all places in the configuration that call ИзменитьРеквизиты and show the context

MCP

Transport
stdio
Authentication
not required

Environment variables

BSL_CODE_SEARCH_INDEX
Path to the index directory when using a non-default location.

Limitations

The repository contains no 1C configurations at all, including ERP and ZUP; you index your own dump. Only the Windows x64 build is officially tested. The index can be large, roughly twice the size of the source BSL text, and should be stored as carefully as the configuration dump itself.

How to disable. Remove the bsl-code-search-mcp entry from the MCP client config, and delete the local index folder if needed.

FAQ

Does the configuration code go over the network?

No, indexing only reads the given directory, the serve command makes no external network calls, and its backend listens on a random localhost port.

Can I search several configurations at once?

Yes, each configuration is indexed under its own name, and a search with allCorpora: true covers all attached ones at once.

How is BSL Code Search MCP different from searching 1C code in the Configurator?

A local read-only server indexes a 1C configuration dump from the Configurator or EDT with the Zoekt engine and gives the agent two tools, including search_code for lexical, exact and regex search. Search is fast and runs over your own dumps.

Does configuration code go to the network and can I search several configurations?

The index and search work locally and the server only reads files. Several configurations are indexed under different names with the index --name command and a dump path, as in the install block. The server ships as a Windows executable.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A read-only MCP service for hybrid 1C BSL code search: BM25 plus vector search, deduplication and reranking

MCP serverExtended access3
Russian stack

A Dockerized MCP server for searching 1C dumps: structural index, call graph and semantic code search

MCP serverExtended access79
Russian stack

An MCP server for Claude Code: full-text search over multiple 1C XML+BSL configuration exports in a local SQLite FTS5 database

MCP serverExtended access
Russian stack

A local MCP server for semantic search over an exported 1C configuration, with a choice of embedding model and vector database

MCP serverExtended access11
Russian stack

A SQLite code index with MCP tools for search, call graphs and metadata, including 1C dumps from Designer and EDT

MCP serverExtended access162
Russian stack

A local OneScript MCP server for searching a 1C configuration dump right from Cursor

MCP serverExtended access18

README in short

The README carefully describes three steps: choosing and indexing a source dump, checking attached configurations with the status command, and connecting an MCP client via the serve command. It gives search_code query examples with file, case and regex filters, and explains corpus-selection priority for different task types. A dedicated privacy section stresses that indexing writes nothing outside the local index, and the server tools are read-only with readOnlyHint and idempotentHint annotations. Build-from-source commands are given, and pinned dependency versions are mentioned.

README badge

Report a problem