Skip to main content
Glama

Related Servers

Alternatives to v8help-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for RAG-based search over 1C Enterprise configuration documentation, enabling natural language queries to find objects like справочники, документы, and отчеты.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search and retrieve 1C:Enterprise 8.3 syntax documentation, including quick references, detailed syntax info, and object members, through MCP tools backed by an Elasticsearch index.
      3
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for searching and analyzing 1C enterprise metadata and BSL code using a SQLite backend. Enables querying configuration structure, code routines, and performing compliance checks via natural language.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for 1C:Enterprise that provides precise syntax reference cards (call signatures, parameters, return types, examples) by element name and lists object members. It helps AI agents answer 1C development questions using the official Russian help book.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for 1C:Enterprise that provides AI assistants with access to configuration data via vector search, structural indexing, and call graphs. It enables semantic code queries and rapid metadata object lookups without requiring the direct reading of raw files.
      77
      AGPL 3.0

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    The tools are largely distinct: search, page retrieval, related pages, hierarchy, index build/status, and config access have clear boundaries. The only mild overlap is discover vs config_get, which both surface configuration/state, but their focus on autodiscovery vs effective settings is enough to separate them.

    Naming Consistency3/5

    Names are readable and mostly snake_case, but the conventions are mixed: bare verbs (search, build, discover), nouns (related, hierarchy), verb_noun (get_page), and the inverted noun_verb pattern (config_get, config_set). This is inconsistent but not chaotic.

    Tool Count5/5

    Nine tools form a well-scoped set for a documentation/help-server: four read/retrieval operations, two index lifecycle operations, and three config/discovery operations. Each tool has a distinct job and none feel redundant.

    Completeness5/5

    The surface covers the full help-documentation workflow: search, page content, related links, table of contents, index rebuild with async status, and configuration discovery/update. I see no critical dead ends for agents using this server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues