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
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- The server only reads files inside MODULES_DIR, there is no write access to the configuration
- The grep_modules search runs a regex over local files, with no network requests
Install
Manual install
npm installInstall dependencies before the first run.
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 contextLimitations
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.
MCP
- Transport
- stdio
- Authentication
- not required
| Environment variables | |
|---|---|
| MODULES_DIR required | Path to the directory with the 1C configuration's exported modules. |
Security check
- The server only reads files inside MODULES_DIR, there is no write access to the configuration
- The grep_modules search runs a regex over local files, with no network requests
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.
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.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything