1C modules MCP server
MCP 1C Modules Server
A minimal Node.js stdio MCP server that gives an agent 1C module texts from a configuration export directory
- 19 ★ on the repository
- Last commit
Extended access
Why this level
- Starts a local Node server that reads 1C modules only inside MODULES_DIR
- Searches modules with regular expressions and never writes to the configuration
Install
- Works in
- Services
Manual install
npm installInstall dependencies before the first run.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Starts a local Node server that reads 1C modules only inside MODULES_DIR
- Searches modules with regular expressions and never writes to the configuration
This is third-party code. Review the repository files before installing.
What it does
The server works over a plain directory holding a 1C configuration export produced by DESIGNER /DumpConfigToFiles, and gives an agent three tools: listing module files by a glob pattern, reading a specific module by relative path with a byte-size cap, and case-insensitive regex search across modules. Access is restricted to the directory set in the MODULES_DIR environment variable, and the server does not go outside it.
Who it is for. For 1C developers who already have a file-based configuration export and need a quick way to let an agent read and search module texts.
Good fit when
- You have a 1C configuration export directory from DumpConfigToFiles
- You need simple grep and module file reading without parsing XML metadata
- You want a lightweight MCP server without Docker and dependencies beyond Node.js
Not a fit when
- You need structured metadata information rather than module text
- The configuration export is stale: the server does not check its freshness
Example request
Find all calls to the GetBalances function across the configuration's modules and show them with contextMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
MODULES_DIRrequired- Path to the directory with the 1C configuration's exported modules.
Limitations
No license is specified. The server does not refresh the export itself, and the README explicitly advises updating the MODULES_DIR directory manually on a regular basis. The tools only read files, the server does not write changes into the configuration.
How to disable. Remove the 1c-modules-stdio server from your MCP client configuration.
FAQ
How do I get the export directory for MODULES_DIR?
Through the 1C configurator's DESIGNER /DumpConfigToFiles command, which saves modules as bsl, txt or 1c files.
Can the server go outside MODULES_DIR?
No, the README explicitly states access is restricted to that directory.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsTen MCP servers for 1C development: platform reference, targeted object dump and load, COM, storage, file search and BSL Language Server
An MCP server and portable admin tool for analyzing an exported 1C XML configuration: object listing, metadata structure, code search
A Docker server with a read-only core and pluggable modules: metadata, code, forms and relations of several 1C configurations through one MCP contract
A native component that runs a full MCP server inside 1C: tools, resources and prompts are written in BSL, while a DLL handles the protocol
A Go MCP server for debugging 1C over the HTTP Debug Protocol: breakpoints, step execution and variable inspection
A single-binary Go MCP server: the agent sees 1C metadata, searches code, runs read-only queries and writes accurate BSL
README in short
The README, which mirrors a publication on INFOSTART.RU, describes a minimal stdio server for reading 1C modules: Node.js 18+ requirements, npm install setup, running with the MODULES_DIR variable, a Cursor connection example, and the three tools list_module_files, read_module_text and grep_modules.