qa-mcp: native 1C TestClient QA
qa-mcp
An MCP server and manager for native 1C TestClient QA automation: BDD scenarios, managed-form checks, without a Vanessa Automation runtime
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- The Windows bridge performs lifecycle operations and bounded desktop input in a real 1C session
- UI operations and mutations require disposable test data; the README explicitly warns against using production databases
Install
Manual install
python3 -m venv .venv
.venv/bin/python -m pip install ./qa_mcp-0.1.0-py3-none-any.whl
.venv/bin/qa-native-mcpInstall from the ready v0.1.0 release wheel, starts the stdio server.
This is third-party code. Review the repository files before installing.
What it does
The server speaks the 1C platform's TestManager/TestClient protocol directly, without a Vanessa Automation runtime layer in between. It runs Gherkin BDD scenarios, reads and checks managed forms, assertions and waits, produces JUnit and Allure-format reports, and exposes target-bound lifecycle and UI operations to an agent over standard or authenticated HTTP MCP transport. For Windows scenarios there's a separate host-agent bridge that drives a real TestClient, relays events, takes screenshots and performs bounded desktop input, also with mandatory authentication.
Who it is for. For QA engineers and 1C developers who want to automate managed-form and scenario testing directly through the TestClient protocol, without Vanessa Automation.
Good fit when
- You want to run Gherkin BDD scenarios against a real 1C client without Vanessa Automation
- You need JUnit or Allure-format reports for an existing CI setup
- You need a governed Windows bridge for UI operations with bounded desktop input
Not a fit when
- You need a stable production tool: the v0.1.0 release is explicitly marked as an MVP prerelease, not Stable, with no PyPI or GHCR publication
- The v0.1.0 Windows executable is an unsigned Linux cross-build without native Windows verification, as the README explicitly states
- You need live operation without an explicitly authorized test 1C platform and Windows session: tests marked live are not part of ordinary public verification
Example request
Run the customer order scenario on the test database's managed form and send back an Allure-format reportLimitations
The v0.1.0 release is an MVP prerelease; the README explicitly states it does not claim stable or live-native qualification. The Windows bridge in this release has no native Windows verification or a successful helper-bundle check. The open_external_processor tool remains dormant research code and is excluded from the declared stable surface. It requires Python 3.11 or newer and uv to build from source. HTTP transport defaults to loopback only; publishing it without a bearer token is unsafe.
How to disable. Stop the qa-native-mcp process and remove it from your MCP client configuration; for the Windows bridge, stop and remove the host-agent service.
MCP
- Transport
- stdio, http
- Authentication
- API key
| Environment variables | |
|---|---|
| QA_MCP_BEARER_TOKEN secret | Bearer token for authenticated HTTP transport, required for a non-loopback bind. |
| QA_MCP_TRANSPORT | Transport choice: stdio by default or http. |
Security check
- The Windows bridge performs lifecycle operations and bounded desktop input in a real 1C session
- UI operations and mutations require disposable test data; the README explicitly warns against using production databases
README in short
The English README describes the v0.1.0 MVP release contents with SHA256SUMS verification, an architecture of a protocol core, a scenario engine and an optional authenticated Windows bridge, installing from the wheel or from a source snapshot via uv, setting up authenticated HTTP with a bearer token, separately warning about the unsigned Windows executable cross-build, describing a safety model with disposable test data and mandatory transport authentication, and linking to the tool reference, Docker delivery docs and the publication policy. Apache-2.0 license.
FAQ
Is Vanessa Automation needed to use it?
No, the server speaks the TestManager/TestClient protocol directly and does not require a Vanessa Automation manager runtime.
Can this release already be trusted in production?
No, the README explicitly calls v0.1.0 an MVP prerelease with no stability claim, and the Windows bridge has no native verification.
Related
A CLI for testing and red teaming LLM applications: compares models, runs automated CI checks and finds vulnerabilities
Playwright CLI
playwright-cli
Microsoft's official Playwright CLI with an agent skill: drive a browser through short commands without heavy MCP schemas
The official MCP server debugger: web UI, automation CLI and terminal UI in one package
SonarSource's official MCP server: quality and security issues, quality gates and code analysis from SonarQube Server and Cloud