Skip to main content
Glama
infaton

INFATON MCP35

Official
by infaton

Related Servers

Alternatives to INFATON MCP35

No user-submitted related servers found.

    Related Servers

    • 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
      A
      quality
      B
      maintenance
      MCP server for full lifecycle of 1C binary files (CF/CFE/EPF/ERF) without EDT import: unpack to a temporary directory, read and edit code/forms/help, search, diff, repack, and cleanup. Enables code analysis, patching, and bytecode decompilation of protected modules via natural language.
      20
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides read-only access to 1C:Enterprise configuration metadata extracted into SQLite, enabling LLMs to inspect objects, modules, and validate 1C queries.
      MIT
    • 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
      A
      maintenance
      MCP server that validates AI-generated 1C:Enterprise (BSL) code against the real platform API. Catches unknown enum values, wrong argument counts, and missing type members by parsing the platform syntax-helper (shcntx_ru.hbk) — independent Rust implementation with built-in expression validator.
      27
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Rust-native code index MCP server with first-class 1C:Enterprise (BSL) support. Static binary, no runtime — 25 MCP tools (18 universal + 7 BSL-specific), tree-sitter AST for 10 languages, federation across multiple repos.
      131
      MIT

    TDQS

    B3.2/5.0

    Scored across 51 tools

    Disambiguation3/5

    Most tools have distinct purposes, but several clusters overlap heavily: metadata exploration (get_metadata_tree, get_object_metadata, get_object_attributes, get_object_tabular_sections, get_register_dimensions, get_form_structure, search_metadata), object lookup (find_by_name, find_by_code, get_object_by_ref, get_list, get_document_list), and register reads (get_register_records, get_register_totals, get_balance, get_accounting_entries). Descriptions help disambiguate but an agent could easily misselect within these groups.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern (get_, find_, create_, update_, delete_, run_, execute_). Minor deviations like exchange_execute and a few bare action names are readable but slightly off-pattern.

    Tool Count1/5

    51 tools is a severe overload for a single server, exceeding the 50-tool threshold for extreme mismatch. The surface attempts to cover metadata, data access, diagnostics, accounting, exchange, CDC, and batch execution all at once, making selection unwieldy.

    Completeness4/5

    Coverage is broad and strong: full CRUD (create/update/delete/copy), posting lifecycle, metadata introspection, register read/write, accounting balances/entries, diagnostics, CDC/sync, and batch execution. A few gaps exist (e.g. no explicit transaction rollback control or attachment handling), but core lifecycle is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues