1C Testpilot
Related Servers
Alternatives to 1C Testpilot
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to interactively drive 1C:Enterprise UI through the testing client, including opening forms, clicking buttons, filling fields, and capturing evidence.1295MIT
- AlicenseBqualityCmaintenanceEnables AI agents to drive native 1C TestClient QA automation over stdio or authenticated streamable-HTTP transports, running BDD/Gherkin scenarios, reading and verifying managed forms, and performing target-bound lifecycle and UI operations. It also supports JUnit/Allure reporting and an optional authenticated Windows host bridge for desktop input and screenshots.645Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with 1C:Enterprise databases through natural language, providing metadata retrieval, configuration analysis, and code generation.9-
- FlicenseAqualityDmaintenanceEnables AI agents to interact with 1С:Enterprise and BAS ERP systems through REST and HTTP services, providing tools for searching catalogs, creating documents, and querying stock balances.6-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with 1C: Enterprise development environment, including running tests, managing launch profiles, building configurations, and performing database operations through the 1C: Platform Tools extension.38MIT
- AlicenseNot gradedqualityBmaintenanceIntegrates AI agents with 1C:Enterprise databases via MCP and REST API, supporting a built-in HTTP server (no Python required) or a Python proxy mode.279GPL 3.0
TDQS
Scored across 10 tools
Top-level tools are split by domain (session, app, window, field, table, form, etc.), but several overlap in practice: tc_table and tc_field both edit table cells, tc_app and tc_window both expose window state, and tc_form, tc_app, and tc_find all provide element discovery or reading. An agent can often distinguish them, but there are enough cross-cutting concerns to cause misselection.
All 10 tools use a consistent tc_<noun> pattern in snake_case, making the set highly predictable. Action names within each group are also uniformly snake_case and descriptive, even when they use varied phrasing.
10 tools is well within the ideal 3–15 range and each tool maps to a distinct functional area of the 1C test client. The grouping is logical, even though individual tools contain many actions.
The surface covers a broad UI automation lifecycle: connection/launch, window and form state, field and table editing, documents, calendars, scenarios, and object finding. Minor gaps may exist, such as explicit document-saving operations, but the core workflows are well represented.