SkillFoxx

Type a name, a task or a service

METR

METR (MCP 1C:Enterprise Test Runner)

An MCP server that lets an agent update a 1C infobase, run YaXUnit tests and check syntax

MCP serverHigh riskRussian stack

alkoleft/mcp-onec-test-runnerAuthor: alkoleft

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.

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 failures

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.

MCP

Transport
stdio, sse
Authentication
not required
Environment variables
SPRING_CONFIG_IMPORT
required		Path to application.yml with project and infobase settings
LOGGING_LEVEL_ROOT
Log level: DEBUG, INFO, WARN, ERROR

Security check

  • 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

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.

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.

Playwright CLI

playwright-cli

Editors’ pick

Microsoft's official Playwright CLI with an agent skill: drive a browser through short commands without heavy MCP schemas

CLIMedium risk13.3K
Editors’ pick

The official MCP server debugger: web UI, automation CLI and terminal UI in one package

CLIMedium risk10.9K
Editors’ pick

SonarSource's official MCP server: quality and security issues, quality gates and code analysis from SonarQube Server and Cloud

MCP serverMedium risk648

Open-source AI agent for pull request review: descriptions, feedback and improvement suggestions on GitHub, GitLab and more

CLIMedium risk13K