Skip to main content
Glama
ROCTUP

1C Testpilot

by ROCTUP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to 1C Testpilot

No user-submitted related servers found.

    Related Servers

    • Answer42

      pZayash
      A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to interactively drive 1C:Enterprise UI through the testing client, including opening forms, clicking buttons, filling fields, and capturing evidence.
      129
      6
      MIT

    • qa-mcp

      vlikhobabin
      A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      64
      5
      Apache 2.0

    • bas-mcp-server

      qkiomat
      A
      license
      A
      quality
      D
      maintenance
      Enables 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
      ISC

    • 1C MCP Toolkit

      ROCTUP
      A
      license
      Not graded
      quality
      B
      maintenance
      Integrates 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.
      316
      GPL 3.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    The ten tools are grouped by clear UI domains such as table, window, field, form, document, calendar, and session, so most selections are obvious. However, element discovery/reading overlaps somewhat between tc_app, tc_find, tc_form, and tc_field, requiring descriptions to cross-reference each other to steer correct usage.

    Naming Consistency5/5

    All top-level tools follow a consistent tc_<noun> snake_case pattern, and the nested action names are also uniformly snake_case verbs. There is no mixing of camelCase, PascalCase, or vague standalone names.

    Tool Count5/5

    Ten top-level tools is well within the ideal 3–15 range for a broad UI automation server, and each domain-specific group earns its place. The very large operation surface is handled through action parameters rather than by exploding the exposed tool count.

    Completeness5/5

    The surface covers connection/session lifecycle, window navigation, form/field/table/document/calendar interaction, UI tree search, snapshots and scenario replay, logging, screenshots, and file dialogs. No obvious lifecycle or operation gap stands out for 1C UI test automation.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources