comol/qa_mcp repository overview

⁠QA MCP for 1C:Enterprise

Streamable HTTP MCP server for the logical UI model of 1C:Enterprise managed applications, driven through the platform's own automated-testing framework (TestiruemoePrilozhenie, /TestManager).

Platform: linux/amd64. Published tags: 0.5.0, latest.

⁠How it runs

The container is an HTTP bridge to a manager server that runs where the 1C platform is installed (Windows). It forwards every MCP request to MCP_QA_UPSTREAM_URL (default http://host.docker.internal:8020/mcp⁠, bearer token in MCP_QA_UPSTREAM_TOKEN) and never starts 1C itself. On the Windows host start the manager first:

python -m mcp_qa --backend manager --transport http --port 8020

⁠Run the bridge

docker run -d --name qa-mcp --init --restart unless-stopped \
  -p 127.0.0.1:8030:8020 \
  --add-host host.docker.internal:host-gateway \
  -e LICENSE_KEY=<your key> \
  -e MCP_QA_UPSTREAM_URL=http://host.docker.internal:8020/mcp \
  -v qa-mcp-data:/data comol/qa_mcp:0.5.0

MCP endpoint: http://127.0.0.1:8030/mcp⁠. Health check: /healthz; info: /. MCP_QA_HTTP_TOKEN protects /mcp with a bearer token; / and /healthz stay public. Set MCP_QA_UPSTREAM_TOKEN to the manager's own token.

Persistent files under /data; the process runs as UID/GID 10001. 1C:Enterprise itself, infobases and 1C licenses are not included.