SkillFoxx

1c-configuration-indexer CLI

A local CLI indexer for 1C XML and BSL exports that chunks a configuration and uploads it to an external backend for semantic search

  • 0 ★ on the repository
  • Last commit
CLI

Extended access

Why this level

  • Sends configuration code and metadata fragments to an external webhook and Supabase outside the user's own infrastructure
  • Requires a token to access the external upload service
All reasons and checks
Russian stack

tarasov46/1c-configuration-indexerAuthor:tarasov46

Install

Manual install

python -m venv .venv && .\.venv\Scripts\python.exe -m pip install -e .

Installing the indexer from source on Windows.

Access and checks

How we review

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

  • Sends configuration code and metadata fragments to an external webhook and Supabase outside the user's own infrastructure
  • Requires a token to access the external upload service

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

What it does

The tool takes a local folder with a 1C configuration export (src and optionally exchanges with extensions), builds a compact index of navigation entities, RAG chunks and the relations between them, and, following a job from configuration-mcp, uploads the packaged chunks over HTTP to an external webhook that feeds them into Supabase. Full BSL and query text is not the source of truth: Supabase gets the path, line numbers, hashes, lengths and short previews, while the exact code stays in Git. It includes commands to retry failed upload parts, rebuild a package with smaller chunks, and run a local embedding worker as a manual fallback to the scheduled n8n or NeuroCore worker.

Who it is for. For teams already using a configuration-mcp and Supabase pairing for semantic search over 1C configurations, who need a local indexing and upload step.

Good fit when

  • You already run a configuration-mcp and Supabase setup and need a local indexer for it
  • You need to index a configuration or individual extensions without passing large files into the model's context

Not a fit when

  • You do not have your own configuration-mcp, Supabase project and the author's webhook infrastructure running: the tool targets that specific setup rather than working standalone
  • You need local semantic search without sending data out

Example request

Index the extension in the exchanges folder and upload the package per the configuration-mcp job

Limitations

The tool sends configuration chunks over HTTP to a specific webhook on the author's infrastructure (d4vibe.core.neuro42.ru) and into Supabase; without access to that infrastructure or your own equivalent, the upload-package and run-job upload commands are not useful. The local embedding worker optionally uses the OpenAI API. The README explicitly asks not to commit 1C exports, generated packages, .cf, .cfe, .dt files or tokens.

How to disable. Delete the project's virtual environment and stop running configuration-indexer.exe; the tool leaves no local background processes.

FAQ

Is full BSL code stored in Supabase?

No, Git remains the source of truth for code; Supabase gets the path, hashes, lengths and short previews.

Can indexing be tested without uploading?

Yes, the --no-upload flag on run-job builds the package locally without sending it.

Discussion

No questions or reviews yet.

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

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

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 closed-source Windows app with a set of local MCP servers: indexes a 1C configuration with extensions and answers the agent from real code, not memory

MCP serverExtended access6

README in short

The English README describes an autonomous flow from a job file to an uploaded package, a project layout with src and exchanges, a compact v2 package format with entities, search chunks and relations, separating upload from embedding generation via a scheduled worker, the upload-package, retry-failed-package and rechunk-package commands with a specific webhook address on the author's infrastructure, and a safety rule against committing exports and tokens.

README badge

Report a problem