conf-doc: semantic search over a 1C configuration

Install

Manual install

copy config.docker.example.yaml config.yaml
docker compose build
docker compose up -d

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

What it does

The server parses a standard Configurator export-to-files output (catalogs, documents, enums, registers) and builds markdown documentation, a structural SQLite index and a FAISS vector index from it. Indexing happens once through the web UI or the CLI, and Cursor connects a thin stdio MCP client, conf-doc mcp, which has no direct access to the export files, only to the HTTP API. The agent gets tools for semantic search, reading an object's card, and a specific reference fragment. Search runs by default on local sentence_transformers embeddings with no keys or network calls; it can be switched to an OpenAI-compatible embedding API for better quality. A separate optional RAG layer via conf_doc_query answers the whole question if an LLM provider (Ollama or OpenAI) is configured on the server; it's off by default.

Who it is for. For 1C developers in Cursor who want fast semantic search over a large configuration without manually browsing the XML export.

Example request

Find where the Leave document's attributes are stored in the configuration, and show the full reference text

Limitations

The web UI and HTTP API have no built-in authentication; the README explicitly warns against exposing the port externally without a reverse proxy. The /query RAG endpoint is off by default (llm.provider: none) and returns HTTP 503 until Ollama or OpenAI is explicitly configured on the server. Switching to API embeddings changes the vector dimension and requires a full index rebuild. The same author maintains a related OData bot project (1c-odata-skill) where conf-doc is used as one component, so some logic may overlap.

How to disable. Stop the container with docker compose down and remove the conf-doc mcp block from .cursor/mcp.json.

MCP

Transport

stdio

Authentication

not required

Security check

• Only reads and indexes the XML export, doesn't write to a database or configuration
• The web UI and HTTP API have no built-in authentication, unsafe to expose externally

README in short

The README describes in detail a Docker quick start with local indexing via the web UI, a full list of seven MCP tools and environment variables, an HTTP API with configuration and job management endpoints, a separate section on the difference between embedding-based search and optional LLM-backed RAG, a comparison of local versus API embedding providers, the output/ structure with XML, markdown, FAISS and SQLite stores, and a mention of the project's conf-doc-search skill for the Cursor Agent.

Related