METR MCP
METR (MCP 1C:Enterprise Test Runner)
An MCP server that lets an agent update a 1C infobase, run YaXUnit tests and check syntax
- 120 ★ on the repository
- Last commit
- GPL-3.0
Broad access
Why this level
- Updates the 1C infobase configuration via the connection string
- Launches Designer, ibcmd and 1C clients on the machine
- Infobase login and password sit in the settings file
Install
- Works in
- Services
Manual install
{
"mcpServers": {
"yaxunit-runner": {
"type": "stdio",
"command": "java",
"args": ["-jar", "/path/to/your/mcp-yaxunit-runner.jar"],
"env": {
"SPRING_CONFIG_IMPORT": "/path/to/your/application.yml"
}
}
}
}Download the JAR from releases and prepare application.yml first.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Updates the 1C infobase configuration via the connection string
- Launches Designer, ibcmd and 1C clients on the machine
- Infobase login and password sit in the settings file
This is third-party code. Review the repository files before installing.
What it does
The server attaches to a 1C:Enterprise project through a settings file and gives the agent build and test tools. Before running tests it checks whether sources changed, converts them for EDT projects, updates the infobase through Designer or ibcmd and runs all YaXUnit tests or a single module. It also runs syntax checks through Designer (CheckConfig, CheckModules) and 1C:EDT, dumps the configuration and launches Designer or a client. The agent sees compile errors and failing tests after its own edits.
Who it is for. For 1C developers who write YaXUnit tests and want the agent to run them after each change.
Good fit when
- The agent edits configuration code and must confirm the project builds
- You want YaXUnit tests run from Claude Code, Cursor or VS Code
- You need module syntax checks without opening Designer by hand
Not a fit when
- The project has no YaXUnit tests and no separate test infobase
- The connection string points at a live production infobase
Example request
Update the test infobase, run the tests for the sales posting module and show failuresMCP
- Transport
- stdio, sse
- Authentication
- not required
Environment variables
SPRING_CONFIG_IMPORTrequired- Path to application.yml with project and infobase settings
LOGGING_LEVEL_ROOT- Log level: DEBUG, INFO, WARN, ERROR
Limitations
Requires JDK 17+, an installed 1C:Enterprise 8.3.10+ platform and the YaXUnit framework, plus 1C:EDT 2025.1+ for EDT projects. It ships as a JAR from releases with no npm or PyPI package. You have to write a YAML file with source paths and the infobase connection string first.
How to disable. Remove the yaxunit-runner block from the client MCP config and delete the JAR file.
FAQ
Is the EDT format supported?
Yes, with app.format: EDT the server converts sources before building, and with auto-start it keeps EDT CLI running to speed up conversion.
What updates the infobase?
Designer or the ibcmd utility, selected by app.tools.builder.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsAn MCP server and manager for native 1C TestClient QA automation: BDD scenarios, managed-form checks, without a Vanessa Automation runtime
An MCP server that drives the 1C test client's interface directly: opens forms, fills fields, records and replays scenarios
An MCP tool for interactively driving the 1C:Enterprise UI through the test client: clicks, fields, tables and evidentiary scenario recording
An MCP server and portable admin tool for analyzing an exported 1C XML configuration: object listing, metadata structure, code search
A 1C:EDT plugin that gives agents projects, errors, BSL analysis, form screenshots, metadata refactoring and infobase launch over MCP
1C metadata MCP server
1C_MCP_metadata
An MCP server over a 1C extension's HTTP service that exposes configuration metadata, searches objects and validates query syntax
README in short
The README lists requirements, the YAML settings schema and the MCP tools: test runs, build, configuration dump, app launch and syntax checks. Client setup lives in docs/IDE_SETUP.md with a config example for Claude Desktop and VS Code. It also covers building from source with Gradle and a roadmap. GPL-3.0 licensed.