MCP server for 1C infobases via COM
1C MCP Server
A Windows Python MCP server that connects to file and server 1C infobases via COMConnector and stores connection profiles with DPAPI-protected passwords
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Restricted write tools change data in the connected 1C infobase behind an explicit confirmation
- Stores the 1C user's login and password in local connection profiles
Install
Manual install
python -m venv .venv && .venv\Scripts\Activate.ps1 && pip install -e .Installs on Windows in a virtual environment.
This is third-party code. Review the repository files before installing.
What it does
The server connects to a 1C infobase passed in each tool call, via COMConnector on Windows, detecting the installed platform version from the registry itself and choosing the right V85 or V83 connector with a fallback on failure. It supports read-only queries, metadata lookup, object reads, lightweight analytics, and restricted write tools gated by an explicit confirmation flag and environment-based allowlists. Connection profiles with address, login and password can be saved; on Windows, passwords are stored via DPAPI when pywin32 is available, and the profile list never returns saved passwords. The server can write a detailed rotating diagnostics log with passwords masked.
Who it is for. For 1C developers on Windows who need an MCP server with explicit control over write operations and safe storage of connection passwords.
Good fit when
- You need agent access to a file or server 1C infobase specifically via COM on Windows
- Writes to the infobase must require explicit confirmation and be restricted by an allowlist
- You need to store several connection profiles without keeping passwords in plain text
Not a fit when
- You are not on Windows: the server uses COMConnector and has no alternative for Linux or macOS
- No 1C platform with a registered COM connector is installed
Example request
Connect to the test 1C infobase using the saved demo-file-base profile and show the Counterparties catalog structureLimitations
Works only on Windows with an installed 1C platform and a registered COMConnector for version 8.5 or 8.3. Without pywin32, profile passwords are not DPAPI-protected. The project is small, has no listed license, no releases and no stars.
How to disable. Remove the onec-mcp-server entry from your MCP client config and, if needed, the connection-profiles.json file with saved profiles.
MCP
- Transport
- stdio
- Authentication
- not required
| Environment variables | |
|---|---|
| ONEC_MCP_LOG_LEVEL | Diagnostics log level, for example DEBUG. |
| ONEC_MCP_LOG_PATH | Path to the rotating diagnostics log file. |
Security check
- Restricted write tools change data in the connected 1C infobase behind an explicit confirmation
- Stores the 1C user's login and password in local connection profiles
README in short
The English README describes a Python MCP server built on COMConnector for file and server 1C infobases. It covers platform and connector requirements, installing via venv and pip install -e ., running with the onec-mcp-server command over stdio, configuring the diagnostics log through environment variables, and the structure of a saved connection profile with the infobase address.
FAQ
Does the server return saved passwords?
No, the list_connection_profiles tool never returns passwords, only profile metadata.
How are writes to the infobase restricted?
Write tools require an explicit confirmation flag and are limited by an allowlist set through environment variables.
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