Skip to main content
Glama
Sign In
mcp-1c-local-bridge

mcp-1c-local-bridge

by ntappw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to mcp-1c-local-bridge

No user-submitted related servers found.

    Related Servers

    • OneC Remote EPF

      MaryginR
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to work with remote 1C:Enterprise through a local MCP bridge and an EPF agent over outbound HTTPS, supporting metadata inspection, queries, BSL execution, document access, file transfer, and configuration changes without COM or database publication.
      MIT

    • 1c-mcp

      skiddgoddamn
      A
      license
      Not graded
      quality
      D
      maintenance
      Give an AI agent eyes into your 1C:Enterprise 8.3 base — read metadata & data, run queries, and diagnose why a document won't post — over one extension HTTP service.
      MIT

    • 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

    • 1C Testpilot

      ROCTUP
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to drive the 1C:Enterprise test client directly, opening forms, reading and modifying data, working with tables, and recording or replaying action scenarios. Connects to local or remote test clients over their network protocol without a testing manager.
      11
      84
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    The tools mostly target clearly different operations: execute/eval/query are separated by code execution, expression evaluation, and 1C query language semantics. Metadata, find, and usages overlap in domain but differ as browse, search, and dependency lookup; descriptions help resolve the remaining ambiguity.

    Naming Consistency3/5

    All names are lowercase single words, but the set mixes verbs (cancel, eval, execute, find, ping) with nouns (metadata, query, result, sessions, usages). The names are readable and semantically clear, but there is no consistent verb_noun or noun-based convention across the toolset.

    Tool Count5/5

    Ten tools is well within a reasonable range for a bridge server that must cover code execution, queries, metadata introspection, diagnostics, and asynchronous command lifecycle. Each tool appears to earn its place, including auxiliary tools like result, cancel, ping, and sessions.

    Completeness4/5

    The surface covers the core domain well: execute/eval/query for 1C operations, metadata/find/usages for introspection, sessions/ping for diagnostics, and result/cancel for async command handling. A minor gap is the lack of a general command-status/list operation, but most workflows can be completed with the existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources