SkillFoxx

MCP-1C: a 1C configuration structure server

MCP 1C

A Docker server with a read-only core and pluggable modules: metadata, code, forms and relations of several 1C configurations through one MCP contract

  • 12 ★ on the repository
  • Last commit
  • Apache-2.0
MCP server

Extended access

Why this level

  • Stores and indexes the full source code and structure of 1C configurations in its own data/ store
  • Requires an admin token with rights to upload and delete sources, whose compromise exposes the whole knowledge base
All reasons and checks
Russian stack

azeevan/mcp-1cAuthor:AzeevAN

Install

Manual install

cp .env.example .env
docker compose up -d

After filling .env with two different tokens, API_TOKEN and ADMIN_TOKEN.

Access and checks

How we review

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

  • Stores and indexes the full source code and structure of 1C configurations in its own data/ store
  • Requires an admin token with rights to upload and delete sources, whose compromise exposes the whole knowledge base

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

What it does

The server parses 1C configuration exports (structure, code, forms, relations, virtual tables, platform reference for several versions) and serves them to an agent through MCP, an SPA dashboard and an HTTP API. The always-on read-only core can be extended with capability modules: Forms builds Form.xml and Module.bsl from a canonical spec, validates the result and decompiles it back, without changing the configuration or database, and Metadata Authoring creates and checks an object's metadata bundle, also without writing into the configuration or infobase; all module operations are described as pure. A disabled module doesn't publish its tools and doesn't take up the MCP client's context. The server holds several configurations at once without mixing their data, and runs as a single Docker container with mandatory separate access and admin tokens and a strict non-root setup.

Who it is for. For 1C developers with several large configurations who need a persistently running local context server for an agent, not a one-off local process.

Good fit when

  • Several 1C configurations are maintained at once, and the agent must explicitly pick the right one
  • You want a human-facing dashboard for sources, relations and server state, not just an API
  • You need a form built from a spec with validation, without direct writes into the configuration

Not a fit when

  • You can't deploy Docker and prepare a data directory with the correct 10001:10001 owner: the README describes this as a mandatory step
  • You need direct writes into the configuration or infobase: both Forms and Metadata Authoring are intentionally pure and only return artifacts as text
  • You need a full MXL parser built in: the repository doesn't ship source HBK files or exports, only the runtime over prepared sources

Example request

In the Retail configuration, find all objects related to the stock register and show the relation graph

MCP

Transport
http, stdio
Authentication
API key

Environment variables

API_TOKEN required, secret
Access token for MCP and the dashboard, required, at least 32 characters.
ADMIN_TOKEN required, secret
Admin token for uploading, deleting and reloading sources, must differ from API_TOKEN.
MCP1C_CAPABILITIES
Bootstraps the enabled module set on first run, until data/server-settings.json exists.

Limitations

The official image requires two different random tokens of at least 32 printable ASCII characters before it even starts, without which the server won't run even on localhost. On Linux, the data directory must be owned by UID:GID 10001:10001 in advance; a plain mkdir -p won't do that. The repository ships no source HBK files, configuration exports or their indexes; those are prepared separately by the administrator and stay outside git. Only one heavy intake operation is supported at a time; a second one gets a 409 before its request body is even read. An unsigned or tampered shared-reference artifact is marked untrusted and the server won't open it.

How to disable. Stop the container with docker compose down and remove the server from your MCP client settings.

FAQ

Does the built form get written straight into the configuration?

No, the Forms module returns Form.xml and Module.bsl as text; the server itself never changes the configuration or infobase.

Can several configurations be handled in one install?

Yes, that's one of the stated reasons the server exists: the agent explicitly picks the configuration it needs and never gets another one's data by accident.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools

1C MCP server suite in Docker

MCP-серверы для 1С

Russian stack

A Docker Compose stack of MCP servers for 1C development in Cursor: syntax, platform help, the standard library, forms, graph search over a configuration

MCP serverExtended access10
Russian stack

A Docker gateway with one address instead of several MCP connections: 1C data, BSL navigation, ITS search via 1C:Napparnik, and a web dashboard

MCP serverBroad access5

Docker deployment for 1C MCP servers

MCP-серверы для 1С:Enterprise

Russian stack

Ready Docker Compose files and management scripts for nine 1C:Enterprise MCP servers: help, metadata, graph search, syntax checking

MCP serverExtended access
Russian stack

Five independent Docker-based MCP servers: a Neo4j metadata and call graph, static BSL analysis, platform syntax help, a query builder and 1C coding standards

MCP serverExtended access

1C metadata MCP server

1C_MCP_metadata

Russian stack

An MCP server over a 1C extension's HTTP service that exposes configuration metadata, searches objects and validates query syntax

MCP serverExtended access63
Russian stack

An MCP server and portable admin tool for analyzing an exported 1C XML configuration: object listing, metadata structure, code search

MCP serverExtended access2

README in short

The README describes in detail a read-only core with pluggable Forms and Metadata Authoring capability modules, a modern dashboard, a modular capability system that needs a fresh MCP session after enabling a module, and a very detailed Docker deployment runbook on a clean Linux host: preparing the data directory with a specific owner, two mandatory tokens, local/http/https-proxy access modes, the difference between Source A and Source B for loading configurations, a two-phase intake API with preview and explicit publication, upload size limits, and a signed read-only shared platform-reference artifact. It covers upgrading from version 3.3.0 to 4.0.0.

README badge

Report a problem