edt-bridge
Related Servers
Alternatives to edt-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP 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.205MIT

INFATON MCP35official
AlicenseBqualityAmaintenanceMCP server for 1C:Enterprise ERP with 35 tools: metadata inspection, document CRUD, register queries, and BSP integration. First MCP server for Russian ERP systems (300,000+ organizations). JSON-RPC 2.0 compliant BSL implementation.5140MIT- FlicenseNot gradedqualityAmaintenanceMCP 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-
- AlicenseNot gradedqualityAmaintenanceRust-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.131MIT
- AlicenseAqualityAmaintenanceEnables agents and MCP clients to perform static analysis and code navigation on 1C (BSL) codebases, including diagnostics, callers/callees, definitions, references, complexity metrics, and reindexing.7MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for generating, validating, converting, and searching managed 1C:Enterprise forms in three formats: Configurator, Managed, and EDT.9MIT
TDQS
Scored across 18 tools
Every tool targets a clearly distinct resource/action pair: generic mutations, forms, MXL layouts, CF artifacts/extensions, interface/panels, and validation. Even the edit/info pairs are unambiguous because they operate on different objects or return different views.
All tools share the edtb_ prefix and lower_snake_case, and most follow a <resource>_<operation> pattern. plan_mutations and apply_mutations invert the order, and cf_panels/cf_artifact are noun-heavy names, so the pattern is not perfectly uniform but remains predictable.
18 tools is on the heavy side, but the server covers several distinct EDT workflows such as forms, MXL, CF artifacts, extensions, interface configuration, and validation. Each tool earns its place, so the count is slightly above ideal rather than bloated.
The set covers the main lifecycle pairs: plan/apply mutations, compile/decompile/info for forms and MXL, edit/info for interface and panels, plus CF dump/load and validation. Minor gaps exist, such as no direct generic metadata read/list or extension project creation tool, but agents can often work around them via mutations.