SkillFoxx

1C Testpilot MCP

An MCP server that drives the 1C test client's interface directly: opens forms, fills fields, records and replays scenarios

  • 84 ★ on the repository
  • Last commit
  • AGPL-3.0
MCP server

Broad access

Why this level

  • Drives the real 1C interface and can post documents and change data like a regular user
  • tc_execute_code runs arbitrary BSL code in the client or server context
All reasons and checks
Russian stack

roctup/1c-testpilotAuthor:ROCTUP

Install

Manual install

pipx install git+https://github.com/ROCTUP/1c-testpilot.git && pipx ensurepath

After installation, restart the terminal and the MCP client.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Drives the real 1C interface and can post documents and change data like a regular user
  • tc_execute_code runs arbitrary BSL code in the client or server context

This is third-party code. Review the repository files before installing.

What it does

The server connects to a local or remote 1C test client over its own network protocol, with no test manager involved. An agent gets 10 tools organized by interface object type, driven by an action parameter (up to 155 actions): navigating the window-form-element tree, reading and filling fields, working with tables and trees, clicks, checkboxes, calendars, hyperlinks, and comparing form-state snapshots before and after an action. Separately, tc_execute_code for BSL code and tc_execute_query for queries are available through the Testpilot.epf external processing, which the server opens in the client automatically. It supports recording scenarios to XML (uilog) and replaying them, HTML and Allure reports, 1C window screenshots, and running tests through pytest with a ready Python API.

Who it is for. For QA engineers and 1C developers who want an agent to drive the real 1C interface like a user, including end-to-end checks with no test manager involved.

Good fit when

  • You need an agent to replay a user scenario in the 1C interface and verify the result
  • You write pytest automated tests against the real interface with no test manager
  • You need before-and-after form state comparisons and HTML or Allure reports

Not a fit when

  • You need to work against a production base: the server drives the real interface and can change real data
  • There is no graphical session on Linux (Xvfb is needed) or the run happens under direct Wayland without X11/XWayland
  • You need built-in HTTP authentication: there is none, network access must be restricted yourself

Example request

Open the employee hiring form, fill the required fields with test data and post the document, capturing a screenshot at each step

MCP

Transport
stdio, http, sse
Authentication
not required

Environment variables

TC1C_TRANSPORT
Server transport: stdio, streamable-http or sse.
TC1C_PROFILES_FILE
Path to the YAML file of named connection and launch profiles.

Limitations

The test client protocol is closed and may differ between platform versions; the README limits verified combinations to Windows 8.3.27/8.5.1 and, remotely, Windows and Ubuntu 8.3.27. There is no built-in HTTP authentication; access to the server over Streamable HTTP must be restricted by network or an external proxy. get_screenshot and the isolated desktop are not supported on macOS.

How to disable. Stop the server process or remove the 1c-testpilot entry from your MCP client config, then close the test client it launched with the stop_client action.

FAQ

Can it be used without MCP, just for automated tests?

Yes, there is a separate Python API with pytest integration that talks to 1C directly with no MCP server running.

How do you restrict arbitrary code and queries?

tc_execute_code and tc_execute_query are off by default and are enabled separately via server parameters, independently of each other.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

An MCP tool for interactively driving the 1C:Enterprise UI through the test client: clicks, fields, tables and evidentiary scenario recording

MCP serverBroad access6
Russian stack

A skill and tester agent for Claude Code that test the 1C interface through the 1c-testpilot MCP server with evidence

SkillExtended access22
Russian stack

An MCP server and manager for native 1C TestClient QA automation: BDD scenarios, managed-form checks, without a Vanessa Automation runtime

MCP serverBroad access5

Tester

Тестер

Russian stack

A scenario testing system for 1C:Enterprise with a set of agent skills that let an AI agent operate the application like a regular user

SkillBroad access208

METR

METR (MCP 1C:Enterprise Test Runner)

Russian stack

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

MCP serverBroad access123

1C AI development environment

1C AI Development Environment

Russian stack

1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C

MCP serverBroad access18

README in short

The README describes capabilities in detail (navigation, reading and filling fields, snapshots, recording and replaying scenarios), requirements and installation via pipx, connecting Claude Desktop, Claude Code and Codex over stdio and Streamable HTTP, working with the test client and named YAML profiles, the full list of environment variables, the TOON and JSON response formats, an agent activity log with HTML and Allure reports, and a limitations section on the closed protocol and verified platforms.

README badge

Report a problem