Semantic search over 1C platform help MCP
1c-sntx-sem
An MCP server for Cursor and Claude Desktop with hybrid embeddings and BM25 search over 1C platform help, the query language and the standard subsystems library
- 7 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs a Python server with hybrid search over 1C help and the BSP XML export
- Downloads the E5 model on first run; with an external embedding provider it sends query text there
Install
- Works in
- Services
Manual install
pip install -e ".[embeddings]"Installs with the local E5 embedding model; without the extras only the external OpenAI-compatible API option works.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs a Python server with hybrid search over 1C help and the BSP XML export
- Downloads the E5 model on first run; with an external embedding provider it sends query text there
This is third-party code. Review the repository files before installing.
What it does
The server builds a search index over 1C platform help (BSL and the SDBL query language) and over exported methods of standard subsystems library (BSP) common modules exported to XML. Search is hybrid: embeddings plus BM25 combined with RRF; embeddings default to a local E5 model, with options via an OpenAI-compatible API and Ollama. Each user builds the help database locally from their own licensed platform with the ingest command; the database is not part of the repository. There is an HTTP API with a browser search UI and a Docker option where the API runs in a container while a thin MCP client runs on the host.
Who it is for. For 1C developers on Cursor or Claude Desktop who need meaning-based, not just text, search over built-in platform help and the standard subsystems library.
Good fit when
- You need meaning-based search over 1C platform help, not exact term matching
- You work with the standard subsystems library and need examples of exported methods
- You are ready to build the index locally from your own licensed platform
Not a fit when
- No licensed 1C platform is installed to build the index from
- 8 GB-plus RAM for the Docker IVF index is not available, and accuracy is lower without it
Example request
Look up how a left join works in the 1C query language and show an example from the standard subsystems libraryMCP
- Transport
- stdio, http
- Authentication
- not required
Environment variables
SNTX_SEM_CONFIG- Path to config.yaml for the local in-process run.
SNTX_SEM_API_URL- API address for a thin MCP client on top of the Docker container.
Limitations
The help database is not shipped with the repository; each user builds it from their own platform, which takes 5 to 15 minutes on CPU. The local E5 embedding model is about 120 MB and downloads on first run. Rebuilding the IVF index in Docker needs 8 GB or more of Docker Desktop RAM; without it, search runs without ANN.
How to disable. Remove the 1c-syntax-sem entry from the client's mcp.json and stop the containers with docker compose down if Docker was used.
FAQ
Is torch needed on the host when using Docker?
No, the Docker option has mcp.json.docker.example with no torch; the heavy computation stays in the API container.
Is the standard subsystems library indexed?
Yes, as a separate bsp domain: exported methods from the ПрограммныйИнтерфейс areas in common modules exported to XML.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA local MCP server for semantic search over an exported 1C configuration, with a choice of embedding model and vector database
A read-only MCP service for hybrid 1C BSL code search: BM25 plus vector search, deduplication and reranking
An MCP server with hybrid search over 2262 community BSL code templates and a CRUD web interface built on Monaco Editor
A Dockerized MCP server for searching 1C dumps: structural index, call graph and semantic code search
1C configuration graph MCP server
1C Configuration MCP Server
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
A local OneScript MCP server for searching a 1C configuration dump right from Cursor
README in short
The README gives a quick start: install with the embeddings extras, copy the config, the ingest command to build the index from the platform, ingest-bsp for the standard subsystems library, and scan-examples for examples from local configurations. It covers the HTTP API and web UI, a Docker mode splitting API and MCP, choosing an embedding provider among sentence_transformers, an OpenAI-compatible API or Ollama, plus architecture docs and a decision log.