SkillFoxx

1C MCP server suite in Docker

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

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

  • 10 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • Indexes and sends configuration code fragments to an external embedding provider unless a local option is chosen
  • Uses 1C license keys and credentials stored in .env
All reasons and checks
Russian stack

ilya-batalov/mcp-1cAuthor:ilya-batalov

Install

Manual install

Copy-Item .env.example .env

First step: fill in license keys and embedding API keys.

Access and checks

How we review

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

  • Indexes and sends configuration code fragments to an external embedding provider unless a local option is chosen
  • Uses 1C license keys and credentials stored in .env

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

What it does

The project brings up a set of always-on global MCP servers through Docker Compose (syntax check, platform help search, code checker, standard-library search, forms handling, code template search) plus separate servers per 1C configuration under the projects folder. Each configuration needs a report and source export from the Configurator, after which you can run the metadata profile for code and metadata search, a cloud profile as a cloud-embeddings alternative, and a graph profile with a Neo4j database for tracing object relationships. PowerShell scripts handle starting, stopping, backups and generating mcp.json for Cursor.

Who it is for. For 1C developers on Windows using Cursor who want a full set of infrastructure MCP servers for one or several configurations at once.

Good fit when

  • You need a full set of servers at once: syntax, help, code checking, the standard library, forms, templates
  • Several 1C configurations are maintained, each needing its own metadata and code index
  • You need graph-based search over configuration object relationships via Neo4j

Not a fit when

  • Docker and PowerShell are unavailable or work happens outside Windows: the management scripts are written for PowerShell
  • You want a minimal local server without Docker and without embedding API keys
  • There are no 1C license keys and platform install to export the configuration

Example request

Find all places in the buh configuration that use the Settlements accumulation register, and show related objects through the graph

MCP

Transport
stdio, http
Authentication
not required

Environment variables

GLOBAL_OPENAI_API_KEY required, secret
Key for an OpenAI-compatible embedding API used by the global help_search, ssl_search and template_search servers; the README shows an OpenRouter example.
OPENAI_API_KEY required, secret
Key for CodeMetadata in the project's metadata profile, unless the cloud profile is used instead.
GRAPH_OPENAI_API_KEY secret
A separate key for Graph Metadata Search; a local provider such as LM Studio can be used instead.

Limitations

The global help_search, ssl_search and template_search servers use GLOBAL_OPENAI_API_KEY and an embedding model over an OpenAI-compatible API, with the README giving an OpenRouter example, so several servers won't work without an external embedding provider. CodeMetadata also expects OPENAI_API_KEY by default unless the cloud profile is chosen. The management scripts are written in PowerShell, and the README does not claim cross-platform support. 1C license keys and a path to the platform install are required in .env.

How to disable. Stop the servers with stop-global.ps1 and stop-project.ps1 -Name <name>, then remove the entries from Cursor's mcp.json.

FAQ

Can only some global servers be started?

Yes, the -Services parameter of start-global.ps1 accepts a list of names, for example syntax_check,help_search.

Is Neo4j required for graph search?

Yes, the graph profile brings up neo4j together with graph_metadata, as a separate profile on top of the regular metadata one.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

A ready-made Cursor setup: a live 1C infobase via LN_MCP plus seven Docker containers of MCP_Distr static analysis for code and BSP search

MCP serverExtended access

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

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

MCP serverExtended access12
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
Russian stack

Ten MCP servers for 1C development: platform reference, targeted object dump and load, COM, storage, file search and BSL Language Server

MCP serverBroad access1

README in short

The README describes the repository layout of global and per-project MCP servers on Docker Compose, gives a step-by-step quick start from filling in .env to installing mcp.json in Cursor, a table of PowerShell scripts, a port table for global servers and for six ready-made configurations, instructions for adding a new configuration, tables of the metadata, cloud and graph profiles, and environment variables for indexing and embeddings. It ends with links to the project's external documentation and to Cursor Rules for 1C.

README badge

Report a problem