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.
      4
      -
    • 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
      C
      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.
      79
      AGPL 3.0

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: search finds pages, get_page retrieves full text, related handles links, hierarchy provides the TOC, and build/build_status form a trigger/check pair. The only real overlap is config_get vs discover, since both surface current configuration (discover additionally does autodiscovery), which could cause occasional misselection.

    Naming Consistency3/5

    Naming mixes single-word noun/verb tools (search, related, hierarchy, build, discover) with verb_noun patterns (get_page, build_status) and noun_verb patterns (config_get, config_set). The ordering of config_get/config_set (noun_verb) conflicts with build_status (verb_noun), so conventions are readable but not fully predictable.

    Tool Count5/5

    Nine tools is well-scoped for a documentation search/index server. Each tool covers a distinct operation (search, retrieval, related links, TOC, build lifecycle, config) with no obvious redundancy beyond the minor config overlap.

    Completeness4/5

    The surface covers the full lifecycle: discovery, config get/set, index building with async status, search, page retrieval with chunking, related links, and hierarchy browsing. Minor gaps exist (e.g., no direct way to enumerate books or list all pages), but core retrieval workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues