Skip to main content
Glama

Related Servers

Alternatives to bsl-ls-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to run project-wide 1C/BSL diagnostics and per-method cyclomatic/cognitive complexity analysis, returning a ranked refactor triage of what to fix first alongside 25 navigation, search, format and fix tools. Deployed over Streamable HTTP behind nginx with bearer-token auth, one container per project, using a pure-Python engine with no Java or LSP bridge.
      2
      -
    • 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.
      126
      MIT
    • 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.
      -
    • 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.
      24
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to explore and search a 1C:Enterprise configuration codebase, including metadata objects, module procedures, call graphs, and semantic similarity search.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to perform local code search, indexing, and analysis across Java, JavaScript/TypeScript, .NET/C#, and Python projects through the MCP protocol.
      1
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Every tool targets a distinct language-server operation: incoming calls, outgoing calls, declaration lookup, usage lookup, diagnostics, complexity metrics, and index rebuilding. The inverse pairs callers/callees and definition/references are clearly separated by their descriptions, so an agent is unlikely to confuse them.

    Naming Consistency4/5

    All tools share the consistent bsl_ prefix and snake_case convention, and most are noun-style operations such as bsl_callers, bsl_definition, and bsl_diagnostics. The main deviation is bsl_reindex, which reads as an imperative action rather than a noun, but the overall pattern remains predictable.

    Tool Count5/5

    Seven tools is well-scoped for a BSL code-intelligence server: four navigation tools, two code-analysis tools, and one index-maintenance command. Each tool earns its place, and the set is neither too thin nor overloaded.

    Completeness4/5

    The toolset covers the main analysis workflow: callers/callees for call-graph navigation, definition/references for symbol lookup, diagnostics for linting, complexity for maintainability review, and reindex for keeping the index fresh after large changes. A direct symbol-search or module-outline tool is missing, but the complexity tool can enumerate module methods, so the gap is minor and workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues