1C Log Checker MCP
1C Log Parser Service
Parser for 1C event and technology logs into ClickHouse, with Grafana dashboards and an MCP interface for agents
- 80 ★ on the repository
- Last commit
Extended access
Why this level
- Runs a Docker stack with ClickHouse, Grafana and an MCP server
- Tools change the technology log config on the 1C server
- Grafana has no auth by default, and logs may contain user data
Install
- Works in
- Services
Manual install
docker network create infra
cd deploy/docker
docker compose up -dFill in deploy/docker/.env and configs/cluster_map.yaml first. Outside a devcontainer remove the work_data volume from docker-compose.yml.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs a Docker stack with ClickHouse, Grafana and an MCP server
- Tools change the technology log config on the 1C server
- Grafana has no auth by default, and logs may contain user data
This is third-party code. Review the repository files before installing.
What it does
Reads 1C event logs (.lgf, .lgp, .lgx) and technology logs, loads them into ClickHouse and shows them in ready Grafana dashboards. The MCP server lets an agent query events from both logs in minimal or full format. Separate tools save, generate, restore and disable the logcfg.xml technology log config.
Who it is for. 1C developers and administrators investigating errors and performance on server databases.
Good fit when
- Find new event log errors from the last 24 hours
- Investigate locks, slow SQL and exceptions in the technology log
- Have the agent enable the technology log for specific events and restore settings afterwards
- Store and analyze logs from several databases in one place
Not a fit when
- No Docker, or your 1C servers do not run on Windows
- You need PostgreSQL or MS SQL log analysis: still on the roadmap
Example request
Show event log errors for the ERP database over the last day, grouped by error textMCP
- Transport
- http, stdio
- Authentication
- not required
Environment variables
LOG_DIRSrequired- Event log directories separated by semicolons
TECHLOG_DIRS- Technology log directories
TECHLOG_CONFIG_DIR- Non-system directory for logcfg.xml
CLICKHOUSE_PASSWORDsecret- ClickHouse password, default logchecker
LOG_RETENTION_DAYS- Log retention in days, default 30
Limitations
Designed for a Windows host with 1C logs and Docker Desktop. Requires manual conf.cfg edits per platform version and a cluster_map.yaml with cluster and database GUIDs. Technology log parsing has not been tested at scale, tests show about 170 records per second. Grafana runs without authentication by default.
How to disable. Remove the 1c-log-checker block from the MCP client config and stop the stack with docker compose down in deploy/docker. If the agent enabled the technology log, restore settings with logc_restore_techlog or logc_disable_techlog.
FAQ
Why is cluster_map.yaml needed?
It tells the agent the cluster and database GUIDs so it can request logs for a specific database. The service does not work without it.
How long are logs kept?
30 days by default, set by LOG_RETENTION_DAYS.
How fast is event log parsing?
According to the README, a 30 GB log with 250 million rows loads in about 50 minutes without deduplication.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA single-container web dashboard for monitoring and controlling a fleet of 1C MCP servers: status, indexing progress, VRAM and license checks
Ten MCP servers for 1C development: platform reference, targeted object dump and load, COM, storage, file search and BSL Language Server
An MCP server that unpacks 1C's .hbk help, indexes it in Qdrant and gives the agent search over API, snippets and standards
A stdio MCP server that indexes a 1C structure XML export and code into SQLite and gives an agent search over objects and procedures
A local read-only MCP server suite for 1C: a Rust code indexer, metadata skills, a prompt gallery and platform help search, with evidence-backed answers
A read-only MCP and CLI that read a 1C file infobase directly from 1Cv8.1CD and build a configuration map for an AI agent and Obsidian
README in short
The Go service parses 1C event and technology logs, writes them into ClickHouse with daily partitions and TTL, and provisions Grafana dashboards for activity, errors, metadata and the technology log. The MCP server is available over HTTP and stdio. The README details path and conf.cfg setup, external Docker resources, ClickHouse tables and troubleshooting. The author recommends a separate TECHLOG_SKILL for technology log work.