SkillFoxx

onec-config-mcp

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

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

Extended access

Why this level

  • A Python indexer loads XML and BSL configuration dumps into SQLite FTS5
  • The MCP server only searches the index and never writes to the 1C database
All reasons and checks
Russian stack

asgdeveloper/onec-config-mcpAuthor:ASGDeveloper

Install

Manual install

git clone https://github.com/ASGDeveloper/onec-config-mcp
cd onec-config-mcp
pip install -e .

Installs the package; next, config.json needs to be filled in and the indexer run.

Access and checks

How we review

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

  • A Python indexer loads XML and BSL configuration dumps into SQLite FTS5
  • The MCP server only searches the index and never writes to the 1C database

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

What it does

The server indexes 1C configurations exported as XML and BSL into a local SQLite database with FTS5 full-text search and gives 11 tools: code search with AND/OR/NOT syntax, metadata object search by name, getting a module's full code, finding a procedure or function definition with its line number and deprecation flag, getting a procedure body without reading the whole file, a module map without source, and lists of callers and callees. Several configurations can be indexed at once at different depths: standard ones like БП or УНФ only need base objects without forms, while your own configuration and libraries like БСП can be indexed fully. The get_object_metadata tool separately shows which of an object's fields the platform actually indexes, following the logic from 1C's official database table index documentation. The index updates automatically on file changes via watchdog.

Who it is for. For 1C developers on Claude Code who work with several exported configurations and want fast code and metadata search without opening the Configurator.

Good fit when

  • You need full-text search across several configurations' BSL code at once
  • You need to see who calls a procedure and what it calls, without reading the whole module
  • You need to check which of an object's fields are actually part of the database index when designing filter conditions

Not a fit when

  • You have no XML+BSL configuration export from the Configurator or EDT
  • The index database path falls under AppData\Local: Claude Code's UWP sandbox redirects that path

Example request

Find all calls to the ПроверитьПрава procedure and show its body

MCP

Transport
stdio
Authentication
not required

Limitations

The get_callees call graph is built on a regex heuristic and does not distinguish an object method call from a global module function call. The indexed-fields analysis does not cover additional composite Indexes, which are only available under the platform's KORP license, or special cases for hierarchical catalogs. After a database schema update, the old index.db is incompatible and must be deleted before reindexing. The database path must not sit under AppData\Local because of Claude Code's sandbox.

How to disable. Remove the onec-config-mcp entry from ~/.claude/.mcp.json and delete index.db if it is no longer needed.

FAQ

Can I index several configurations at once?

Yes, config.json accepts a list of configurations with separate paths and indexing-depth settings, and the tools filter by configuration name.

Why can't the database live under AppData\Local?

Claude Code on Windows runs in a UWP sandbox that redirects that path, so the README advises keeping db_path in Documents or elsewhere.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
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

1C configuration graph MCP server

1C Configuration MCP Server

Russian stack

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

MCP serverExtended access4
Russian stack

A local read-only MCP server suite for 1C: a Rust code indexer, metadata skills, a prompt gallery and platform help search, with evidence-backed answers

MCP serverExtended access
Russian stack

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

MCP serverExtended access

README in short

The README lists the features: FTS5 search, object and procedure search, a module map, a call graph, auto-reindexing and multi-configuration support. It gives pip install steps, the config.json format with an example of two configurations at different indexing depths, indexer commands, connecting to Claude Code via the global .mcp.json, and the list of allowed tools for settings.local.json. Each of the 11 tools is described with its parameters, the indexed_fields and auto_indexed_fields logic is explained with a reference to 1C's own documentation, and what is not implemented is explicitly listed. MIT license.

README badge

Report a problem