Vanessa Automation MCP
Vanessa Automation MCP reads 1C test state from chat, showing results and the manager environment after a scenario fails.
- 740 ★ on the repository
- Last commit
- BSD-3-Clause
Broad access
Why this level
- The agent can click buttons and change 1C form fields, affecting the tested information base.
- `get_va_settings` returns setting values without masking passwords and tokens.
Install
- Works in
- Services
Manual install
Read https://pr-mex.github.io/vanessa-automation/dev and its MCP section. Install client_mcp in the test manager base and start the session with `/TestManager`. Enable VanessaExt in Vanessa Automation and install VAExtension in the test-client base. Start with `get_environment_data`; obtain approval for form and data actions.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent can click buttons and change 1C form fields, affecting the tested information base.
- `get_va_settings` returns setting values without masking passwords and tokens.
This is third-party code. Review the repository files before installing.
What it does
Vanessa Automation MCP is an MCP server inside a running Vanessa Automation session. An agent connects to a 1C test manager, inspects the environment, opens feature files and runs scenarios. Tools also read test state and operate forms in the test client. The server starts through the `client_mcp` extension installed in the manager’s information base. This is the testing tool’s own operational interface; separate scenario-writing prompts and session-recovery proxies serve different purposes.
Who it is for. 1C configuration testers running BDD scenarios and inspecting client actions through an AI agent.
Good fit when
- A tester loads a feature file and receives scenario results through an agent.
- A developer inspects form elements in a separate test base.
- An agent checks the manager environment before starting a test client.
- After a scenario failure, a team reads state and results without switching windows manually.
Not a fit when
- A user expects a standalone MCP process without a 1C and Vanessa Automation session.
- The session lacks `/TestManager` but the agent must control a test client.
- The server port would be exposed to an untrusted network with access to a working base.
Example request
Connect to the Vanessa test manager and show environment and scenario state without clicking form buttons or changing data yet.MCP
- Transport
- http
- Authentication
- not required
Limitations
A 1C session running Vanessa Automation with `/TestManager` is required; starting MCP does not turn an ordinary session into a test manager. The manager base needs an active extension named exactly `client_mcp`. Quick start requires enabling the VanessaExt external component in Vanessa Automation and installing the VAExtension extension in the test-client base. Availability depends on client mode: some VanessaExt tools do not work in the web client, so consult the specific tool’s documented requirements before using it.
How to disable. Disable automatic MCP startup on the AI tab, stop the server in client_mcp and remove the IDE connection. Closing the manager session ends the embedded server.
FAQ
Where are installation instructions?
The README points to https://pr-mex.github.io/vanessa-automation/dev. MCP needs Vanessa Automation and an active `client_mcp` from https://github.com/1c-neurofish/onec-client-mcp-devkit/releases in the manager base.
Do I start a separate server?
When `client_mcp` is found and AI-tab startup is enabled, Vanessa starts it automatically. Open it in the test-manager session first and leave self-test mode off.
What is the local endpoint?
The guide uses `http://localhost:9874/mcp` when the IDE is on the same computer. The AI tab changes the port; match that value in the client configuration.
How do I begin diagnostics?
Ask the agent to show the platform version, OS and manager base through `get_environment_data`. Then request loaded-scenario state with `get_vanessa_automation_state` before running tests.
Why are some tools unavailable in the web client?
VanessaExt-dependent tools may require a native client. `get_process_list_os`, for example, explicitly excludes the web client; select a supported session.
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 tool for interactively driving the 1C:Enterprise UI through the test client: clicks, fields, tables and evidentiary scenario recording
PowerShell recipes for headless 1C GUI test runs via Vanessa Automation TestManager, plus a Claude Code skill that solves gotchas absent from the docs
A native component that runs a full MCP server inside 1C: tools, resources and prompts are written in BSL, while a DLL handles the protocol
Reconnecting proxy for the 1C client MCP
client_mcp_vanessa_proxy
A stdio proxy between Claude Code and the client_mcp server inside 1C that reconnects itself after 1C restarts without a manual /mcp
METR
METR (MCP 1C:Enterprise Test Runner)
An MCP server that lets an agent update a 1C infobase, run YaXUnit tests and check syntax
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Vanessa Automation MCP (this card) | yes | not required | 740 | |
| 1C Client MCP Server | no | not required | 71 | The client_mcp extension supplies transport; Vanessa registers its test-manager tools. |
| Vanessa_for_AI | no | 3 | The instruction set guides test writing; Vanessa’s server executes scenarios and reads client state. |
README in short
The main README links to product documentation. The AI guide covers test-manager sessions, extensions, HTTP connection and form tools. Event logging can be enabled for short diagnostics.